This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] GNU/k*BSD support (with ChangeLog) for gcc
- From: "David O'Brien" <obrien at FreeBSD dot org>
- To: Robert Millan <zeratul2 at wanadoo dot es>
- Cc: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>, gcc-patches at gcc dot gnu dot org, glibc-bsd-hackers at nongnu dot org
- Date: Fri, 19 Mar 2004 08:14:52 -0800
- Subject: Re: [PATCH] GNU/k*BSD support (with ChangeLog) for gcc
- Organization: The NUXI BSD Group
- References: <email@example.com> <200403160425.i2G4PHcH067996@latour.rsch.comm.mot.com> <20040316210658.GB4558@aragorn>
- Reply-to: obrien at FreeBSD dot org
On Tue, Mar 16, 2004 at 10:06:58PM +0100, Robert Millan wrote:
> Yes. __FreeBSD__ implies a FreeBSD kernel, but it does also imply FreeBSD
> userland and, most importantly, FreeBSD linker and FreeBSD C library.
> Thus, it is reasonable that many programs use __FreeBSD__ to check for
> FreeBSD C library or FreeBSD dynamic linker.
> Our system, however, uses GNU libc and not FreeBSD libc. The only component
> it shares with FreeBSD is the kernel. Therefore, we need a new macro for
> the kernel, that can be shared with pure FreeBSD systems, but is not tied
> to other userland components like __FreeBSD__ is.
I'm sorry, but I still don't see the need for an additional symbol to
__FreeBSD__. Can you show a small example of why it is needed?
-- David (obrien@FreeBSD.org)