This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] GCC multilib vs. OS multilib naming (take 2)
- From: Andreas Jaeger <aj at suse dot de>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, rth at redhat dot com
- Date: Fri, 04 Oct 2002 08:14:17 +0200
- Subject: Re: [PATCH] GCC multilib vs. OS multilib naming (take 2)
- References: <20021003172638.S3451@sunsite.ms.mff.cuni.cz>
Jakub Jelinek <jakub@redhat.com> writes:
> Hi!
>
> There were some crt*.o search buglets in the last patch and also it handled
> sparc64-linux only.
> This version should do the job for other targets too.
> Bootstrapped/regression tested on sparc64-linux. Also did a bunch of strace
> runs on /usr/bin/gcc built by that to see whether it
> is doing the right thing.
> Ok to commit?
>
> 2002-10-03 Jakub Jelinek <jakub@redhat.com>
>
> * gcc.c (print_multi_os_directory): New variable.
> (option_map): Support --print-multi-os-directory.
Shouldn't this new flag get documented in the manual?
[...]
> --- gcc/config/i386/t-linux64.jj 2002-05-27 20:55:55.000000000 +0200
> +++ gcc/config/i386/t-linux64 2002-10-01 00:16:43.000000000 +0200
> @@ -6,10 +6,9 @@ SHLIB_MAPFILES = $(srcdir)/libgcc-std.ve
>
> MULTILIB_OPTIONS = m64/m32
> MULTILIB_DIRNAMES = 64 32
> +MULTILIB_OSDIRNAMES = ../lib64 ../lib32
Why lib32? 32-bit libraries will go into lib. I can commit the
obvious patch but first like to hear what the reasoning is behind
lib32.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj