* [Bug libstdc++/8307] libstdc++ fails to compile because of fixincludes headers
[not found] <20021021222600.8307.pgonzalez@bluel.com>
@ 2003-08-05 1:53 ` neroden at gcc dot gnu dot org
2003-08-24 18:19 ` dhazeghi at yahoo dot com
` (2 subsequent siblings)
3 siblings, 0 replies; 7+ messages in thread
From: neroden at gcc dot gnu dot org @ 2003-08-05 1:53 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8307
------- Additional Comments From neroden at gcc dot gnu dot org 2003-08-05 01:53 -------
Possiblility 1. Fixincludes/fixproto is simply running on the wrong set of
headers (this can be checked by looking at the value of SYSTEM_HEADER_DIR in the gcc
Makefile, which should refer to the correct header directory).
Possibility 2. A fixincludes hack is demolishing stdlib.h. (Run fixincludes
by typing 'make stmp-fixinc' in the gcc/ directory, and see if there are lines
saying 'Fixed: stdlib.h'. Those hacks will be the possible culprits.)
Possibility 3. It's being trampled post-fixincludes, by fix-header.c/fixproto.
(this seems unlikely, but is possible).
The solutions are quite different in the three cases, so if it could be determined for sure which one was going wrong, it would help a lot in
tracking this down.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/8307] libstdc++ fails to compile because of fixincludes headers
[not found] <20021021222600.8307.pgonzalez@bluel.com>
2003-08-05 1:53 ` neroden at gcc dot gnu dot org
@ 2003-08-24 18:19 ` dhazeghi at yahoo dot com
2003-09-19 17:57 ` pinskia at gcc dot gnu dot org
2003-09-21 15:00 ` pgonzalez at bluel dot com
3 siblings, 0 replies; 7+ messages in thread
From: dhazeghi at yahoo dot com @ 2003-08-24 18:19 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8307
------- Additional Comments From dhazeghi at yahoo dot com 2003-08-24 18:19 -------
Just a reminder that this bug is still in WAITING, and will be closed, if we don't get feedback about
it. I'm unable to see this with gcc mainline, cvs newlib and binutils, though thanks to PR11476, I
must disable multilibs to build.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/8307] libstdc++ fails to compile because of fixincludes headers
[not found] <20021021222600.8307.pgonzalez@bluel.com>
2003-08-05 1:53 ` neroden at gcc dot gnu dot org
2003-08-24 18:19 ` dhazeghi at yahoo dot com
@ 2003-09-19 17:57 ` pinskia at gcc dot gnu dot org
2003-09-21 15:00 ` pgonzalez at bluel dot com
3 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-09-19 17:57 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8307
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-09-19 15:59 -------
No feedback in 3 months and Dara could not reproduce this.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/8307] libstdc++ fails to compile because of fixincludes headers
[not found] <20021021222600.8307.pgonzalez@bluel.com>
` (2 preceding siblings ...)
2003-09-19 17:57 ` pinskia at gcc dot gnu dot org
@ 2003-09-21 15:00 ` pgonzalez at bluel dot com
3 siblings, 0 replies; 7+ messages in thread
From: pgonzalez at bluel dot com @ 2003-09-21 15:00 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8307
------- Additional Comments From pgonzalez at bluel dot com 2003-09-21 10:36 -------
Sorry I didn't respond sooner. I am happy with this outcome.
I've been able to workaround the bugs by deleting the bad
headers, and the problem seemed to have been fixed in a
recent 3.4 snapshot.
^ permalink raw reply [flat|nested] 7+ messages in thread