Not finding regexec?

[melinkai]

I'm running 64-bit Windows 7 with MinGW and MSYS, and have run into issues with ./configure - specifically, getting it to locate the regex files.

It seems it is able to find the regex.h file, which contains the regexec command, but then determines that regexec isn't there?

I have perused some previous discussions of similar problems in this group, and my best guess is that I need to put a 64-bit version of the GNU regex2.dll somewhere in my file system - thing is, I can't seem to find a 64-bit regex2.dll, and I have no idea where to put it.

My MSYS log is as follows:

...

checking for an ANSI C-conforming const... yes

checking for towupper... yes

checking for native Win32... yes

checking for 64-bit Apple OSX... no

checking stdio.h usability... yes

checking stdio.h presence... yes

checking for stdio.h... yes

checking sqlite3.h usability... no

checking sqlite3.h presence... no

checking for sqlite3.h... no

checking for ASPELL... no

checking aspell.h usability... no

checking aspell.h presence... no

checking for aspell.h... no

checking for new_aspell_config in -laspell... no

checking for HUNSPELL... no

checking hunspell.h usability... no

checking hunspell.h presence... no

checking for hunspell.h... no

checking locale.h usability... yes

checking locale.h presence... yes

checking for locale.h... yes

checking for LC_MESSAGES... no

checking for LIBEDIT... no

checking regex.h usability... yes

checking regex.h presence... yes

checking for regex.h... yes

checking for regexec... no

checking for regexec in -lregex... no

configure: error: No regex library found

I can post my config.log too, if that would help, but I'm avoiding that for now as it's bulky and I don't know what part of it to show.

[Linas Vepstas]

Hi,

Sorry you are having troubles.

Be sure to subscribe to the mailing list, or it is likely ou will miss replies from others.

Look at the config.log file. somewhere, about 90% of the way in, you will find what actually went wrong.   configure works by creating a very small program, vaguely something like this:  #include "regex.h" main() {}  and then it tried to compile and link it.  The log file will show exactly what compiler flags were used, and what directories were searched for the libraries (and it wiil also show the source for what its trying to compile.  At this point, there problem usually becomes obvious. 

Actually, you look in config.log to find what line-number of configure the stuff is happening in.  You should find something like the below, which is the program that it tries to compile and link.  The actual compiler flags are in the config.log

cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

/* Override any GCC internal prototype to avoid an error.
   Use char because int might match the return type of a GCC
   builtin and then its argument prototype would still apply.  */
#ifdef __cplusplus
extern "C"
#endif
char regexec ();
int
main ()
{
return regexec ();
  ;
  return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
  ac_cv_lib_regex_regexec=yes
else
  ac_cv_lib_regex_regexec=no
fi

--linas

--
You received this message because you are subscribed to the Google Groups "link-grammar" group.
To unsubscribe from this group and stop receiving emails from it, send an email to link-grammar...@googlegroups.com.
To post to this group, send email to link-g...@googlegroups.com.
Visit this group at http://groups.google.com/group/link-grammar.
For more options, visit https://groups.google.com/d/optout.