sys-devel/gcc-4.3.3 creates broken .la files Reproducible: Always Steps to Reproduce: 1. run reconclio (paludis revdep-rebuild) 2. FAIL Actual Results: uptempo ~ # reconcilio Searching for broken packages... reconcilio@1233161897: [WARNING reconcilio.broken_linkage_finder.failure] In thread ID '9941': ... In program reconcilio : ... When performing the Fix Linkage action: ... When checking for broken linkage in '/': ... When checking '/usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libgfortran.la' as a libtool library: ... Expected an = at line 41 reconcilio@1233161897: [WARNING reconcilio.broken_linkage_finder.failure] In thread ID '9941': ... In program reconcilio : ... When performing the Fix Linkage action: ... When checking for broken linkage in '/': ... When checking '/usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libgomp.la' as a libtool library: ... Expected an = at line 41 reconcilio@1233161897: [WARNING reconcilio.broken_linkage_finder.failure] In thread ID '9941': ... In program reconcilio : ... When performing the Fix Linkage action: ... When checking for broken linkage in '/': ... When checking '/usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libsupc++.la' as a libtool library: ... Expected an = at line 41 reconcilio@1233161897: [WARNING reconcilio.broken_linkage_finder.failure] In thread ID '9941': ... In program reconcilio : ... When performing the Fix Linkage action: ... When checking for broken linkage in '/': ... When checking '/usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libmudflap.la' as a libtool library: ... Expected an = at line 41 reconcilio@1233161897: [WARNING reconcilio.broken_linkage_finder.failure] In thread ID '9941': ... In program reconcilio : ... When performing the Fix Linkage action: ... When checking for broken linkage in '/': ... When checking '/usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libgfortranbegin.la' as a libtool library: ... Expected an = at line 41 reconcilio@1233161897: [WARNING reconcilio.broken_linkage_finder.failure] In thread ID '9941': ... In program reconcilio : ... When performing the Fix Linkage action: ... When checking for broken linkage in '/': ... When checking '/usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libmudflapth.la' as a libtool library: ... Expected an = at line 41 No broken packages found Expected Results: There should be a "=" at line 41 in the .la files above. Running fix_libtool_files.sh does not help in any way.
.la files are created by libtool, not by gcc. Care to cat one of the .la files? That might help figuring out whether this is a libtool problem or a paludis problem.
# libgfortran.la - a libtool library file # Generated by ltmain.sh (GNU libtool 1.2435 2007/03/18 18:44:42) 2.1a # # Please DO NOT delete this file! # It is necessary for linking the library. # The name that we can dlopen(3). dlname='libgfortran.so.3' # Names of this library. library_names='libgfortran.so.3.0.0 libgfortran.so.3 libgfortran.so' # The name of the static archive. old_library='libgfortran.a' # Linker flags that can not go in dependency_libs. inherited_linker_flags='' # Libraries that this one depends upon. dependency_libs=' -lm' # Names of additional weak libraries provided by this library weak_library_names='' # Version information for libgfortran. current=3 age=0 revision=0 # Is this an already installed library? installed=yes # Should we warn about portability when linking against -modules? shouldnotlink=no # Files to dlopen/dlpreopen dlopen='' dlpreopen='' # Directory that this library needs to be installed in: libdir'/usr/lib/gcc/i686-pc-linux-gnu/4.3.3' ^ the "=" is missing
I have same problem. Dunno maybe its paludis thing, maybe gcc 4.3.3 needs libtool 2.2.7a. I tryed to downgrade gcc, but 4.3.2 shows same erros after downgrade. I downgraded paludis, but no result.
Hi, similar problem with openmp stuff: emerge imagemagick fails file: /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.3/libgomp.la # Directory that this library needs to be installed in: libdir'/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.3' adding a '=': >>> Installing media-gfx/imagemagick-6.4.8.3 :-)
Okay so this is not a paludis issue.
The Gentoo GCC Upgrading guide says that libtool should be reemerged. Have you already done so? http://www.gentoo.org/doc/en/gcc-upgrading.xml
I haven't. And that was also not necessary when going from GCC 4.0.x (or was it 4.1.x?) to 4.3.2 last week. But as the affected file(s) are .la files created during the gcc upgrade (here from 4.3.2 to 4.3.3). Is the idea to - emerge gcc - re-emerge libtool - emerge gcc again to get it right? That would really be a waste of time... But if so, then the GCC ebuild should be change to at least print that requirement. (I have set PORTAGE_ELOG_CLASSES="warn error" but didn't see anything like that.)
i've done this without success: the .la remains puzzled. Wed Jan 28 21:12:59 2009 >>> sys-devel/gcc-4.3.3 ...here the '=' hack Wed Jan 28 23:15:30 2009 >>> media-gfx/imagemagick-6.4.8.3 Thu Jan 29 17:32:39 2009 >>> sys-devel/libtool-1.5.26 Thu Jan 29 18:27:02 2009 >>> sys-devel/gcc-4.3.3 Thu Jan 29 18:48:17 2009 >>> sys-devel/libtool-1.5.26 /usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.3/fix_libtool_files.sh 4.3.2
*** This bug has been marked as a duplicate of bug 256636 ***
(In reply to comment #9) > > *** This bug has been marked as a duplicate of bug 256636 *** > steps are: emerge --sync (now:toolchain.eclass,v 1.389) emerge gcc OK