public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Pete Chown <pc@flinnel.demon.co.uk> To: gcc-gnats@gcc.gnu.org Subject: fortran/4279: "g77 -h" gives bogus output Date: Sun, 09 Sep 2001 15:36:00 -0000 [thread overview] Message-ID: <E15gD7B-0000KG-00@flinnel.demon.co.uk> (raw) >Number: 4279 >Category: fortran >Synopsis: "g77 -h" gives bogus output >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Sep 09 15:36:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Pete Chown >Release: 3.0.1 >Organization: none >Environment: System: Linux flinnel.demon.co.uk 2.4.8 #1 Tue Aug 14 19:43:28 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/local/gcc3 >Description: Typing "g77" on it's own does this: % g77 g77: No input files This is correct behaviour (obviously). Typing "g77 -h" gives this: % g77 -h g77: unrecognized option `-h' /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x18): undefined reference to `main' collect2: ld returned 1 exit status I don't feel this is correct. After receiving an invalid option, g77 should either stop or ignore the option it didn't know about. Also the GNU coding standard says that -h is an alias for --help which does produce the expected output. Hardly an important bug but it should be simple to fix when someone has a bit of time. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-09-09 15:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-09 15:36 Pete Chown [this message] 2001-09-29 7:23 toon 2001-11-19 0:56 toon 2001-11-19 3:26 toon
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=E15gD7B-0000KG-00@flinnel.demon.co.uk \ --to=pc@flinnel.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: 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).