Re: [Mingw-users] I broke my MinGW

[Brian D. <br...@de...>]

Erik de Castro Lopo wrote:

> I've had MinGW installed on my machine for some time now, but hadn't
> used it for a while until today. Now when I try to run the configure
> script for one of my projects I get:

Technically, this is not MinGW but MSYS.  Roughly speaking MinGW is just
the toolchain (compiler, assembler, linker, and support files like
headers) and MSYS is the set of POSIX utilities like the Bourne shell,
'ls', 'awk', 'grep', 'sed', 'make' et al. that are necessary to use a
POSIX build environment such as autoconf-generated 'configure' scripts.

The part that is failing in your case seems to be the MSYS runtime
(msys-1.0.dll), with the specific manifestation of failure to launch the
Bourne shell /bin/sh, but that could just be the first thing that the
configure script does that triggers the error.  You should try to
isolate and reduce it from a complex configure script to just running
something simple that uses the MSYS runtime like /bin/true or /bin/ls or
whatever.

> $ ./configure
>       0 [main] sh 2948 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
> ./configure: line 113:  2948 Segmentation fault      (core dumped) ( set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`" )
>       0 [main] sh 2756 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
> ./configure: line 113:  2756 Segmentation fault      (core dumped) ( set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`" )
>       0 [main] sh 4544 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
> ./configure: line 113:  4544 Segmentation fault      (core dumped) ( set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`" )
>       0 [main] sh 4620 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>       0 [main] sh 5964 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
>       0 [main] sh 6112 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump

> I tried re-installing MinGW from scratch, but that didn't work.
> I've tried googling for answers with no luck.

Reinstalling MinGW won't do anything as this isn't MinGW, but
reinstalling MSYS might.  :-)  You should look at the stackdump file,
and try to reduce it as much as possible as explained above.  If it's
specific to bash then there might be some environmental thing (such as
finding an incompatible DLL in the PATH) that is tripping it up.  It's
hard to give any specific advice; it's more a matter of just removing as
many things as possible until you isolate the thing that is causing the
failure.

Brian