From: mjn3@codepoet.org (Manuel Novoa III)
To: Robert de Bath <robert$@mayday.cix.co.uk>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: More dev86 changes (0.16.7)
Date: Sat, 10 Aug 2002 13:36:01 -0600 [thread overview]
Message-ID: <20020810193601.GA11440@codepoet.org> (raw)
In-Reply-To: <bdd32ab4f9e0460f@mayday.cix.co.uk>
Hello Robert,
Sorry it took so long to do some testing, but I've been swamped.
Tried to build some of my uClibc stuff and found a bug with the new cpp
that is illustrated with the following test case.
test.c:
#define X (1UL)
#if X == 0
#error this shouldn't happen
#endif
With the new cpp, what shouldn't happen... does.
Here's the output for "ncc -ansi -E test.c".
test.c:3: warning: Unexpected text following preprocessor command
test.c:5: error: #error this shouldn't happen
# 1 "test.c"
Output without -ansi is:
# 1 "test.c"
test.c:3: warning: Unexpected text following preprocessor command
test.c:5: error: #error this shouldn't happen
Also, with the old cpp one could use "-I" to not include the default
include dirs. This feature seems to be lacking in the new version.
Manuel
next prev parent reply other threads:[~2002-08-10 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 20:18 More dev86 changes (0.16.7) Robert de Bath
2002-08-02 20:24 ` Manuel Novoa III
2002-08-03 10:17 ` More dev86 changes (0.16.7) [About the optimiser] Harry Kalogirou
2002-08-03 11:01 ` Robert de Bath
2002-08-03 11:31 ` Robert de Bath
2002-08-03 12:24 ` Harry Kalogirou
2002-08-10 19:36 ` Manuel Novoa III [this message]
2002-08-10 20:28 ` More dev86 changes (0.16.7) Robert de Bath
2002-08-11 1:06 ` Manuel Novoa III
2002-08-11 16:44 ` dev86-0.16.8 cpp bugs Manuel Novoa III
2002-08-11 19:19 ` Robert de Bath
2002-08-11 20:01 ` Manuel Novoa III
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 5:21 More dev86 changes (0.16.7) Ken Martwick
2002-08-03 6:12 ` Robert de Bath
2002-08-03 17:07 Ken Martwick
2002-08-03 17:14 ` Paul Nasrat
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=20020810193601.GA11440@codepoet.org \
--to=mjn3@codepoet.org \
--cc=linux-8086@vger.kernel.org \
--cc=robert$@mayday.cix.co.uk \
/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