--- Comment #7 from ktietz at gcc dot gnu dot org 2009-07-17 10:35 ---
Seems to be fixed by side-effect.
Thanks,
Kai
--
ktietz at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from rainer at emrich-ebersheim dot de 2009-07-17 10:30
---
This doesn't show up anymore. Someone with appropriate permissions may close
this PR.
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39610
--- Comment #5 from rainer at emrich-ebersheim dot de 2009-04-06 08:53
---
This is a regression because it used to work for gcc-4.4.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39610
--- Comment #4 from ktietz at gcc dot gnu dot org 2009-04-05 08:39 ---
for mingw-w64 we have the same issue as cygwin.
--
ktietz at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #3 from rainer at emrich-ebersheim dot de 2009-04-05 06:46
---
(In reply to comment #1)
> Can you configure with --disable-libstdcxx-pch and try again?
>
Now I get in libstdc++-v3/src:
libtool: compile:
/home/rainer/software/build/i686-pc-cygwin/gcc-4.5.0/gcc/./gcc/xgcc
--- Comment #2 from rainer at emrich-ebersheim dot de 2009-04-02 12:05
---
(In reply to comment #1)
> Can you configure with --disable-libstdcxx-pch and try again?
>
sure, in the evening.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39610
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-04-02 09:33 ---
Can you configure with --disable-libstdcxx-pch and try again?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39610