Bug 33503 - [4.3/4.4 Regression] problems with libtool wrapper scripts on mingw32
Summary: [4.3/4.4 Regression] problems with libtool wrapper scripts on mingw32
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: bootstrap (show other bugs)
Version: 4.3.0
: P2 normal
Target Milestone: 4.3.3
Assignee: Not yet assigned to anyone
URL:
Keywords: build
Depends on:
Blocks:
 
Reported: 2007-09-19 19:59 UTC by Sergey Pyptev
Modified: 2008-12-31 18:09 UTC (History)
6 users (show)

See Also:
Host: i686-pc-mingw32
Target: arm-unknown-elf
Build: i686-pc-mingw32
Known to work: 4.2.0
Known to fail: 4.3.2 4.4.0
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Pyptev 2007-09-19 19:59:51 UTC
snapshot gcc-4.3-20070914
When i try to build gcc the process falls when it tries to use just created binutils or gas. Investigating the problem I've found that libtool creates "normal" binutils in binutils/.libs directory and creates a wrapper in binutils directory for each util. The wrapper should start shell with script in the same directory but it can not find shell.
Current wrapper tries to call execve() with first parameter "/bin/sh" and returns error. Errno is ENOENT. I suppose execve() works with windows path under MinGW and really, when I've changed libtool to execve() have C:\msys\1.0\bin\sh.exe as first parameter then the wrapper starts correctly, but now shell script, which started by the wrapper, can not start "normal" util, while the script does it from command line without a problem (or may be shell can not find script, I'm not sure). So problem needs further investigation. Wrapper code is in gcc/ltmain.sh
Comment 1 Paolo Bonzini 2008-04-25 15:21:09 UTC

*** This bug has been marked as a duplicate of 35752 ***
Comment 2 Paolo Bonzini 2008-08-01 08:44:54 UTC
not really a duplicate
Comment 3 Ralf Wildenhues 2008-08-01 09:05:34 UTC
Have you tried configuring like this?

  CONFIG_SHELL='C:/msys/1.0/bin/sh.exe' C:/msys/1.0/bin/sh.exe \
    ../gcc-4.3XX/configure [OPTIONS...]
Comment 4 Richard Biener 2008-11-01 11:43:33 UTC
Hum, this is a host problem - and we do not have a list of primary or
secondary host platforms ... extrapolating from the secondary mingw32 target
platform I set this to P2.
Comment 5 Paolo Bonzini 2008-11-01 14:26:37 UTC
The problem is that this bug is unconfirmed.  I'd like to see a failure log; mingw builds were tested very carefully when we upgraded Libtool.

Marked as waiting.
Comment 6 Andrew Pinski 2008-12-31 18:09:30 UTC
No feedback in 3 months so closing.