configure problems under msys

download the latest from the head of the trunk, then ran ‘configure’ under msys and received the following… has anyone done this under msys on a windows pc??

$ configure
./configure: line 51: 1968 Segmentation fault (core dumped) ( PATH=“/nonexistent;.”; conf$$.sh ) >/dev/null 2>&1
./configure: line 58: 5272 Segmentation fault (core dumped) ( ( MAIL=60; unset MAIL ) || exit ) >/dev/null 2>&1
0 [main] sh 4000 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 6116 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 3592 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 816 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 5032 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
./configure: line 113: 5032 Segmentation fault (core dumped) ( set +x; test -z “(eval $as_var=C; export $as_var) 2>&1” )
0 [main] sh 3932 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 5180 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
./configure: line 113: 5180 Segmentation fault (core dumped) ( set +x; test -z “(eval $as_var=C; export $as_var) 2>&1” )
0 [main] sh 4936 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
./configure: line 113: 4936 Segmentation fault (core dumped) ( set +x; test -z “(eval $as_var=C; export $as_var) 2>&1” )
0 [main] sh 4348 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
./configure: line 113: 4348 Segmentation fault (core dumped) ( set +x; test -z “(eval $as_var=C; export $as_var) 2>&1” )
0 [main] sh 4628 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 4272 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 4192 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 5244 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
checking build system type… 0 [main] sh 3032 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 5020 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 4720 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 1568 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 2480 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh 3564 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
autoconf/config.guess: line 1: 3564 Segmentation fault (core dumped) ( umask 077 && mkdir $tmp )
0 [main] sh 2696 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
autoconf/config.guess: line 1: 2696 Segmentation fault (core dumped) ( umask 077 && mkdir $tmp )
: cannot create a temporary directory in /tmp
0 [main] sh 4348 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
autoconf/config.guess: line 1: 4348 Segmentation fault (core dumped) ( rm -f $tmpfiles 2>/dev/null; rmdir $tmp 2>/dev/null )
configure: error: cannot guess build type; you must specify one
0 [main] sh 2720 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump

Hello, Bob

download the latest from the head of the trunk, then ran 'configure' under
msys and received the following.... has anyone done this under msys on a
windows pc??

Msys works fine for me. What is the version of msys you're using? What
is the version of bash?

i running msys 1.0 it appears; the bash sh is 2.04.0(1)

just to be sure, i’m simply typing $SRC_ROOT/configure from my $OBJ_ROOT directory

Anton Korobeynikov wrote:

Hello, Bob

i running msys 1.0 it appears; the bash sh is 2.04.0(1)

Hrm... This seems to be pretty ancient and buggy. :slight_smile:
Consider reading
http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx
it can provide necessary sources of different tools requires. Some
versions noted there might be already out-of-date, but otherwise the
text looks good.

hi anton,

i upgrade my bash, per instructions on the blog… but the configure script is still causing segmentations faults… again, i’m running configure with no arguments…

Anton Korobeynikov wrote:

Hello, Bob

i upgrade my bash, per instructions on the blog.... but the configure
script is still causing segmentations faults.... again, i'm running
configure with *no* arguments....

No idea then. Everything works perfectly here (even w/o any parameters
to configure).