On 2010-Jan-30 11:51:08 +0000, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: >Bill Hart wrote: >> Cause of what David? MPIR 1.3.0 works absolutely fine on t2 if you set >> the library paths correctly. > >I'm not convinced it should be necessary to set LD_LIBRARY_PATH like >that. It is not with other 64-bit applications. But I may be mistaken
I'll go further: If it's necessary to set LD_LIBRARY_PATH for an executable to find a compiler-specific library then the linker configuration is broken. If gcc/g++ needs libgcc then it's up to it to ensure that libgcc is linked into the executable with an appropriate rpath (if necessary) to enable it to be found at runtime. If libtool is overriding gcc's default linker, then it's up to libtool to ensure that it correctly handles compiler-specific libraries. In this case, I'm not sure whether it's gcc or libtool that is broken but one of them is. >But from experience, compiling code on multiple platforms often shows >up errors not seen on other platforms, but lie in wait, ready to give >the wrong answers at some point in the future. Agreed. -- Peter Jeremy
pgpFNxyUvE2NB.pgp
Description: PGP signature
