--- Comment #13 from paolo dot carlini at oracle dot com 2009-05-24 04:34
---
*** Bug 40231 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738
--- Comment #12 from loaden at gmail dot com 2009-05-23 09:46 ---
(In reply to comment #2)
> (In reply to comment #1)
> > Are you sure your entire compiler is up to date, not just the library? And
> > the
> > build and install directories are clean? Because your first lines of failure
>
--- Comment #11 from ktietz at gcc dot gnu dot org 2009-04-13 19:25 ---
(In reply to comment #10)
> I try to build gcc with latest CRT from svn (revision 764) - build is OK. It
> seems, snapshot from sourceforge download page(November 15, 2008) not
> compatible with gcc 4.4.
>
Well, th
--- Comment #10 from css20 at mail dot ru 2009-04-13 18:06 ---
I try to build gcc with latest CRT from svn (revision 764) - build is OK. It
seems, snapshot from sourceforge download page(November 15, 2008) not
compatible with gcc 4.4.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3
--- Comment #9 from css20 at mail dot ru 2009-04-13 15:48 ---
> Do you use for native toolchain an fresh initialized directory?
> Which version of toolchain you are using (especially header-set)?
> Do you use --prefix and --with-sysroot options?
I use directory with mingw-64 runtime ins
--- Comment #8 from ktietz at gcc dot gnu dot org 2009-04-13 08:34 ---
(In reply to comment #7)
> > Please make sure, that you have in your gcc source root directory the
> > symbolic
> > link "winsup" pointing to your prefix directory. Secondly, make sure you
> > have
> > the symbolic
--- Comment #7 from css20 at mail dot ru 2009-04-13 08:11 ---
> Please make sure, that you have in your gcc source root directory the symbolic
> link "winsup" pointing to your prefix directory. Secondly, make sure you have
> the symbolic link "mingw" in your prefix directory, which has t
--- Comment #6 from ktietz at gcc dot gnu dot org 2009-04-12 19:49 ---
(In reply to comment #5)
> I see this bug in compiler driver is already known
> (http://sourceforge.net/forum/forum.php?thread_id=3091795&forum_id=723797), it
> works only with "-O0". I can't found report about this b
--- Comment #5 from css20 at mail dot ru 2009-04-12 19:35 ---
I see this bug in compiler driver is already known
(http://sourceforge.net/forum/forum.php?thread_id=3091795&forum_id=723797), it
works only with "-O0". I can't found report about this bug in database.. does
it exists ?
> Wel
--- Comment #4 from css20 at mail dot ru 2009-04-12 08:50 ---
First tests of Win64 compiler.. simple source file test.c was created:
#include "windows.h"
int main(int argc, char **argv)
{
MessageBox(NULL, "test", "test", MB_OK);
}
E:\temp\test>gcc test.c
gcc: CreateProcess: No such
--- Comment #3 from css20 at mail dot ru 2009-04-11 21:09 ---
> Are you sure your entire compiler is up to date, not just the library?
No.. it was not lasest snapshot (20090331).
> We solve this by setting up in gcc's source tree a symbolic link "winsup"
> pointing to the sysroot (pref
--- Comment #2 from ktietz at gcc dot gnu dot org 2009-04-11 19:33 ---
(In reply to comment #1)
> Are you sure your entire compiler is up to date, not just the library? And the
> build and install directories are clean? Because your first lines of failure
> involve bits of the library wh
12 matches
Mail list logo
