This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: lib64 and --disable-multilib
- From: Andrew Haley <aph at redhat dot com>
- To: Shaun Jackman <sjackman at gmail dot com>
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Wed, 10 Sep 2014 09:12:19 +0100
- Subject: Re: lib64 and --disable-multilib
- Authentication-results: sourceware.org; auth=none
- References: <CADX6M3qTU-0q0RuSXgo5z2jBXQywJU5aei6tz+p5--6NHgvd7w at mail dot gmail dot com> <540F428D dot 9010802 at redhat dot com> <CADX6M3oVS0=jgG8piihWy_wLGyb85wkzotRczdZZy_WONPfrDg at mail dot gmail dot com>
Hi,
On 09/09/14 21:04, Shaun Jackman wrote:
> On 9 September 2014 11:10, Andrew Haley <aph@redhat.com> wrote:
>> On 09/09/2014 06:57 PM, Shaun Jackman wrote:
>>> Hi. I compiled gcc with --disable-multilib on an x86-64 system and
>>> expected GCC libraries to be installed in $prefix/lib, but found them
>>> instead installed in $prefix/lib64.
>>
>> That's right: it's the standard place for 64-bit x86-64 libraries.
>>
>>> Is there a configure option to
>>> override this behaviour and install libraries in $prefix/lib? If not,
>>> should simply moving the libraries to $prefix/lib work?
>
> I understand lib64 has a vital purpose on a multilib system. On a
> non-multilib system, it seems odd to me to have a populated lib64
> directory and an empty lib directory. It's tidier (in my opinion) to
> just name the directory lib.
Sure, but it's nonstandard. You should just do what Debian do, and
symlink lib and lib64.
> Most open-source software after `./configure && make install` install
> libraries into $prefix/lib, not $prefix/lib64. I installed 139 open
> source packages on this system, and only four packages installed
> libraries in lib64: gcc, git, libffi and r.
Well, those packages are broken. I'm surprised that there are so many
packages out there which still haven't been fixed. Standards exist
for a reason.
Andrew.