This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.
- From: Rask Ingemann Lambertsen <rask at sygehus dot dk>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, newlib at sourceware dot org
- Date: Fri, 1 Jun 2007 11:47:32 +0200
- Subject: Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.
- References: <200604190055.k3J0t3UF032396@greed.delorie.com> <20070531111003.GV5690@sygehus.dk> <200705311603.l4VG3LH7013326@greed.delorie.com>
On Thu, May 31, 2007 at 12:03:21PM -0400, DJ Delorie wrote:
>
> > Why don't we do this for all the newlib targets, instead of just
> > for m32c-*-*? Is there a particular reason for not doing so when
> > --with-newlib is specified?
>
> Not all targets have their files in the same location, but otherwise,
> I suppose we could add *some* generalization here.
The libgloss configure script knows how to map a target triplet into a
subdirectory name. Is there a way of getting access to that information from
the top level configure script?
--
Rask Ingemann Lambertsen