This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: committed: merge with libada-branch
- From: Laurent GUERBY <laurent at guerby dot net>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Arnaud Charlet <charlet at ACT-Europe dot FR>, gcc at gcc dot gnu dot org
- Date: Tue, 10 Feb 2004 20:36:36 +0100
- Subject: Re: committed: merge with libada-branch
- References: <20040210115744.A25558@dublin.act-europe.fr> <87r7x2yexs.fsf@egil.codesourcery.com>
(moved to gcc from gcc-patches)
I successfully built and tested c,ada on x86-linux by
following the new instructions (ie: not doing the previously needed
additional "make -C ada gnatlib_and_tools"). No regressions.
I hope this will make it easier for GCC people to build
and test Ada when the backend is changed :).
On Tue, 2004-02-10 at 19:20, Zack Weinberg wrote:
> So, what this gives us is a wrapper Makefile in libada/ that invokes
> gcc/Makefile to do all the work. None of the code is moved. This is
> a step forward, but the multilibs logic is very fragile, and I doubt
> it can be made to work without physically moving all of the libada
> source code into the libada directory (I could be wrong about this).
The GNAT library has always been built by first
copying ("ln -s" where available) the appropriate
set of runtime sources in a clean directory (ada/rts).
The new libada stuff works the same.
Moving the Makefile code makes sense, but I don't
see clearly the point in moving the runtime
sources around in CVS.
Is there any overview and may be detailed explanation of what
multilibs are and how they work Makefile-wise? Any way to
make use of multilibs on a regular x86-linux box?
Laurent