Re: [RFA] Type cleanups

Daniel Jacobowitz
2002-05-17T15:02:48Z

On Fri, May 17, 2002 at 11:09:20AM +0300, Eli Zaretskii wrote:
> > Date: Mon, 13 May 2002 09:59:50 -0400
> > From: Daniel Jacobowitz <drow@mvista.com>
> >
> > Several targets (i586-pc-msdosdjgpp, sparc-elf, sparc64-elf)
> > failed with this message (also JB_SP for Sparc):
> >
> > In file included from /usr/include/setjmp.h:30,
> > from ../../src-build/gdb/top.c:58:
> > /usr/include/bits/setjmp.h:31: warning: `JB_PC' redefined
> > tm.h:57: warning: this is the location of the previous definition
> > make[1]: *** [top.o] Error 1
>
> How come /usr/include/setjmp.h is being used for the DJGPP build? It
> should have used the headers from the cross-compilation toolkit,
> i.e. the headers that come with DJGPP development enviroment. And
> those don't define no steenking JB_PC.
>
> What am I missing? Are we talking about building a native DJGPP port
> of GDB, or about something else?

Cross build, not foreign host build - i.e. an i386-linux -> djgpp cross
debugger. <setjmp.h> is needed for GDB to use on its own, and does
define these constants.

--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer