public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: preprocessor/2948
Date: Sun, 27 May 2001 00:46:00 -0000 [thread overview]
Message-ID: <20010527074600.9978.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR preprocessor/2948; it has been noted by GNATS.
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Sean McNeil <sean@mcneil.com>
Cc: neil@gcc.gnu.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: preprocessor/2948
Date: Sun, 27 May 2001 08:39:49 +0100
Sean McNeil wrote:-
> 2 stage command:
>
> arm-wrs-vxworks-g++ -E -mcpu=arm8 -mapcs-32 -mlittle-endian -ansi
> -nostdinc -fno-implicit-templates -DVXW_EXPLICIT_TEMPLATES -O2
> -mno-sched-prolog -I/usr/wind/target/h -DCPU=ARMARCH4 -DARMEL
> -fno-exceptions -o /tmp/ttt.cc -c PlotFile.cpp
>
> arm-wrs-vxworks-g++ -mcpu=arm8 -mapcs-32 -mlittle-endian -ansi -nostdinc
> -fno-implicit-templates -DVXW_EXPLICIT_TEMPLATES -O2 -mno-sched-prolog
> -I/usr/wind/target/h -DCPU=ARMARCH4 -DARMEL -fno-exceptions -o
> /tmp/ttt.o /tmp/ttt.cc
Could you try naming your intermediate file ttt.ii? This is the
convention for C++ preprocessed source. Naming it ttt.cc informs the
compiler that it is unpreprocessed source for the 2nd invocation too,
which could be what is causing the problems.
Neil.
next reply other threads:[~2001-05-27 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 0:46 Neil Booth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-29 18:26 preprocessor/2948 Sean McNeil
2001-05-29 18:06 preprocessor/2948 Sean McNeil
2001-05-29 10:26 preprocessor/2948 Neil Booth
2001-05-29 9:46 preprocessor/2948 Sean McNeil
2001-05-28 23:46 preprocessor/2948 Neil Booth
2001-05-28 18:56 preprocessor/2948 Sean McNeil
2001-05-28 15:26 preprocessor/2948 Neil Booth
2001-05-27 10:36 preprocessor/2948 Sean McNeil
2001-05-26 8:46 preprocessor/2948 Sean McNeil
2001-05-26 1:16 preprocessor/2948 neil
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=20010527074600.9978.qmail@sourceware.cygnus.com \
--to=neil@daikokuya.demon.co.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).