This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: bootstrap/2670
- To: nobody at gcc dot gnu dot org
- Subject: Re: bootstrap/2670
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- Date: 5 Jun 2001 18:06:01 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
The following reply was made to PR bootstrap/2670; it has been noted by GNATS.
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: jsm28@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org
Subject: Re: bootstrap/2670
Date: Tue, 5 Jun 2001 19:57:53 +0200 (MEST)
jsm28@gcc.gnu.org writes:
> Synopsis: Passing -fpic to cc gives warning
>
> State-Changed-From-To: open->feedback
> State-Changed-By: jsm28
> State-Changed-When: Mon Jun 4 08:59:45 2001
> State-Changed-Why:
> Is this problem still present with current 3.0 CVS?
I didn't see it in a bootstrap attempt (which didn't work out, see
http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00876.html
http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00962.html
http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00967.html
) of gcc 3.0 20010431, but I've now figured out why: the toplevel
configure.in includes config/mh-x86pic and config/mt-x86pic if ${shared} =
yes; this is set when you configure with --enable-shared (as I'd done in
the original bootstrap, but not in the later ones, keeping them as vanilla
as possible), not taking into account that the bootstrap compiler may need
another PIC flag, not -fpic/-fPIC. This problem is obviously generic,
since all the config/m?-*pic files only use -fpic/-fPIC.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE