On 02/27/2013 08:04 PM, Armin K. wrote: > On 02/27/2013 07:24 PM, Frans de Boer wrote: >> Dear all, >> >> The book allows creation if 32-bit systems as well as 64-bit. However, >> on 64-bit systems the library directory is still called /usr/lib pointed >> to from the symlink /usr/lib64. >> >> I case I want a system which can handle mainly 64-bit programs and on >> occasion a 32-bit program, I need the two libraries separated. This >> applies of course also for the root based /lib and /lib64 directories. >> >> I tried giving the parameter '--libdir=/usr/lib64' to the configure >> script. But I see at the end of chapter 5, that the 64-bit library was >> riddled with links to the 32-bit library. This is not a problem as long >> as it affects only the programs in the /tools directory, but I saw the >> same at the root. >> >> I searched the document, but could not find a way to solve this. Could >> someone give me a pointer where I might have gone wrong or what else I >> can/should do? >> >> Regards, Frans. >> > > Bruce already responded, but as a side note, you can use /lib32 and > /usr/lib32 for 32bit libraries on 64bit OS where /lib64 /usr/lib64 is > symlink to /lib and /usr/lib respectively. > Yes, that thought had occurred to me too.
By the way, I looked at the CLFS site and see that things are not that different only that they are a couple of versions behind. That said, I think I will try sometime their ideas and incorporated it with the running LFS. Until then, I keep a watchful eye on them and continue with the LFS project. After-all, with the current hardware it's quite easy to have VM's running 32/64-bit systems. So if in need of a 32-bit system on my 64-bit systems, I'll use a VM for now. Sorry Bruce, I am not out of your hair yet...;) Regards, Frans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
