This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Building mips*-linux-gnu using --with-newlib
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Sun, 19 Oct 2003 19:51:40 -0400
- Subject: Re: Building mips*-linux-gnu using --with-newlib
- References: <wvnptgt2g51.fsf@talisman.cambridge.redhat.com>
On Sun, Oct 19, 2003 at 08:15:22PM +0100, Richard Sandiford wrote:
> Dunno how standard this is, but I tend to build a mips*-linux-gnu
> sysroot as follows:
>
> - build a bare-bones gcc, configured using:
> --with-newlib --disable-shared --disable-threads
> --enable-languages=c
> - use it to build & install glibc
> - build a full compiler, no special configure options
> - use it to build the rest of the sysroot
>
> The point of --with-newlib is to stop libgcc including any system
> header files since they aren't available until glibc is installed.
>
> Anyway, this no longer works with the new definition of
> MD_FALLBACK_FRAME_STATE_FOR. libgcc will unconditionally
> include <signal.h>.
>
> Is it OK to apply the patch below to get around this? It seems safe,
> but I notice most other ports don't do this.
Richard's said in the past, IIRC, that this isn't the right way to do
it. Use glibc's make install-headers instead. Of course, make
install-headers has lots of its own deficiencies.
Also, as Chris pointed out, you may or may not (depending on exact
glibc version and phase of moon) get a copy of the unwind routines
which don't support MD_FALLBACK_FRAME_STATE_FOR linked into the built
library. That's bad :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer