This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
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. But I would really advise to use lib64 - this is the standard on AMD64 as described also in the FHS. Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Attachment:
pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |