From: Rick Richardson <rickr@mn.rr.com>
To: GDB Mailing List <gdb@sources.redhat.com>
Subject: gdb retargetting
Date: Wed, 14 Aug 2002 09:05:00 -0000 [thread overview]
Message-ID: <20020814110514.A28654@mn.rr.com> (raw)
Maybe someone can help me, maybe not. Here's the deal:
1) I retargetted binutils to support a new processor. I started with
binutils-2.12.1 from the GNU ftp site. That work is complete.
2) I grabbed gdb-5.2.1 and merged the gdb directories with my now-modified
binutils tree. This meant I just copied the gdb, malloc, readline, sim,
and utils directories from the gdb tree to the combined tree.
3) As a check that everything is buildable in the combined tree, I
configured for i386 (default) on linux, and did a "make". I wanted
to make sure that I started from a buildable tree before I hack on
the gdb and sim directories to support the new processor.
4) Everything built fine until it got to gdb/gdbserver. It exploded
compiling utils.c:
In file included from utils.c:22:
server.h:37:25: gdb/signals.h: No such file or directory
5) No question, there is no gdb/signals.h included in the gdb-5.2.1.tar.gz
file that I got from ftp.gnu.org. Nor is there one in gdb-5.2.tar.gz.
What gives? I'm beginning to suspect that nobody compiles the
snapshots on the GNU ftp site. Should I have started from some other
snapshots? I'm completely learing of basing off of "the tip" of the
CVS tree, as I have no idea when that is stable. So I thought basing
off of the GNU snapshots would be the way to go.
-Rick
--
Rick Richardson rickr@mn.rr.com http://home.mn.rr.com/richardsons/
Stock information at your fingertips: http://linuxtrade.0catch.com/
In its earliest years, access to Usenet required "Level 5 geek
clearance". The same people that could get a feed also could get
marijuana. -- Richard Sexton
next reply other threads:[~2002-08-14 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 9:05 Rick Richardson [this message]
2002-08-14 9:11 ` Daniel Jacobowitz
2002-08-14 9:27 ` Rick Richardson
2002-08-17 22:54 ` Andrew Cagney
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=20020814110514.A28654@mn.rr.com \
--to=rickr@mn.rr.com \
--cc=gdb@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