--- Comment #15 from andry at inbox dot ru 2008-08-03 12:18 ---
I found where the bug is:
"/mingw/lib/libmsvcrt.a" and "/mingw/lib/libmsvcrtd.a" should be Microsoft
Visual Studio v6.0 libraries. I just run "gccmrt.bat" attached to TDM builds of
GCC (http://www.tdragon.net/recentgcc/) and
--- Comment #14 from andry at inbox dot ru 2008-08-03 02:42 ---
(In reply to comment #12)
> MinGW apps like gcc have *no* way of interpreting anything but Win32 paths.
It is, i found that Msys bash shell (not console) converts all this stuff with
Msys paths. So xgcc already gothering pat
--- Comment #13 from andry at inbox dot ru 2008-08-03 01:50 ---
(In reply to comment #12)
> You're not really testing what you think you are
Ok, i found that Msys console converts all application arguments and
environment variables before run any application. So, i missed out that in
Win
--- Comment #12 from brian at dessent dot net 2008-08-02 21:02 ---
Subject: Re: cc1.exe: internal compiler error: Segmentation
fault
You're not really testing what you think you are, because MSYS
translates everything on the command line, so saying that "gcc
-I/foo/bar" works just me
--- Comment #11 from andry at inbox dot ru 2008-08-02 20:41 ---
> /c/foo/bar is valid for *MSYS* apps. But we're talking about gcc which
> is NOT a MSYS app, it is a MinGW app, i.e. native win32. /c/foo/bar is
> *not* valid for such an app.
Not true, for example, Mingw GCC 3.4.4 perfec
--- Comment #10 from brian at dessent dot net 2008-08-02 19:24 ---
Subject: Re: cc1.exe: internal compiler error: Segmentation
fault
/c/foo/bar is valid for *MSYS* apps. But we're talking about gcc which
is NOT a MSYS app, it is a MinGW app, i.e. native win32. /c/foo/bar is
*not* v
--- Comment #9 from andry at inbox dot ru 2008-08-02 18:01 ---
(In reply to comment #8)
> It's a valid MinGW path only if you have created a physical directory
> named "c" at the root of the current drive, i.e. X:\c\_GccBuilds\...
>
>From "/msys/1.0/doc/MSYS_VS_CYGWIN":
/cygdrive: Ther
--- Comment #8 from brian at dessent dot net 2008-08-02 16:56 ---
Subject: Re: cc1.exe: internal compiler error: Segmentation
fault
It's a valid MinGW path only if you have created a physical directory
named "c" at the root of the current drive, i.e. X:\c\_GccBuilds\...
--
http:
--- Comment #7 from andry at inbox dot ru 2008-08-02 11:10 ---
(In reply to comment #6)
> This kind of path
> '--prefix=/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686' may be understood by
But this is Mingw compatible path, isn't it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=369
--- Comment #6 from dannysmith at users dot sourceforge dot net 2008-08-01
04:34 ---
This kind of path
'--prefix=/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686' may be understood by
your shell, but won't be found by the xgcc driver or cc1.exe which are native
windows apps. Search the
--- Comment #5 from andry at inbox dot ru 2008-08-01 02:14 ---
I check it without these flags and crash happend again, here:
"xgcc.exe -v"
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36948
--- Comment #4 from andry at inbox dot ru 2008-07-27 17:52 ---
Seems that crash happens when GCC run with "-O2" flag:
make CFLAGS="-O2" CFLAGS_FOR_TARGET="-O2"
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36948
--- Comment #3 from andry at inbox dot ru 2008-07-27 14:03 ---
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
make: *** [all] Error 2
--
andry at inbox dot ru changed:
--- Comment #2 from andry at inbox dot ru 2008-07-27 14:01 ---
Created an attachment (id=15967)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15967&action=view)
libgcc config log
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36948
--- Comment #1 from andry at inbox dot ru 2008-07-27 14:01 ---
Created an attachment (id=15966)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15966&action=view)
Root config log
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36948
15 matches
Mail list logo
