This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.

From: DJ Delorie <dj at redhat dot com>
To: sjackman at gmail dot com
Cc: gcc-patches at gcc dot gnu dot org, newlib at sourceware dot org
Date: Wed, 19 Apr 2006 16:33:56 -0400
Subject: Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.
References: <200604190055.k3J0t3UF032396@greed.delorie.com> <7f45d9390604191327h2d190898m3c836d0996b3bd45@mail.gmail.com>

> It seems to me arm-elf --disable-newlib-supplied-syscalls has this
> issue as well. Is there a general solution?

You mean, besides --disable-libssp?  ;-)

libstdc++ doesn't have a problem.  libssp does.  Based on that fact
alone, I'd claim libssp is broken, or trying too hard to be clever
about shared libraries.  The other libraries use GCC_NO_EXECUTABLES,
which avoids the whole I-cant-link-yet problem.

Anyone know why libssp has to test-build shared libraries?

References:
- [m32c] build libstdc++; combined builds, libssp, and libgloss.
  - From: DJ Delorie
- Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.
  - From: Shaun Jackman

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]