Jeremy Huntwork wrote:
> Ryan Oliver wrote:
>
> [snip]
>
>
>> Just some thoughts
>>
>
> Ryan, thanks for the feedback. I don't have anything specific to say in
> connection with any of your points yet (I guess no one else does
> either), but I will be looking them over in more detail as I have a free
> moment, so I'm bookmarking this thread.
>
> Just wanted to say thanks and it was nice hearing from you again.
>
> While you are 'here' I have another question I want to throw out there
> for opinions. If and when LFS also decides to allow multilib on x86_64
> (which, more and more I'm thinking it is only the 'Right Thing' to do if
> supporting 64-bit - specifically just enough to add 32-libs and the
> ability for gcc to compile 32-bit binaries if necessary), I'm currently
> leaning towards going a different direction than Greg has done in DIY.
>
> Specifically, DIY currently has 64-bit libs in /lib64 and /usr/lib64 and
> 32-bit libs in /lib, /usr/lib. I'm guessing that this is because this is
> the logic the toolchain uses by default for search paths and requires
> less configuration of the toolchain.
>
> However, such a situation requires _more_ configuration when building
> packages, especially those that install libraries. This is because GCC
> will build 64-bit binaries and libraries by default, but the configure
> system for most packages will install by default into /lib, /usr/lib.
> There is of course the --libdir option for many packages, but this
> doesn't hold true for all. Some (like OpenSSL) will still hard-code lib
> into the build system.
>
> What I would like to see (which agrees with what the FHS seems to
> suggest, or at least lists as a possible scenario) is this:
>
> /lib64
> /lib32
> /lib -> lib64
> /usr/lib64
> /usr/lib32
> /usr/lib -> lib64
>
> This way, both libraries are clearly identified and the default location
> of lib agrees with the default architecture gcc will build for. If
> people don't like the symlink, we can always remove {/usr,}/lib64 and
> just use {/usr,}/lib for 64-bit.
>
> The only thing is that (from what I can see) this will require
> configuring GCC to search in lib32 for 32 bit libs, which it doesn't do
> by default.
>
> Thoughts?
>
> --
> JH
>
Best just keep to the standard, otherwise pre-compiled packages and out
of tree drivers (nvidia) wont work.
For multilib just follow clfs, its worked for 4+ years and it keeps
things consistent.
Best Regards
[R}
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
