On Aug 3, 2013, at 12:24, Nathan Coulson wrote:
> Not much out there even looks for the lib64 folder
Greetings,
Except the linker when using gcc which will default to m64 during x86_64 builds
and use lib64 unless LFS is made to be a pure 64bit system and adjust gcc specs
config to use lib o
On Sat, Aug 3, 2013 at 6:15 AM, Michael E. Maher
wrote:
> On Sat, 2013-08-03 at 07:53 +0200, Aleksandar Kuktin wrote:
>> >On Fri, 02 Aug 2013 19:52:19 -0700
>> >Bryan Kadzban wrote:
>>
>> > Yeah, there are a few packages I've run into that do "if config.guess
>> > says something that looks like x
On Sat, 2013-08-03 at 07:53 +0200, Aleksandar Kuktin wrote:
> >On Fri, 02 Aug 2013 19:52:19 -0700
> >Bryan Kadzban wrote:
>
> > Yeah, there are a few packages I've run into that do "if config.guess
> > says something that looks like x86_64, use lib64". Which is exactly
> > the right thing to do
>On Fri, 02 Aug 2013 19:52:19 -0700
>Bryan Kadzban wrote:
> Yeah, there are a few packages I've run into that do "if config.guess
> says something that looks like x86_64, use lib64". Which is exactly
> the right thing to do for an x86_64 system, actually, but the standard
> autoconf macros don't
Bryan Kadzban wrote:
> Bruce Dubbs wrote:
>> I just noticed that we do not create /usr/local/lib64. Should be make
>> /usr/local/lib64 a symlink to /usr/local/lib the way we have:
>>
>> ln -sv lib /lib64
>> ln -sv lib /usr/lib64
>>
>> What I found was that some programs (e.g. gcc) will create a se
Bruce Dubbs wrote:
> I just noticed that we do not create /usr/local/lib64. Should be make
> /usr/local/lib64 a symlink to /usr/local/lib the way we have:
>
> ln -sv lib /lib64
> ln -sv lib /usr/lib64
>
> What I found was that some programs (e.g. gcc) will create a separate
> /usr/local/lib64
