--- Comment #8 from pinskia at gcc dot gnu dot org 2008-12-31 20:04 ---
I have compiled the trunk (4.4) on cygwin without any patches so closing as
works for me.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from leisner at rochester dot rr dot com 2008-07-19 16:11
---
(In reply to comment #6)
It seems to do better (still compiling), now that I've adjusted the
LD_LIBRARY_PATH to point to mpfr (there's another bug that seems to be a
duplicate). It should really produce a
--- Comment #5 from merkert at comcast dot net 2008-03-14 18:57 ---
I've been getting the same thing with the 4.3 release build. I had no problem
building this version: gcc (GCC) 4.3.0 20071228 (experimental)
Here's the tail of my output (I'll try to build again)
m -f
--- Comment #6 from merkert at comcast dot net 2008-03-15 01:45 ---
It seems to do better (still compiling), now that I've adjusted the
LD_LIBRARY_PATH to point to mpfr (there's another bug that seems to be a
duplicate). It should really produce a better warning or something. It really
--- Comment #3 from rguenth at gcc dot gnu dot org 2008-01-25 22:46 ---
*** Bug 34766 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34481
--- Comment #4 from rguenth at gcc dot gnu dot org 2008-01-25 22:47 ---
*** Bug 34414 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34481
--- Comment #2 from andry at inbox dot ru 2007-12-22 13:56 ---
(In reply to comment #1)
can you try not building in the source directory and use an building
directory?
The same.
May be i missed something to install?
Here my list of components which i checked when installing cygwin:
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-12-22 02:38 ---
can you try not building in the source directory and use an building directory?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
