From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: GDB doesn't compile on GNU/Linux
Date: Tue, 28 Nov 2006 21:37:00 -0000 [thread overview]
Message-ID: <17772.43776.133395.659031@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061128212116.GA32731@nevyn.them.org>
Daniel Jacobowitz writes:
> On Wed, Nov 29, 2006 at 10:07:06AM +1300, Nick Roberts wrote:
> > 2006-11-29 Nick Roberts <nickrob@snap.net.nz>
> >
> > * linux-thread-db.c: Include <signal.h>.
>
> OK. Wonder what implicitly pulled it in where Ulrich tested, but
> it's not worth finding out.
In his case, linux-thread-db.c probably didn't get rebuilt after his changes.
Nothing in the Makefile seems to depend on nm-linux.h. I probably hadn't
updated this checkout since before 2006-10-19.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-11-28 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 21:11 Nick Roberts
2006-11-28 21:21 ` Daniel Jacobowitz
2006-11-28 21:34 ` Ulrich Weigand
2006-11-28 21:37 ` Nick Roberts [this message]
2006-11-28 21:46 ` Ulrich Weigand
2006-11-28 21:48 ` Daniel Jacobowitz
2006-11-28 21:59 ` Ulrich Weigand
2006-11-28 21:57 ` Nick Roberts
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=17772.43776.133395.659031@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--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