This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.
- From: "Shaun Jackman" <sjackman at gmail dot com>
- To: "DJ Delorie" <dj at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, newlib at sourceware dot org
- Date: Wed, 19 Apr 2006 14:27:39 -0600
- Subject: Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.
- References: <200604190055.k3J0t3UF032396@greed.delorie.com>
- Reply-to: "Shaun Jackman" <sjackman at gmail dot com>
On 4/18/06, DJ Delorie <dj@redhat.com> wrote:
> m32c can build libstdc++-v3 now, so no reason to hold it back any more.
>
> libssp needs to link an executable during configure (which seems wrong
> to me, but outside the scope of this patch). The m32c can't link
> executables until libgloss is installed (crt0, libnosys, and r8c.ld
> are needed), and libssp can't have GCC_NO_EXECUTABLES because it needs
> to(?) test some things about shared libraries (libstdc++-v3 doesn't
> seem to have this problem).
...
It seems to me arm-elf --disable-newlib-supplied-syscalls has this
issue as well. Is there a general solution?
Cheers,
Shaun