From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: eliz@gnu.org, mark.kettenis@xs4all.nl, denis.pilat@st.com,
gdb-patches@sourceware.org
Subject: Re: [RFA] gdb is broken: missing signal.h checking
Date: Fri, 30 Mar 2007 18:53:00 -0000 [thread overview]
Message-ID: <200703301853.l2UIrTSg009986@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070330121226.GB7415@caradoc.them.org> (message from Daniel Jacobowitz on Fri, 30 Mar 2007 08:12:26 -0400)
> Date: Fri, 30 Mar 2007 08:12:26 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, Mar 30, 2007 at 03:01:01PM +0300, Eli Zaretskii wrote:
> > > Date: Thu, 29 Mar 2007 13:48:08 -0400
> > > From: Daniel Jacobowitz <drow@false.org>
> > > Cc: Denis PILAT <denis.pilat@st.com>, gdb-patches <gdb-patches@sourceware.org>
> > >
> > > GDB definitely does not support systems without <signal.h>, but
> > > gdbserver now tries to.
Aha, missed that bit of detail I guess.
> > Then perhaps we should add this information to gdb/README: it now
> > explicitly says that an ISO C compiler is required, without
> > qualifications.
>
> I believe some projects (binutils and gcc maybe?) draw a distinction
> between "an ISO C compiler" and "an ISO C standard library" and
> require the former but not the latter.
The distinction is "Freestanding" versus "Hosted" I believe.
Obviously GDB requires the latterm but I can see people wanting to
support the former for gdbserver.
> I assume we require an ISO C runtime for the rest of GDB. If that's
> true, then how about the attached patch?
Effectively we do. Or at least I think we should. We made some
exceptions in the past for specific targets that had an almost ISO C
compatible runtime (SunOS, Ultrix) but we no longer support those.
This diff looks fine to me.
> 2007-03-30 Daniel Jacobowitz <dan@codesourcery.com>
>
> * README: Mention ISO C library requirement.
>
> Index: README
> ===================================================================
> RCS file: /cvs/src/src/gdb/README,v
> retrieving revision 1.38
> diff -u -p -r1.38 README
> --- README 21 Nov 2006 05:12:44 -0000 1.38
> +++ README 30 Mar 2007 12:11:32 -0000
> @@ -87,7 +87,9 @@ Bugs' section below; there are a few kno
> GDB requires an ISO C (ANSI C) compiler. If you do not have an ISO
> C compiler for your system, you may be able to download and install
> the GNU CC compiler. It is available via anonymous FTP from the
> -directory `ftp://ftp.gnu.org/pub/gnu/gcc'.
> +directory `ftp://ftp.gnu.org/pub/gnu/gcc'. GDB also requires an ISO
> +C standard library. The GDB remote server, gdbserver, builds with some
> +non-ISO standard libraries - e.g. for Windows CE.
>
> GDB uses Expat, an XML parsing library, to implement some target-specific
> features. Expat will be linked in if it is available at build time, or
>
next prev parent reply other threads:[~2007-03-30 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 15:07 Denis PILAT
2007-03-29 15:12 ` Daniel Jacobowitz
2007-03-29 15:25 ` Denis PILAT
2007-03-29 17:41 ` Mark Kettenis
2007-03-29 17:48 ` Daniel Jacobowitz
2007-03-30 12:01 ` Eli Zaretskii
2007-03-30 12:12 ` Daniel Jacobowitz
2007-03-30 12:23 ` Eli Zaretskii
2007-03-30 12:58 ` Daniel Jacobowitz
2007-03-30 12:23 ` Eli Zaretskii
2007-03-30 18:53 ` Mark Kettenis [this message]
2007-03-30 19:01 ` Daniel Jacobowitz
2007-03-30 21:04 ` Jim Blandy
2007-03-30 21:13 ` Daniel Jacobowitz
2007-03-29 20:37 ` Pedro Alves
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=200703301853.l2UIrTSg009986@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=denis.pilat@st.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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