From: Bruce Korb <bkorb@pacbell.net>
Cc: autogen-devel@lists.sourceforge.net, bkorb@pacbell.net
Subject: Re: [Autogen-devel] building a libguile client
Date: Tue, 25 Jun 2002 17:53:45 -0700 [thread overview]
Message-ID: <afb6gq$jud$2@main.gmane.org> (raw)
In-Reply-To: 3D18FB4D.56978564@yahoo.com
Earnie Boyd wrote:
>
> I execute noag-boot.sh and find that configure can't locate
> -lregex for some reason. I do have it in /usr/lib.
But not in /usr/lib/libc*.
> So I export LIBS=-lregex and execute noag-boot.sh again.
Exactly the thing I was hoping to point you at with the config message:
> cat >&2 <<'_EOF_'
> I cannot detect POSIX compliant regcomp/regexec routines.
> These are required for AutoGen to work correctly. If you have
> such a library present on your system, you must specify it by
> setting the LIBS environment variable, e.g., "LIBS='-lregex'".
> If you do not have such a library on your system, then you should
> download and install, for example, the one from:
> ftp://ftp.gnu.org/gnu/rx/
...
> I make distclean, configure --prefix=/usr --disable-shared and make.
> Now I find config.h and /usr/include/libguile/scmconfig.h redefine
> a boat load of constants, like PACKAGE_*, is this due to
> a misconfigure of libguile?
Yes. Unfortunately, there is no trivial
way out of the problem. I think the proper solution is for guile
(and any other package that installs its own config.h file) to
"prefix" the defines:
http://ac-archive.sf.net/Miscellaneous/ac_create_prefix_config_h.html
and use those #define-d values from their installed config header.
It would be "good" to prominently document the importance of this
in the autoconf docs. Meanwhile, we have a problem....
> I finally get to the compile of agen5/cgi-fsm.c and find cgi-fsm.h
> missing. Is this supposed to be generated? The agen5/cgi-fsm.c file is
> stored in CVS, should the corresponding header also be available from
> CVS?
No. cgi-fsm.c is under CVS because it contains some edited source,
though it is mostly generated. Looks like I left cgi-fsm.h off the
list of generated source. Sorry. It will be updated in a few minutes.
I'll also send it as an attachment under separate cover.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2002-06-26 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D1210F1.2EC8AAD8@yahoo.com>
[not found] ` <3D1213A9.727CCD5B@yahoo.com>
[not found] ` <3D1241BE.17B9A0F2@pacbell.net>
[not found] ` <3D1256FF.7CDE510C@yahoo.com>
[not found] ` <3D125729.7E6DA69B@pacbell.net>
[not found] ` <3D18FB4D.56978564@yahoo.com>
2002-06-26 0:53 ` Bruce Korb [this message]
[not found] ` <3D191099.89BA48FD@pacbell.net>
2002-06-26 10:54 ` [Autogen-devel] building a libguile client Earnie Boyd
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='afb6gq$jud$2@main.gmane.org' \
--to=bkorb@pacbell.net \
--cc=autogen-devel@lists.sourceforge.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).