From: Richard Shann <richard.shann@virgin.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: statically linking in srfi modules
Date: Tue, 12 Feb 2013 12:58:36 +0000 [thread overview]
Message-ID: <1360673916.2172.3548.camel@debian-box.lan> (raw)
In-Reply-To: <874nhi2363.fsf@tines.lan>
On Mon, 2013-02-11 at 12:03 -0500, Mark H Weaver wrote:
> Richard Shann <richard.shann@virgin.net> writes:
> > 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.
>
> Can you find out where the 'regcomp' function is?
Well, I tracked back from the GNU/LilyPond build system - it seems to
originate in glibc, but in the GNU/LilyPond build system it has been
extracted out as a separate library.
http://lilypond.org/download/gub-sources/regex-2.3.90-1.tar.bz2
By building this with --disable-shared I have obtained a library which
links to guile and ice-9/regex is now working inside Denemo.
Thank you very much for your help. I don't know if there is anything
that it would be good to do upstream as a result of this epic little
voyage ...
Richard
> If you can find it,
> you could pass LDFLAGS=-lfoobar to ./configure. My suspicion is that
> it's missing from your MXE build. Another possibility is that 'regcomp'
> is a preprocessor macro in one of the include files, which the current
> tests would fail to detect.
>
> > I am a bit out of my depth here ... these seem to be the libraries that
> > could plausibly provide regcomp(), )
> > (by running find . -name '*regex*' -print)
> >
> > ./usr/i686-pc-mingw32/lib/libboost_regex-mt.a
> > ./usr/i686-pc-mingw32/lib/libwxregexu-2.8-i686-pc-mingw32.a
> > ./usr/i686-pc-mingw32/lib/libwxregex-2.8-i686-pc-mingw32.a
> > ./usr/i686-pc-mingw32/lib/libboost_regex-mt-d.a
>
> These aren't the droids you're looking for. Guile 1.8's ./configure
> seems to be looking for either libregex or librx, though I confess that
> my autoconf skills are weak.
>
> Mark
next prev parent reply other threads:[~2013-02-12 12:58 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
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 [this message]
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=1360673916.2172.3548.camel@debian-box.lan \
--to=richard.shann@virgin.net \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
/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).