Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=502024 --- Comment #36 from Antti Andreimann <antti.andreimann@xxxxxxx> 2009-07-07 19:41:05 EDT --- Well, I have now managed to get the package to link with gcc43 on EL5: %build +CXX=g++43 LIBS=`$CXX -print-file-name=libstdc++.a` \ MAKEFLAGS="verbose=1" CXXFLAGS=$RPM_OPT_FLAGS ./build.sh $CXX -print-file-name=libstdc++.a evaluates to: /usr/lib/gcc/i386-redhat-linux6E/4.3.2/libstdc++.a which is part of a libstdc++43-devel package. There is no corresponding libstdc++43 package. This makes me nervous, since I'm not sure which parts of libstdc++ are now statically linked and which are still dynamic. According to this blog post (http://www.trilithium.com/johan/2005/06/static-libstdc/), mixing statically and dynamically linked C++ code is not a very good idea. Which would be the proper solution for EL5? Filter -g and stick with GCC4.1 or compile with 4.3 and hope that this strange linking method actually works? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review