This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/33603] configuration failure during native build
- From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jan 2009 23:39:16 -0000
- Subject: [Bug libstdc++/33603] configuration failure during native build
- References: <bug-33603-1000@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #9 from bkoz at gcc dot gnu dot org 2009-01-08 23:39 -------
I am closing this due to inactivity. The following remain unclear to me:
1) Does this issue exist with mingw32 and configure such as:
Combined binutils/gcc in-tree build with this configuration
../src/configure --host=mingw32 --build=mingw32 --target=mingw32
--with-arch=i486 --with-cpu=generic --disable-werror --prefix=/mingw
--enable-threads --disable-nls --enable-languages=c,c++,objc,obj-c++,fortran
--disable-win32-registry --enable-libstdcxx-debug
--enable-cxx-flags='-fno-function-sections -fno-data-sections'
--enable-version-specific-runtime-lib --enable-libgomp
--disable-sjlj-exceptions --enable-shared --disable-symvers
(Danny Smith says yes, Gaby says no. Nightstrike says yes on mingw32, but not
for mingw64)? No real consensus.
If this is a known issue, it needs to be documented here:
http://gcc.gnu.org/install/specific.html#x-x-mingw
2) If so, does --with-ld=/mingw/bin/ld.exe fix it? (Gaby says Yes.)
--
bkoz at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603