[Bug libstdc++/33603] New: configuration failure during native build

[Bug libstdc++/33603] New: configuration failure during native build

[gdr at gcc dot gnu dot org]

Native build on i686-pc-mingw32 fails in libstdc++ with:

checking for sin in -lm... configure: error: Link tests are not allowed after
GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1


-- 
           Summary: configuration failure during native build
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gdr at gcc dot gnu dot org
 GCC build triplet: i686-pc-mingw32
  GCC host triplet: i686-pc-mingw32
GCC target triplet: i686-pc-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[rask at gcc dot gnu dot org]

------- Comment #1 from rask at gcc dot gnu dot org  2007-09-30 20:35 -------
Please look in your config.log for messages from collect2 and post the last
linker failure one plus any that look wrong.


-- 

rask at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |build


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[gdr at cs dot tamu dot edu]

------- Comment #2 from gdr at cs dot tamu dot edu  2007-09-30 21:22 -------
Subject: Re:  configuration failure during native build

"rask at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| ------- Comment #1 from rask at gcc dot gnu dot org  2007-09-30 20:35 -------
| Please look in your config.log for messages from collect2 and post the last
| linker failure one plus any that look wrong.

Many thanks for the quick and helpful reply.  While looking for collect2, I
realized the path to ld (and as) had been misdetected.  Explicit
specification of the path, --with-ld=/mingw/bin/ld.exe, let me have a
successful configuration.  The buikd is now past the confiuguration step.
I hope there won't be anymore failure.   Many thanks!  Is this type of
failure documented somewhere? 

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[dannysmith at users dot sourceforge dot net]

------- Comment #3 from dannysmith at users dot sourceforge dot net  2007-10-04 08:26 -------
(In reply to comment #2)

 While looking for collect2, I
> realized the path to ld (and as) had been misdetected.  Explicit
> specification of the path, --with-ld=/mingw/bin/ld.exe, let me have a
> successful configuration.  The buikd is now past the confiuguration step.
> I hope there won't be anymore failure.   Many thanks!  Is this type of
> failure documented somewhere? 


Explicit specification of the path to ld and as has bot been necessary
on my native builds on WinXP host, using cygwin bash. But possibly I am
just avoidng the problem by using 'identity' mounts -- mounts where the
posix path equate to the DOS path on the current drive. eg, c:\mingw is
mounted as /mingw. etc so both the posix tools (like exec in the ld
scrtpt) and the native executables refer to the same path.

Danny
> 
> -- Gaby
> 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[gdr at cs dot tamu dot edu]

------- Comment #4 from gdr at cs dot tamu dot edu  2007-10-04 20:29 -------
Subject: Re:  configuration failure during native build

"dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
writes:

| ------- Comment #3 from dannysmith at users dot sourceforge dot net 
2007-10-04 08:26 -------
| (In reply to comment #2)
| 
|  While looking for collect2, I
| > realized the path to ld (and as) had been misdetected.  Explicit
| > specification of the path, --with-ld=/mingw/bin/ld.exe, let me have a
| > successful configuration.  The buikd is now past the confiuguration step.
| > I hope there won't be anymore failure.   Many thanks!  Is this type of
| > failure documented somewhere? 
| 
| 
| Explicit specification of the path to ld and as has bot been necessary
| on my native builds on WinXP host, using cygwin bash. But possibly I am
| just avoidng the problem by using 'identity' mounts -- mounts where the
| posix path equate to the DOS path on the current drive. eg, c:\mingw is
| mounted as /mingw. etc so both the posix tools (like exec in the ld
| scrtpt) and the native executables refer to the same path.

Hi Danny,

  On my mahcine, I too have what you call `identity' mounts.

However, for some reasons, the path to ld is detected as:

c:/Docume~1/gdr/Desktop/sandbox/eval-build/i686-pc-mingw32/libstdc++-v3/c:/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/bin/ld.exe

which is not right.  I suspect the real path is

  c:/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/bin/ld.exe

but somehow it is appended to the build directory path.  Furthermore, it
looks a very complicated path name.

Thanks for looking into this.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[dannysmith at users dot sourceforge dot net]

------- Comment #5 from dannysmith at users dot sourceforge dot net  2007-10-05 07:03 -------
(In reply to comment #4)
> 
> However, for some reasons, the path to ld is detected as:
> 
> c:/Docume~1/gdr/Desktop/sandbox/eval-build/i686-pc-mingw32/libstdc++-v3/c:/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/bin/ld.exe
> 
> which is not right.  I suspect the real path is
> 
>   c:/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/bin/ld.exe
> 
> but somehow it is appended to the build directory path.  Furthermore, it
> looks a very complicated path name.
> 

How do you configure?

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

works for me.  Configure correctly sets 
ORIGINAL_LD_FOR_TARGET="../ld/ld-new.exe"

If I move binutils out of tree then I get
ORIGINAL_LD_FOR_TARGET="/mingw/mingw32/bin/ld"
which also works  correctly.

Are you using MSYS or cygwin bash and tools? 

Danny


-- 

dannysmith at users dot sourceforge dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dannysmith at users dot
                   |                            |sourceforge dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[bkoz at gcc dot gnu dot org]

------- Comment #6 from bkoz at gcc dot gnu dot org  2007-10-18 16:31 -------

Yo Gaby. Has this been worked out? Can we close this?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[gdr at cs dot tamu dot edu]

------- Comment #7 from gdr at cs dot tamu dot edu  2007-10-18 18:46 -------
Subject: Re:  configuration failure during native build

"bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| Yo Gaby. Has this been worked out? Can we close this?

As long as we document that that build on MinGW requires explicit
specification of the paths to `as' and `ld'.  

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[nightstrike at gmail dot com]

------- Comment #8 from nightstrike at gmail dot com  2007-10-20 19:12 -------
Explicit paths for mingw for as and ld should not be required.  We fixed this
for mingw-w64, and the same thing should be applied to mingw32.  This same
error occurs regardless of whether or not you are in a mingw environment doing
a native build or doing a cross compile.  For instance, I am cross compiling
from x86_64-pc-linux and the same thing happens.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33603

[Bug libstdc++/33603] configuration failure during native build

[bkoz 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