View previous topic :: View next topic |
Author |
Message |
avx Advocate
Joined: 21 Jun 2004 Posts: 2152
|
Posted: Thu Sep 10, 2009 2:01 pm Post subject: [solved / workaround] libxslt merging fails |
|
|
On a fresh system, merging dev-libs/libxslt-1.1.24-r1 fails for me. I already filed a bug, but since it's quite urgent, maybe someone here has an idea.
The important part from build.log Quote: | /bin/sh ../libtool --tag=CC --mode=link i686-pc-linux-gnu-gcc -Os -march=pentium-m -fomit-frame-pointer -pipe -Wall -version-info 2:24:1 -Wl,--hash-style=both -Wl,-O1 -Wl,--as-needed -Wl,--sort-common -s -o libxslt.la -rpath /usr/lib attrvt.lo xslt.lo xsltutils.lo pattern.lo templates.lo variables.lo keys.lo numbers.lo extensions.lo extra.lo functions.lo namespaces.lo imports.lo attributes.lo documents.lo preproc.lo transform.lo security.lo -lxml2 -lz -lm -lm
libtool: link: i686-pc-linux-gnu-gcc -shared .libs/attrvt.o .libs/xslt.o .libs/xsltutils.o .libs/pattern.o .libs/templates.o .libs/variables.o .libs/keys.o .libs/numbers.o .libs/extensions.o .libs/extra.o .libs/functions.o .libs/namespaces.o .libs/imports.o .libs/attributes.o .libs/documents.o .libs/preproc.o .libs/transform.o .libs/security.o -Wl,--as-needed /usr/lib/libxml2.so /usr/bin /usr/sbin /bin /sbin -ldl -lz -lm -march=pentium-m -Wl,--hash-style=both -Wl,-O1 -Wl,--sort-common -Wl,-soname -Wl,libxslt.so.1 -o .libs/libxslt.so.1.1.24
/usr/bin: file not recognized: Is a directory
collect2: ld returned 1 exit status
make[2]: *** [libxslt.la] Error 1
make[2]: Leaving directory `/portage/tmp/portage/dev-libs/libxslt-1.1.24-r1/work/libxslt-1.1.24/libxslt'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/portage/tmp/portage/dev-libs/libxslt-1.1.24-r1/work/libxslt-1.1.24'
make: *** [all] Error 2
[31;01m*[0m
[31;01m*[0m ERROR: dev-libs/libxslt-1.1.24-r1 failed.
[31;01m*[0m Call stack:
[31;01m*[0m ebuild.sh, line 49: Called src_compile
[31;01m*[0m environment, line 3318: Called die
[31;01m*[0m The specific snippet of code:
[31;01m*[0m emake || die "Compilation failed"
[31;01m*[0m The die message:
[31;01m*[0m Compilation failed
[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 '/portage/tmp/portage/dev-libs/libxslt-1.1.24-r1/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/portage/tmp/portage/dev-libs/libxslt-1.1.24-r1/temp/environment'.
[31;01m*[0m |
tia,
ph
Edit, already run `emerge python libxml2` and `revdep-rebuild`, no change.
Edit2, don't think that that's important, but this system ain't "at live, yet", still in chroot from the latest sysresccd
Last edited by avx on Thu Sep 10, 2009 10:08 pm; edited 1 time in total |
|
Back to top |
|
|
sasho23 Apprentice
Joined: 28 Dec 2005 Posts: 186 Location: Pamplona , Spain
|
Posted: Thu Sep 10, 2009 4:29 pm Post subject: |
|
|
Hi , you should try
Code: | lafilefixer --justfixit |
of course first
Code: | emerge -pv lafilefixer |
and after all
good luck |
|
Back to top |
|
|
avx Advocate
Joined: 21 Jun 2004 Posts: 2152
|
Posted: Thu Sep 10, 2009 6:11 pm Post subject: |
|
|
Tried it, nothing to fix, nothing to rebuild, still the same error. Now having a look at what's been hinted at in the bugreport. |
|
Back to top |
|
|
avx Advocate
Joined: 21 Jun 2004 Posts: 2152
|
Posted: Thu Sep 10, 2009 10:08 pm Post subject: |
|
|
Solved.
It's a bug in the sysresccd and running `unset path` after the chroot solves the problem. More info in the mentioned bug. |
|
Back to top |
|
|
zaai Apprentice
Joined: 24 Jul 2004 Posts: 175
|
Posted: Sat Apr 10, 2010 3:59 am Post subject: |
|
|
Thanks that just saved me a lot of time. _________________ * most bugs can be reduced to either dependency or state *
Athlon64 X2 4800+ on Asus M2N SLI deluxe with 4GB Dual channel
video nVidia GForce 7300 GS 512MB (snail); xorg-7.2
kernel 2.6.24-gentoo-r3 |
|
Back to top |
|
|
darkmagex6 n00b
Joined: 28 Jan 2008 Posts: 8
|
Posted: Mon Jun 21, 2010 6:28 pm Post subject: |
|
|
I just had this problem with libxslt-1.1.26 (like you, in the middle of an install via a system rescue cd)...compile was a success!! Thanks for the tip |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Fri Jul 09, 2010 7:23 pm Post subject: |
|
|
Apparently it's still an issue as I just encountered this on a freshly downloaded System Rescue CD ISO.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
|