From: Robert Millan <rmh@debian.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: neroden@twcny.rr.com, gdb-patches@sources.redhat.com,
glibc-bsd-hackers@nongnu.org
Subject: Re: [PATCH] GNU/k*BSD fixes [w/ChangeLog]
Date: Mon, 09 Aug 2004 19:19:00 -0000 [thread overview]
Message-ID: <20040809191914.GA52624@khazad.dyndns.org> (raw)
In-Reply-To: <200408091748.i79HmXOS038567@elgar.kettenis.dyndns.org>
On Mon, Aug 09, 2004 at 07:48:33PM +0200, Mark Kettenis wrote:
>
> (note: osreldate.h and sys/param.h are equivalent for this purpose)
>
> Indeed <sys/param.h> defenitely exists on all FreeBSD systems, and is
> the official way to get the defined we're talking about here.
Ok. I'll take note on this.
> Not really. I'm sort of bending the rules in i386bsd-nat.c by
> checking the version numbers. By adding more to it, I run the risk
> that people start noticing it ;-). Anyway, this code is not really
> adding any functionality. It's just a bunch of consistency checks,
> that you can perfectly well do without.
>
> [...]
>
> I'm talking about dropping support for pre-FreeBSD-BSD here, which
> actually isn't supported. I'll remove that stuff and you can forget
> about the #ifdefs.
But the macro checks indicated the check is for FreeBSD 3.x? Well, I'm
probably missing something here..
> We have libkvm, but not nlist() which is not part of Glibc. I'm considering
> adding nlist() and other functions in a compatibility library (e.g. libbsd),
> though.
>
> IIRC the Hurd once had such a compatibility library. Anyway ...
It was part of Glibc. Then it was renamed to libutil and still exists, but
with a slightly different purpose.
> But I was surprised that disabling the '#include <nlist.h>' didn't cause the
> build process to fail on missing declarations. Does bsd-kvm.c really work
> without nlist, or am I missing something?
>
> It only needs the definition of `struct nlist'. If something else
> provides that (presumably your <kvm.h> has been hacked to do that)
Heh. Actualy I hacked kvm.h myself to do precisely this (through inclussion
of some kernel headers). I just didn't remember. =)
> everything is fine. I'll add the #ifdef HAVE_NLIST_H. It can't hurt.
Ok. Please don't forget about the hunks for gdb/configure.{host,tgt}.
--
Robert Millan
(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))
next prev parent reply other threads:[~2004-08-09 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 2:20 Robert Millan
2004-08-09 6:59 ` Mark Kettenis
2004-08-09 16:32 ` Robert Millan
2004-08-09 17:48 ` Mark Kettenis
2004-08-09 19:19 ` Robert Millan [this message]
2004-08-09 21:25 ` Mark Kettenis
2004-08-09 22:34 ` Robert Millan
2004-08-09 3:59 Nathanael Nerode
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=20040809191914.GA52624@khazad.dyndns.org \
--to=rmh@debian.org \
--cc=gdb-patches@sources.redhat.com \
--cc=glibc-bsd-hackers@nongnu.org \
--cc=kettenis@chello.nl \
--cc=neroden@twcny.rr.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