On Mon, 2013-02-11 at 10:05 +0000, Richard Shann wrote: > I noticed that the invocation of the guile build was accepting the > default for regex, so I tried setting it explicitly > with --enable-regex=yes in the configure. With this I see in > config.log > > configure:31783: checking for main in -lregex > configure:31812: i686-pc-mingw32-gcc -o conftest.exe > -Wno-unused-but-set-variable > -I/home/rshann/mxe/usr/i686-pc-mingw32/include conftest.c -lregex > -lgmp -lws2_32 -lm -lltdl -lunistring -lintl -liconv >&5 > /home/rshann/mxe/usr/lib/gcc/i686-pc-mingw32/4.7.0/../../../../i686-pc-mingw32/bin/ld: > cannot find -lregex > collect2: error: ld returned 1 exit status > > That must surely be a clue, and perhaps a bug, I presume the default > is > to have regex built? Sorry - I think I was getting fooled here by repeated sections of stuff, checking for regcomp occurs three times and there is this:
configure:31783: checking for main in -lregex configure:31812: i686-pc-mingw32-gcc -o conftest.exe -Wno-unused-but-set-variable -I/home/rshann/mxe/usr/i686-pc-mingw32/include conftest.c -lregex -lgmp -lws2_32 -lm -lltdl -lunistring -lintl -liconv >&5 /home/rshann/mxe/usr/lib/gcc/i686-pc-mingw32/4.7.0/../../../../i686-pc-mingw32/bin/ld: cannot find -lregex probably in all cases. Richard
