9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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
Date: Sun, 10 Jun 2007 11:44:27 -0600	[thread overview]
Message-ID: <B8645BA7-F89A-4441-875E-238DB8B694DF@tinker.com> (raw)
In-Reply-To: <3451faeb5a5ae292da87b275fd80bcd1@terzarima.net>

On Jun 10, 2007, at 11:27 AM, Charles Forsyth wrote:

>> Any enlightenment would be appreciated.
>
> cpp doesn't understand -.
>

Yes, the reason I put -. in CFLAGS is because it is a
parameter to the C compiler.  However, I have tried it
with and without -. and with and without -N.  I have
also tried the following command:

cpp -N ../main.c

It correctly does not find any of the include files.  But,
if I try:

cpp -N -I/sys/include -I/386/include ../main.c

It finds all of the include files.  It should not be
finding inc1.h or inc2.h if I read the man page correctly.
It finds both of these files in ..

This seems like a bug to me.

Kim



  reply	other threads:[~2007-06-10 17:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 16:35 [9fans] trouble with include order using c compiler with ansi preprocessor 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 [this message]
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
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=B8645BA7-F89A-4441-875E-238DB8B694DF@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).