From: Kim Shrier <kim@tinker.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] trouble with include order using c compiler with ansi preprocessor
Date: Sun, 10 Jun 2007 13:24:33 -0600 [thread overview]
Message-ID: <A1F843CD-7E73-4402-8F6B-81919458FDC2@tinker.com> (raw)
In-Reply-To: <20070610181019.GA2034@shodan.homeunix.net>
On Jun 10, 2007, at 12:10 PM, Martin Neubauer wrote:
> The way I understand the man page, the -N option just suppresses the
> predefined include paths. What you seem to want ist the -. option
> which, as
> Charles mentioned, cpp does not support. But as I see it all of those
> options really should be necessary in but very isolated cases. You
> might
> consider reorganising your header files. Otherwise you'll end up
> with those
> horrible compiling commands that are so common in modern Unix[sic].
>
> Martin
You're right. I should approach this problem differently.
I need to get out of the UNIX mind set.
Kim
next prev parent reply other threads:[~2007-06-10 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 16:35 Kim Shrier
2007-06-10 17:27 ` [9fans] trouble with include order using c compiler with ansi Charles Forsyth
2007-06-10 17:44 ` Kim Shrier
2007-06-10 18:10 ` [9fans] trouble with include order using c compiler with ansi preprocessor Martin Neubauer
2007-06-10 19:24 ` Kim Shrier [this message]
2007-06-10 19:26 ` erik quanstrom
2007-06-10 20:07 ` Russ Cox
2007-06-10 20:44 ` Kim Shrier
2007-06-10 22:02 ` Uriel
2007-06-10 22:47 ` Kim Shrier
2007-06-11 0:10 ` Kris Maglione
2007-06-11 1:41 ` Kim Shrier
2007-06-11 7:51 ` Steve Simon
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=A1F843CD-7E73-4402-8F6B-81919458FDC2@tinker.com \
--to=kim@tinker.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).