public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13877] gdb7.4 doesn't build on FreeBSD ia64
Date: Thu, 29 Mar 2012 09:58:00 -0000 [thread overview]
Message-ID: <bug-13877-4717-i8vGAfskn4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13877-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13877
--- Comment #6 from Pedro Alves <palves at redhat dot com> 2012-03-29 09:57:34 UTC ---
See "Adding a New Host" in the "GDB Internals" manual. Basically, these are
makefile fragments, that the main Makefile sources in order to include objects
and definitions that only make sense for a particular host. Among these
objects would be a new ia64-fbsd-nat.o object. Of course, the corresponding
ia64-fbsd-nat.c would need to be written. This file would contain the glue
between common FreeBSD bits, and IA64 specifics. Best see one of the existing
ports, and model on it. See config/i386/fbsd64.mh, for the x86_64 FreeBSD one.
If you're interested in doing this, please do see the CONTRIBUTE file as linked
by <http://sourceware.org/gdb/contribute/>.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
prev parent reply other threads:[~2012-03-29 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 10:46 [Bug gdb/13877] New: gdb coredumps " mexas at bristol dot ac.uk
2012-03-28 18:28 ` [Bug gdb/13877] " tromey at redhat dot com
2012-03-29 8:56 ` [Bug gdb/13877] gdb7.4 doesn't build " mexas at bristol dot ac.uk
2012-03-29 9:05 ` mexas at bristol dot ac.uk
2012-03-29 9:20 ` palves at redhat dot com
2012-03-29 9:43 ` mexas at bristol dot ac.uk
2012-03-29 9:58 ` palves at redhat dot com [this message]
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=bug-13877-4717-i8vGAfskn4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).