public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: thor@sh-home.de To: gcc-gnats@gcc.gnu.org Subject: c/4139: problem using -V Date: Mon, 27 Aug 2001 08:16:00 -0000 [thread overview] Message-ID: <20010827171129.A19365@nubis.osiris.home> (raw) >Number: 4139 >Category: c >Synopsis: gcc -V 2.95.x fails on comments and preprocessor directives >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Mon Aug 27 08:16:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: >Release: 3.0.1 >Organization: >Environment: System: Linux nubis 2.4.9 #1 Tue Aug 21 19:58:29 CEST 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 --enable-shared +--with-gnu-as --with-gnu-ld --enable-threads --enable-cpp >Description: gcc and g++ output parse erros for every /* or // found in the source. Preprocessor directives will result in 'undefined or invalid # +directive' >How-To-Repeat: /* comment */ int main(){} gcc -V 2.95.3 -o test test.c test.c:1: parse error before `/' ------------------ #include <stdio.h> int main(){} gcc -V 2.95.3 -o test test.c test.c:1: undefined or invalid # directive gcc -V 2.95.3 -E -o test.i test.c gcc -V 2.95.3 -o test test.i cc1: Invalid option `-fpreprocessed' >Fix: -- nubis thor@sh-home.de Mommy, what does "Formatting Drive C:" mean? >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-08-27 8:16 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=20010827171129.A19365@nubis.osiris.home \ --to=thor@sh-home.de \ --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: linkBe 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).