Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Feb 1997 00:20:16 +0100 (MET)
From:      Mikael Karpberg <karpen@ocean.campus.luth.se>
To:        joerg_wunsch@uriah.heep.sax.de
Cc:        obrien@freefall.freebsd.org, hackers@freebsd.org
Subject:   Re: cvs commit:  src/contrib/gcc/config/i386 freebsd-elf.h freebsd.h
Message-ID:  <199702222320.AAA09172@ocean.campus.luth.se>
In-Reply-To: <Mutt.19970222201055.j@uriah.heep.sax.de> from J Wunsch at "Feb 22, 97 08:10:55 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
According to J Wunsch:
> As David E. O'Brien wrote:
> 
> > obrien      97/02/16 12:55:34
> > 
> >   Modified:    contrib/gcc/config/i386  freebsd-elf.h freebsd.h
> >   Log:
> >   Add _BSD4_4 as a predefined symbol.
> >   Peter Dufault (dufault@hda.com) suggested this is the most approate symbol
> >   to use.
> >   
> >   2.2-R candidate.
> >   
> >   Revision  Changes    Path
> >   1.2       +1 -1      src/contrib/gcc/config/i386/freebsd-elf.h
> >   1.4       +1 -1      src/contrib/gcc/config/i386/freebsd.h
> 
> What ever came out of this discussion?  2.2 candidate, or dead end?

It's not really needed. What about:

==== myprogconfig.h ====

#if defined(FreeBSD) || defined(OpenBSD) || defined(NetBSD)
#define MYBSDDEF
#endif

========================

There you have your single define. It's very simple to do, and it works on
old versions of the OSes too.

Ofcourse, I don't think it hurts to have that _BSD4_4 define either.
Only thing it does is give a very minor polution to the define namespace.

Just my $0.02...
  /Mikael




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702222320.AAA09172>