This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/36622] 4.3.1 failed to compile gcse.c file.
- From: "rwild at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Jul 2008 16:11:34 -0000
- Subject: [Bug target/36622] 4.3.1 failed to compile gcse.c file.
- References: <bug-36622-15556@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #19 from rwild at gcc dot gnu dot org 2008-07-02 16:11 -------
(In reply to comment #7)
> > >So, you are suggesting that I should remove fPIC option, correct?
> > Yes. Is there a reason why you have CFLAGS set anyways?
> 2. -fPIC has always been set in all the other gcc versions that I have
> compiled through CFLAGS. So, I did not think about this issue until you
> pointed it out.
This does not explain _why_ you used -fPIC in the first place.
IOW, why did you ever start using -fPIC?
We could just recommend to you not to use -fPIC in the CFLAGS
for configuring GCC. But from the PR history it is not clear whether
you had a good reason to use it in the first place, thus it is difficult
to know what you may be working around here for.
> Do I need to exclude -fPIC for the other platform (e.g. x86_64) builds when I
> build gcc 4.3.1? I have tried building 4.3.1 in SLES10 with -fPIC option , and
> it built OK for me.
That may well be.
--
rwild at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rwild at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36622