This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Configuring gcc for pure 64bit x86_64
On Monday 29 Nov 2004 14:06, Andreas Jaeger wrote:
> Andrew Walrond <andrew@walrond.org> writes:
> > On Monday 29 Nov 2004 12:37, Andreas Jaeger wrote:
> >> Andrew Walrond <andrew@walrond.org> writes:
> >> > I want to build a pure 64bit gcc on x86_64, with the 64bit gcc libs
> >> > ending up in /lib rather than the /lib /lib64. I am not interested in
> >> > the -m32 capability.
> >> >
> >> > Is this possible/easy? I would accept /lib32 /lib as an alternative if
> >> > a pure 64bit gcc is not easy to achieve.
> >> >
> >> > Any help appreciated. Google didn't help this time :(
> >>
> >> Try --disable-multilib,
> >
> > Tried that, but I still get a /lib64 directory containing
> > libgcc_s.so libgcc_s.so.1
> >
> > I also use --with-slibdir=/lib to no avail.
> >
> > Are there likely to be any side affects to just moving these into /lib ?
>
> grep glibc and gcc sources for that path - and if nobody uses them
> directly (which I assume), there shouldn't be a problem.
I think it should be safe. I was suprised that --with-slibdir was broken
though.
>
> But I would really advise to use lib64 - this is the standard on AMD64
> as described also in the FHS.
Yes, I know, but I don't agree with it. It should, logically and aesthetically
have been standardised as /lib with /lib32 for legacy 32bit libs.
Consider the (much older) fhs description of /lib:
"The /lib directory contains those shared library images needed to boot the
system and run the commands in the root filesystem, ie. any binaries in /bin
and /sbin"
Ho hum ;)
Andrew Walrond