From: Robert Millan <zeratul2@wanadoo.es>
To: gdb@sources.redhat.com
Cc: glibc-bsd-hackers@nongnu.org
Subject: GNU/K*BSD port
Date: Sun, 07 Dec 2003 21:23:00 -0000 [thread overview]
Message-ID: <20031207211831.GA2058@aragorn> (raw)
Hi!
I'm trying to fix gdb for GNU/K*BSD systems (GNU userland and libc on kernels
of *BSD). I have a semi-working patch that fixes triplet detection, but when
trying to build the file "gdb/i386bsd-nat.c", I encounter build errors. I'm
not sure if that is really the file we should be compiling.
The header description in that file says it contains "Native-dependent code
for modern i386 BSD's". Does it apply for GNU/K*BSD? I.e, is it specific to
the kernel or rather to ld.so, libc or other userland component?
Thanks,
--
Robert Millan
"[..] but the delight and pride of Aule is in the deed of making, and in the
thing made, and neither in possession nor in his own mastery; wherefore he
gives and hoards not, and is free from care, passing ever on to some new work."
-- J.R.R.T, Ainulindale (Silmarillion)
reply other threads:[~2003-12-07 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031207211831.GA2058@aragorn \
--to=zeratul2@wanadoo.es \
--cc=gdb@sources.redhat.com \
--cc=glibc-bsd-hackers@nongnu.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