public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sdack@anitesystems.de
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/6598: configure identifies old/broken gcc as gcc and passes unknown options
Date: Tue, 07 May 2002 11:06:00 -0000	[thread overview]
Message-ID: <20020507180246.15691.qmail@sources.redhat.com> (raw)


>Number:         6598
>Category:       bootstrap
>Synopsis:       configure identifies old/broken gcc as gcc and passes unknown options
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 07 11:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Sven Dack
>Release:        gcc-3.0.4
>Organization:
>Environment:
m88k-motorola-sysv4
>Description:
Motorola ships their boxes with SVR4 and a master piece of compiler suite which is basically a GNU cc with their own assembler and linker but a broken 'cc' frontend. The compiler identifies itself as the GNU compiler through the builtin defines but doesn't accept all command line options. They even scratched --help and --version :-(. '-g' and '-O' works, -Wall doesn't which gets complained about during the bootstrap.
Now the problem is, that the usual configure script identifies this as a gcc but I think it rather shouldn't.

It actually is a gcc-2.2.2 or 2.4.5. Not very clear. It does compile things.
>How-To-Repeat:
Apply for a job at our company and make gcc run on m88k.
>Fix:
Have a configure option which disables checking of 'cc' beeing a GNU cc (and rather assume the worst).
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-05-07 18:06 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=20020507180246.15691.qmail@sources.redhat.com \
    --to=sdack@anitesystems.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: 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).