When trying to install singular on my system, I got the following message (it seems there is a problem with --sort-common and --as-needed).
Created attachment 310855 [details] build log and emerge --info
I have the same issue (with GCC 4.6). I see that a highly related bug is #387869. It seems that this bug is back but I'm not sure if it's the exact same issue as this one was fixed in version 3.1.3. SLDFLAGS is being used with g++ in Makefile.in. The strange thing is that the ebuilds for version 3.1.3.3 and 3.1.4 use the same SLDFLAGS sed command to add the raw SDFLAGS. Version 3.1.3.3 builds, version 3.1.4 does not. Still trying to figure this out. :)
Hi, I did not have time to look into this in detail, but we had this bug fixed for most of singular. It comes up now again because of the introduction of the python dependent code. Basically upstream need to fix their makefiles, it passes ld options to gcc without the proper prefix.
Created attachment 311449 [details] Fixed ebuild Attaching a fixed version of the ebuild. I don't know how "clean" is this solution, please fix as needed. Basically, it adds the SLFLAGS2 variable containing the proper prefixes for GCC, and replaces any SLFLAGS use in a GCC call to SLFLAGS2. In this case it only changes the one line that causes this bug, but the ebuild would "repair" line using bad LDFLAGS. If a patch would be preferred instead of a sed, please let me know and I will fix the ebuild accordingly.
The new ebuild worked fine. Thanks !
(In reply to comment #4) > Created attachment 311449 [details] > Fixed ebuild > > Attaching a fixed version of the ebuild. I don't know how "clean" is this > solution, please fix as needed. > > Basically, it adds the SLFLAGS2 variable containing the proper prefixes for > GCC, and replaces any SLFLAGS use in a GCC call to SLFLAGS2. In this case it > only changes the one line that causes this bug, but the ebuild would > "repair" line using bad LDFLAGS. > > If a patch would be preferred instead of a sed, please let me know and I > will fix the ebuild accordingly. Hi, thanks for finding this solution. It looks alright to me. Eventually upstream will clean it up, but until then can go with your sed. + 13 May 2012; Thomas Kahle <tomka@gentoo.org> +singular-3.1.4-r1.ebuild: + Fix bug 414709. Thanks Jean-Francis Roy for the solution.
