This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/2670] Passing -fpic to cc gives warning


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2670



------- Additional Comments From ro@gcc.gnu.org  2003-05-22 16:54 -------
Confirmed with gcc 3.3.1 20030522 (and seems to be present in mainline as well).
In all of the gcc and src repositories, only libiberty uses PICFLAG from the
toplevel config/m?-*pic files to generate PIC code.  This could be fixed by
switching libiberty to use libtool (and allowed us to remove all of these files
at the same time :-).



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]