View previous topic :: View next topic |
Author |
Message |
nexus6 Tux's lil' helper

Joined: 10 Jan 2007 Posts: 92
|
Posted: Sun Feb 03, 2008 11:54 pm Post subject: [Portage] attr-2.4.39 > warning: jobserver unavailable .. |
|
|
Bonsoir,
Je tente d'emerger attr-2.4.39 mais durant la compilation, j'ai plusieurs fois ce message :
Code: | gmake[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. |
Et je finis lamentablement par ça :
Code: | /usr/bin/xgettext --language=C --keyword=_ -o attr.pot ../attr/attr.c ../getfattr/getfattr.c ../setfattr/setfattr.c ../libattr/attr_copy_fd.c ../libattr/attr_copy_file.c
/usr/bin/xgettext: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory
gmake[1]: *** [attr.pot] Error 127
make: *** [default] Error 2
?[31;01m*?[0m
?[31;01m*?[0m ERROR: sys-apps/attr-2.4.39 failed.
?[31;01m*?[0m Call stack:
?[31;01m*?[0m ebuild.sh, line 1701: Called dyn_compile
?[31;01m*?[0m ebuild.sh, line 1039: Called qa_call 'src_compile'
?[31;01m*?[0m ebuild.sh, line 44: Called src_compile
?[31;01m*?[0m attr-2.4.39.ebuild, line 45: Called die
?[31;01m*?[0m The specific snippet of code:
?[31;01m*?[0m emake || die
?[31;01m*?[0m The die message:
?[31;01m*?[0m (no error message)
?[31;01m*?[0m
?[31;01m*?[0m If you need support, post the topmost build error, and the call stack if relevant.
?[31;01m*?[0m A complete build log is located at '/var/tmp/portage/sys-apps/attr-2.4.39/temp/build.log'.
?[31;01m*?[0m
|
J'ai tenté de me renseigner, et voilà ce que j'ai comme info :
Quote: | warning: jobserver unavailable: using -j1. Add `+' to parent make rule.'
In order for make processes to communicate, the parent will pass information to the child. Since this could result in problems if the child process isn't actually a make, the parent will only do this if it thinks the child is a make. The parent uses the normal algorithms to determine this (see How the MAKE Variable Works). If the makefile is constructed such that the parent doesn't know the child is a make process, then the child will receive only part of the information necessary. In this case, the child will generate this warning message and proceed with its build in a sequential manner. |
Mais je ne comprend pas ce qui coince.
Si quelqun a une idée... |
|
Back to top |
|
 |
CryoGen Veteran


Joined: 11 Feb 2004 Posts: 1426 Location: Bamako - Mali - Afrique
|
Posted: Mon Feb 04, 2008 12:00 am Post subject: |
|
|
Hum, pour la compil qui ne passe pas reemerge sys-devel/gettext (cassé à cause de expat) _________________ - CryoGen` on #gentoofr@irc.freenode.net
- ~amd64 / KDE4
- I'm the bone of my sword... |
|
Back to top |
|
 |
nexus6 Tux's lil' helper

Joined: 10 Jan 2007 Posts: 92
|
Posted: Mon Feb 04, 2008 12:13 am Post subject: |
|
|
Merci CryoGen. J'avais également remarqué des retours sur expat. Certains préconisaient un revdep-rebuild , d'autres de paramétrer MAKEOPTS="-j1".
Mon CPU est un Core2 Duo 64 bit, ça me semblais étrange de devoir parametrer GCC avec MAKEOPTS="-j1" Et étant donné que je ne sais pas comment faire un "revdep-rebuild", alors je vais essayer de reemerger sys-devel/gettext. Pourrais-tu cependant m'indiquer ce que c'est qu'expat? Il paraitrait que c'est une LIB qui peut poser quelques soucis? |
|
Back to top |
|
 |
nexus6 Tux's lil' helper

Joined: 10 Jan 2007 Posts: 92
|
Posted: Mon Feb 04, 2008 12:34 am Post subject: oops! |
|
|
A priori j'ai toujours la même erreur, mais d'autres sont apparues :
Code: | libattr.c:304: warning: pointer targets in passing argument 5 of 'attr_list_pack' differ in signedness
libattr.c:304: warning: pointer targets in passing argument 6 of 'attr_list_pack' differ in signedness
libattr.c: In function 'attr_listf':
libattr.c:344: warning: pointer targets in passing argument 5 of 'attr_list_pack' differ in signedness
libattr.c:344: warning: pointer targets in passing argument 6 of 'attr_list_pack' differ in signedness
|
Bon, j'emerge gentoolkit, apparement c'est avec ça que je pourrais faire un "revdep-rebuild", en espérant que cela réparera le code cassé. Sinon, au pire, je mettrais temporairement "MAKEOPTS="-j1" en option. |
|
Back to top |
|
 |
nexus6 Tux's lil' helper

Joined: 10 Jan 2007 Posts: 92
|
Posted: Mon Feb 04, 2008 12:42 am Post subject: hmmm... |
|
|
Code: | Configuring search environment for revdep-rebuild
Checking reverse dependencies...
Packages containing binaries and libraries broken by a package update
will be emerged.
?[32;01mCollecting system binaries and libraries...?[0m using existing /root/.revdep-rebuild.1_files.
?[32;01mCollecting complete LD_LIBRARY_PATH...?[0m using existing /root/.revdep-rebuild.2_ldpath.
?[32;01mChecking dynamic linking consistency...?[0m using existing /root/.revdep-rebuild.3_rebuild.
?[32;01mAssigning files to ebuilds...?[0m using existing /root/.revdep-rebuild.4_ebuilds.
?[32;01mEvaluating package order...?[0m using existing /root/.revdep-rebuild.5_order.
?[32;01mAll prepared. Starting rebuild...?[0m
emerge --oneshot =sys-devel/gettext-0.17 =dev-lang/python-2.4.3-r4
?.?.?.?.?.?.?.?.?.?.
Calculating dependencies
emerge: there are no ebuilds to satisfy "=dev-lang/python-2.4.3-r4".
?[31;01mrevdep-rebuild failed to emerge all packages?[0m
?[31;01myou have the following choices:?[0m
- if emerge failed during the build, fix the problems and re-run revdep-rebuild
or
- use -X or --package-names as first argument (trys to rebuild package, not exact
ebuild)
or
- set ACCEPT_KEYWORDS="~<your platform>" and/or /etc/portage/package.unmask
(and remove /root/.revdep-rebuild.5_order to be evaluated again)
or
- modify the above emerge command and run it manually
or
- compile or unmerge unsatisfied packages manually, remove temporary files and
try again (you can edit package/ebuild list first)
?[32;01mTo remove temporary files, please run:?[0m
rm /root/.revdep-rebuild*.?_*
|
Bon, je verrai ça demain... (woops ! on y est déjà ) |
|
Back to top |
|
 |
ceric35 Tux's lil' helper


Joined: 27 Aug 2006 Posts: 115
|
Posted: Mon Feb 04, 2008 9:29 am Post subject: |
|
|
dev-lang/python-2.4.3-r4 ne doit plus etre disponible dans l'arbre je pense
tente un "revdep-rebuild -X" |
|
Back to top |
|
 |
|