Thanks
Some status for failed builds:
- atlas : compil error
- bacula : compil error
- base64coder : compil error
- batik : compil error
- bogofilter : need gsl-devel
- brasero : need brasero-devel, nautilus-devel,
tracker-devel
- compat-gcc-32 : compil error
- compat-gcc-34 : compil error
- compat-gcc-44 : compil error
- compat-glibc : compil error
- compat-opensm-libs : need libibmad-devel,
libibumad-devel
- dapl : need libibverbs-devel, librdmacm-devel
- easymock : compil error
- evolution : need bogofilter
- evolution-ews : need evolution-devel
- evolution-mapi : need evolution-devel
- gegl : need suitesparse-devel
- gimp : need gegl-devel
- gnome-document : need inkscape
- golang-github-gorilla-context : need golang
- golang-github-kr-pty : need golang
- golang-github-syndtr-gocapability : need golang
- gsl : compil error
- gutenprint : need gimp, gimp-devel
- hwloc : need libibverbs-devel
- ibacm : need libibumad-devel, libibverbs-devel
- ibutils : need libibumad-devel, libibverbs-devel,
opensm-devel
- infiniband-diags : need libibmad-devel,
libibumad-devel, opensm-devel
- inkscape : need gsl-devel
- ipa : need python-lesscpy
- libcap-ng : compil error
- libcxgb3 : need libibverbs-devel,
valgrind-devel
- libcxgb4 : need libibverbs-devel
- libibcm : need libibverbs-devel
- libibmad : need libibumad-devel, valgrind-devel
- libibumad : need valgrind-devel
- libibverbs : need valgrind-devel
- libmlx4 : need libibverbs-devel
- libmlx5 : need libibverbs-devel
- libmthca : need libibverbs-devel, valgrind-devel
- libnes : need libibverbs-devel, valgrind-devel
- libocrdma : need libibverbs-devel
- librdmacm : need ibacm-devel, libibverbs-devel,
valgrind-devel
- libreoffice : compil error
- libreoffice-voikko : need libreoffice-sdk
- libseccomp : need valgrind
- libusnic_verbs : need libibverbs-devel,
valgrind-devel
- mpich : need hwlock-devel
- mstflint : need libibmad-devel
- mvapich2 : need hwloc-devel, libibmad-devel,
libibumad-devel, libibverbs-devel, librdmacm-devel
- openmpi : need hwloc-devel, libibcm-devel,
libibverbs-devel, librdmacm-devel, opensm-devel,
valgrind-devel
- opensm : need libibmad-devel
- openssl098e : compil error
- papi : need libibmad-devel
- pcp : need libibmad-devel, libibumad-devel,
papi-devel
- perftest : need
libibumad-devel, libibverbs-devel,
librdmacm-devel
- qemu-guest-agent : need librdmacm-devel
- qemu-kvm : need librdmacm-devel
- qperf : need libibverbs-devel, librdmacm-devel
- rhythmbox : need brasero-devel
- scipy : need suitesparse-devel
- spice-gtk : need libcacard-devel
- srptools : need libibumad-devel,
libibverbs-devel
- suitesparse : need atlas-devel > 3.10
- syslinux : need /usr/include/gnu/stubs-32.h
- valgrind : need openmpi-devel
- virt-top : compil error
- virt-viewer : need spice-gtk3-devel
- xsane : need gimp-devel
So... in bold, only dependancies problems.
If we can get
libibverbs, libibmad, libibumad we should compile
a lot of packages, but to get libibverbs it's a
circular dep..
--> libibverbs : need valgrind-devel. valgrind
need openmpi-devel. Openmpi need
libibverbs-devel...
Anyway to put libibverbs-devel on c7-buildroot?
--> Brasero : need brasero-devel. Circular dep :s
--> Golang* : need golang package, but it is not on
repo and not on build list?
Nicolas Repentin
<
nicolas@shivaserv.fr>
1 septembre 2015 18:39 "Fabian Arrotin" <
arrfab@centos.org>
a écrit:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/15 14:09, Nicolas Repentin wrote: > Little update > > <nicolas@shivaserv.fr <mailto:nicolas@shivaserv.fr>> > > > Thanks for the requeue and the explaination. > > I've submitted others jobs: > > *abrt-java-connector - 4178 --> OK* *empathy - 4458 --> OK* requeued ... > > > Questions :p > > - How to help to resolve real compilation errors with plague? Need > to modify and regenerate a modify src.rpm package? yes, and ideally everything will be available as patch[es] so that someone can just reuse that to submit it again for validation. All tho
se
patches
will then need to also land on the corresponding branch on git.centos.org when it will be available. > - Same, for example, to build libibverbs, needed for a lot of > packages, I need valgrind-devel. Valgrind need openmpi-devel >= > 1.3.3, but openmpi need valgrind-devel, and libibverbs-devel (and > others). How to proceed to this kind of case? Because devel package > is generated from normal package, right? That's another issue : circular deps, and one has first to inject a package available in the buildroot to then build the required packages, and then rinse and repeat with the built packages. That what was need to boostrap most of initial packages for the c7-buildroot (built selectively against F19) : http://armv7.dev.centos.org/repodir/c7-buildroot So those were built *outside* of plague, and so directly with mock,
against s
pecific mock config files. For patches, I initially put those I needed here : http://armv7.dev.centos.org/repodir/c7-buildroot-patched-SRPMS but then, when Johnny took up the build effort, I don't know where he copied his. > > > Nicolas Repentin <nicolas@shivaserv.fr > <mailto:nicolas@shivaserv.fr>> > - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
.0.22 (GN
U/Linux) iEYEARECAAYFAlXl1KQACgkQnVkHo1a+xU4chACcCEOrJiKOrTTPsKC/AspsDHnl 40sAnRDal9mda8qMeJpHwtXekS0SuK/Z =CXlv -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev