All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Christ <bryan.christ@hp.com>
To: kratzers@pa.net
Cc: linux-c-programming@vger.kernel.org
Subject: Re: standard OS defines
Date: Wed, 22 Aug 2007 14:28:17 -0500	[thread overview]
Message-ID: <46CC8E51.4050201@hp.com> (raw)
In-Reply-To: <200708221524.41782.kratzers@pa.net>

Thanks!  This list is exactly what I was looking for.  Too bad there's 
not a tool for piping to gcc--I was trying to avoid -D.

Bryan

Stephen Kratzer wrote:
> On Wednesday 22 August 2007 14:35:21 Bryan Christ wrote:
>> does anyone know where i can find a list of standardized OS defines?
>> i've come across the list below, but i haven't found an authoritative
>> resource convince me these are standard/correct.  even if they are i'm
>> sure what i've found is a just a subset of a larger list--but i don't
>> know where to look.
>>
>> __CYGWIN__
>> __NetBSD__
>> __OpenBSD__
>> __linux__
>> __sun__
> 
> Take a look at:
> info cpp "System-specific Predefined Macros"
> 
> A good list is here:
> http://predef.sourceforge.net/preos.html
> 
>> also, is there a tool that like getconf that i can use to pipe these
>> defines into gcc at compile time?
> 
> You can define macros on the command line by passing the -D flag to gcc.
> 
>> thanks in advance,
>> bryan
>> -

  reply	other threads:[~2007-08-22 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 18:35 standard OS defines Bryan Christ
2007-08-22 19:24 ` Stephen Kratzer
2007-08-22 19:28   ` Bryan Christ [this message]
2007-08-22 19:47     ` Stephen Kratzer
2007-08-22 19:48       ` Bryan Christ
2007-08-22 20:01       ` Stephen Kratzer

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=46CC8E51.4050201@hp.com \
    --to=bryan.christ@hp.com \
    --cc=kratzers@pa.net \
    --cc=linux-c-programming@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.