public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
To: gcc-gnats@gcc.gnu.org
Cc: beebe@math.utah.edu, sysstaff@math.utah.edu
Subject: bootstrap/5869: gcc-20020304 bootstrap fails on DEC Alpha OSF/1 4.0 because of gcc-specific compiler flags passed to native compiler
Date: Thu, 07 Mar 2002 08:06:00 -0000	[thread overview]
Message-ID: <CMM.0.92.0.1015516994.beebe@suncore.math.utah.edu> (raw)


>Number:         5869
>Category:       bootstrap
>Synopsis:       gcc-20020304 bootstrap fails on DEC Alpha OSF/1 4.0 because of gcc-specific compiler flags passed to native compiler
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 07 08:06:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Nelson H. F. Beebe
>Release:        3.1 20020304 (prerelease)
>Organization:
Department of Mathematics, University of Utah
>Environment:
	DEC Alpha 4100-5/466 (4 CPUs, 466 MHz, 2GB RAM);          OSF/1 4.0F
	% uname -a
	OSF1 XXXXXX.math.utah.edu V4.0 1229 alpha alpha

host: alphaev56-dec-osf4.0f
build: alphaev56-dec-osf4.0f
target: alphaev56-dec-osf4.0f
configured with: ../gcc-20020304/configure --prefix=/usr/local/test --enable-cpplib --enable-libgcj --enable-shared --enable-version-specific-runtime-libs --with-local-prefix=/usr/local --enable-threads
>Description:
cc -DIN_GCC -g -O2 -L/usr/local/lib -W -Wall -Wwrite-strings \
	-Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H \
	-DGENERATOR_FILE -I. -If -I../../gcc-20020304/gcc \
	-I../../gcc-20020304/gcc/f -I../../gcc-20020304/gcc/config \
	-I../../gcc-20020304/gcc/../include -c  \
	../../gcc-20020304/gcc/f/fini.c -o f/fini.o
cc: Error: Syntax error on -W switch:  form is -Wpassname,switch

The options -W -Wall -Wwrite-strings are gcc specific, and they CANNOT
be used with other compilers!  When a native compiler is available, I
never bootstrap a gcc build with an older version of gcc: doing so is
less of a validation test than with using an alternate compiler.

>How-To-Repeat:
env CC=cc ../gcc-20020304/configure \
	--prefix=/usr/local/test \
	--enable-cpplib \
	--enable-libgcj \
	--enable-shared \
	--enable-version-specific-runtime-libs \
	--with-local-prefix=/usr/local &&
		make bootstrap

>Fix:

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- Center for Scientific Computing       FAX: +1 801 585 1640, +1 801 581 4148 -
- University of Utah                    Internet e-mail: beebe@math.utah.edu  -
- Department of Mathematics, 110 LCB        beebe@acm.org  beebe@computer.org -
- 155 S 1400 E RM 233                       beebe@ieee.org                    -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe  -
-------------------------------------------------------------------------------
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-03-07 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07  8:06 Nelson H. F. Beebe [this message]
2002-03-07  8:56 Zack Weinberg
2002-03-07  9:46 Zack Weinberg
2002-03-19  1:07 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=CMM.0.92.0.1015516994.beebe@suncore.math.utah.edu \
    --to=beebe@math.utah.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=sysstaff@math.utah.edu \
    /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).