[Bug bootstrap/44173] configure -disable-fixincludes doesn't work

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44173

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Target Milestone|--- |13.0
 Resolution|--- |FIXED

--- Comment #3 from Andrew Pinski  ---
Fixed finally by r13-2319-gbe9dd80f933480 .

[Bug bootstrap/44173] configure -disable-fixincludes doesn't work

[ariel.burton at roguewave dot com]

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

Ariel Burton ariel.burton at roguewave dot com changed:

   What|Removed |Added

 CC||ariel.burton at roguewave
   ||dot com

--- Comment #2 from Ariel Burton ariel.burton at roguewave dot com 2012-01-26 
14:37:51 UTC ---
Isn't -disable-fixincludes desirable if you want gcc to always
use the system files on the platform on which it is running,
rather than that on which it was compiled?

[Bug bootstrap/44173] configure -disable-fixincludes doesn't work

[pinskia at gcc dot gnu dot org]

--- Comment #1 from pinskia at gcc dot gnu dot org  2010-05-17 18:53 ---
I don't think this can ever work except when you know 100% that the headers
don't need to be fix included.  Only newer glibc don't need it and newlib
either.  But the majority of the other OS's need it really.


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

  Component|c   |bootstrap


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