public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: juergen@monocerus.demon.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/4075: gcc-3.0.1 - -V... not working
Date: Tue, 21 Aug 2001 16:46:00 -0000 [thread overview]
Message-ID: <m15ZL3l-0003jIC@monocerus.demon.co.uk> (raw)
>Number: 4075
>Category: preprocessor
>Synopsis: Specifying a different version does not work
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Aug 21 16:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Juergen Heinzl
>Release: 3.0.1
>Organization:
>Environment:
System: Linux monocerus.demon.co.uk 2.2.19 #1 Mon Mar 26 21:18:17 BST 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.0.1/configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --enable-threads --enable-languages=c,c++ --disable-nls
>Description:
Invoking gcc with the -V option results in an error message
"file.c:(n): undefined or invalid # directive" where (n) is
the line number of some include directive.
>How-To-Repeat:
echo '#include <stdio.h>' > foo.c
gcc -V2.95.3 foo.c
... or worse ...
gcc -V2.7.2.3 foo.c
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2001-08-21 16:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m15ZL3l-0003jIC@monocerus.demon.co.uk \
--to=juergen@monocerus.demon.co.uk \
--cc=gcc-gnats@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).