This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Well thank you all. With a combination of properly setting the LD_LIBRARY_PATH and the libraries I built with crosstool-NG I was able to determine the libstdc++ library that shipped with openSUSE was bad. The one I built with crosstool-NG of the same version allowed my app to run just fine on openSUSE. Thanks again, Gavin On 8/6/2010 11:21 AM, Arnaud Lacombe wrote: > Hi, > > On Fri, Aug 6, 2010 at 1:59 PM, Gavin Kavanaugh<zeddicus76@gmail.com> wrote: > >> Arnaud, >> Thank you for the quick reply. I had not even tried linking statically so I >> am doing that now. >> >> I have tried LD_LIBRARY_PATH unsuccessfully. When I set it to my new >> library path, suddenly my commands stop working (i.e. ls, cd ). I end up >> with problems since my system needs the existing libraries, but I want the >> application to run with the new ones. I hope that the static linking will >> resolve this. >> >> > you can override LD_LIBRARY_PATH only for your program: > > % LD_LIBRARY_PATH=/path/to/really/old/libc/ /bin/ls > /bin/ls: /path/to/really/old/libc/libc.so.6: version `GLIBC_2.4' not > found (required by /bin/ls) > [...] > > - Arnaud > -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |