From: Mark H Weaver <mhw@netris.org>
To: Richard Shann <richard.shann@virgin.net>
Cc: guile-user@gnu.org
Subject: Re: statically linking in srfi modules
Date: Sun, 10 Feb 2013 21:02:16 -0500 [thread overview]
Message-ID: <87sj531uc7.fsf@tines.lan> (raw)
In-Reply-To: <1360517094.2172.1582.camel@debian-box.lan> (Richard Shann's message of "Sun, 10 Feb 2013 17:24:54 +0000")
Richard Shann <richard.shann@virgin.net> writes:
> On Sun, 2013-02-10 at 10:35 -0500, Mark H Weaver wrote:
>> This is an unrelated problem, namely that './configure' is apparently
>> unable to find a suitable POSIX regexp library. I think you'll find
>> that HAVE_REGCOMP is not defined in 'config.h', in which case
>> 'make-regexp' will not be available. Search for 'regex' and 'rxposix'
>> in 'config.log' for details on what went wrong.
> Thanks for the insight - I have asked on the mxe mailing list, as I
> guess this is a problem of their make file. But in case you can help
> here too, I deliberately triggered a failed build so that I could get at
> the config.log file and I found this within:
>
> ...
> configure:25048: checking for regex.h
> configure:25057: result: yes
> configure:24937: checking rxposix.h usability
> configure:24954: i686-pc-mingw32-gcc -c -Wno-unused-but-set-variable
> conftest.c >&5
> conftest.c:96:21: fatal error: rxposix.h: No such file or directory
> ...
>
> the resultant config.h has
>
> /* Define to 1 if you have the `regex' library (-lregex). */
> /* #undef HAVE_LIBREGEX */
>
> which I guess means it is undefined...
>
> I can't seem to track down anything about rxposix.h though ...
Don't worry about rxposix.h. We need only one of regex.h, rxposix.h, or
rx/rxposix.h, and it doesn't matter which one.
The problem now is that ./configure was apparently unable to find out
how to link in the 'regcomp' function. Search for 'regcomp' in
'configure.in' to see the source code for the relevant tests. Search
for 'regcomp', 'regex', and 'rx' in 'config.log' to see more detail
about what went wrong. Note that 'GUILE_NAMED_CHECK_FUNC' is defined in
'acinclude.m4'.
Regards,
Mark
next prev parent reply other threads:[~2013-02-11 2:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 9:24 statically linking in srfi modules Richard Shann
2013-02-08 9:25 ` Richard Shann
2013-02-08 11:27 ` Andy Wingo
2013-02-08 13:02 ` Richard Shann
2013-02-08 13:21 ` Richard Shann
2013-02-08 17:52 ` Richard Shann
2013-02-08 21:39 ` Mark H Weaver
2013-02-08 22:11 ` Mark H Weaver
2013-02-08 22:36 ` Richard Shann
2013-02-09 12:13 ` Richard Shann
2013-02-09 15:10 ` Mark H Weaver
2013-02-09 15:32 ` Mark H Weaver
2013-02-09 17:57 ` Richard Shann
2013-02-10 2:00 ` Mark H Weaver
2013-02-10 11:11 ` Richard Shann
2013-02-10 15:35 ` Mark H Weaver
2013-02-10 17:24 ` Richard Shann
2013-02-11 2:02 ` Mark H Weaver [this message]
2013-02-11 10:05 ` Richard Shann
2013-02-11 13:07 ` Richard Shann
2013-02-11 17:03 ` Mark H Weaver
2013-02-12 12:58 ` Richard Shann
2013-02-12 19:01 ` Mark H Weaver
2013-02-12 21:38 ` Ludovic Courtès
2013-02-09 18:52 ` Richard Shann
2013-02-08 23:44 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj531uc7.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-user@gnu.org \
--cc=richard.shann@virgin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).