>On Thu, 04 Jul 2013 22:23:03 -0500 >Tyrin Price <[email protected]> wrote: > > On 07/04/2013 09:51 PM, Aleksandar Kuktin wrote: > > an happen if you > > set /tools/bin/gcc to try using /lib/libc.so. The symlink hack I > > suggested is only really usefull for running applications. It should > > never be used for building otherwise you run the risk of opening the > > gates of hell. > Thanks for the pointers. I may just rebuild with clfs. I need to > install the 32-bit Adobe AIR and I am not sure if the method you > outline will work for me or if I will inadvertently open the gates of > hell. :-)
First build what you need from CLFS, then link the linker into /lib and start your application. That way you will never overlap building and running. > Still, that is a lot of work when I really only need one 32-bit app. Yeah, I know. I also recently had to make a piece of proprietary software run on my system, but the documentation specified that the application needed libstdc++.so.5. That version of the standard C++ library last shipped with GCC-3.<something>. So yeah, I built the ancient GCC just for a single old library. :) Ofcourse, later on it turned out that the application will run perfectly well with the current library (libstdc++.so.6). -- You don't need an AI for a robot uprising. Humans will do just fine.
signature.asc
Description: PGP signature
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
