From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com, dj@delorie.com
Subject: Re: [RFA] Type cleanups
Date: Fri, 17 May 2002 08:02:00 -0000 [thread overview]
Message-ID: <20020517150244.GA8388@nevyn.them.org> (raw)
In-Reply-To: <6480-Fri17May2002110920+0300-eliz@is.elta.co.il>
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
next prev parent reply other threads:[~2002-05-17 15:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40 ` Daniel Jacobowitz
2002-05-12 21:31 ` Andrew Cagney
2002-05-13 11:46 ` Daniel Jacobowitz
2002-05-13 12:54 ` Daniel Berlin
2002-05-13 12:57 ` Daniel Jacobowitz
2002-05-13 6:59 ` Daniel Jacobowitz
2002-05-13 8:37 ` Andrew Cagney
2002-05-13 8:51 ` Elena Zannoni
2002-05-13 9:11 ` Andrew Cagney
2002-05-13 9:19 ` Elena Zannoni
2002-05-13 11:50 ` Daniel Jacobowitz
2002-05-13 11:59 ` Daniel Jacobowitz
2002-05-13 15:14 ` Andrew Cagney
2002-05-13 16:09 ` Daniel Jacobowitz
2002-05-13 18:37 ` Elena Zannoni
2002-05-14 17:09 ` Andrew Cagney
2002-05-17 1:11 ` Eli Zaretskii
2002-05-17 8:02 ` Daniel Jacobowitz [this message]
2002-05-17 9:14 ` Eli Zaretskii
2002-05-17 10:21 ` Daniel Jacobowitz
2002-05-17 10:34 ` Andrew Cagney
2002-05-18 0:15 ` Eli Zaretskii
2002-05-18 0:13 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020517150244.GA8388@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=dj@delorie.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox