Summary: | kde-base/arts-1.2.2 failes to emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Veith (RETIRED) <xtv> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas Veith (RETIRED)
![]() possibly dup of 47457? I'm not sure if its a dupe of 47457.. there are the same errors.. but a) I dont use USE="multilib" b) the workaround "LINK = $(LIBTOOL) --mode=link $(CXX) $(AM_CFLAGS) $(CFLAGS)" doesnt work So maybe it is the same bug, maybe not.. I just realized that I now also can't emerge arts-1.2.1 anymore; what a pity I cant remember when it worked and which packages differ from then... I could build arts-1.2.2 without problems on my laptop, which is not 100% identical to my main pc. libtool-1.4.3-r4, gcc-3.3.3, glibc-2.3.2-r9, binutils-2.14.90.0.7-r4, yacc-1.9.1-r1, automake-1.7.8 and autoconf-2.58-r1 are the same version; laptop is linux 2.4.20-gentoo-r6 with OSS, pc is linux 2.6.5 with ALSA... I need guidance to solve this problem - so if anyone has an idea where I could look for differences or any other idea... I just got an email from Janne Ravantti: --- I started to "emerge arts" and after emerge ran "./configure" and made "Makefiles", I simply suspended emerge with ^Z and went to "/var/tmp/portage/arts-1.2.2.../mcop/"-directory (Sorry, I lost the actual path when the emerge finished) and added as one of the library paths to link against the /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3 - path (I added the line in Makefile where there were other "-L" - descriptions). After adding the -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3, I simply resumed emerge and it went all ok. --- This also fixed it for me! Thank you, Janne! Maybe this gives you the hint how to fix the ebuild. Regards, Thomas have you tried doing it without using distcc? seems more of a problem keeping multiple copies of gcc around, or distccing it acrossing different gcc versions? anyway, i can't recreate this so it seems like a local configuration issue of some sort. |