From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: building guile problem (configure: possibly undefined macro)
Date: Mon, 25 Mar 2013 15:33:39 +0100 [thread overview]
Message-ID: <87ip4f35x8.fsf@gnu.org> (raw)
In-Reply-To: 87ip4fd3c0.fsf@yagnesh.org
Hi,
Yagnesh Raghava Yakkala <hi@yagnesh.org> skribis:
> It seems to build guile I need to have automake 1.12 atleast.
Yes.
> I feel that dependency is somewhat harsh given that ubuntu 12.04 is the latest LTS.
Automake is not needed when building from a tarball. So we’d just
requiring that from people who are likely developers (to be) of Guile.
This doesn’t sound unreasonable to me.
> configure.ac:61: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:80: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
> configure.ac:81: error: possibly undefined macro: AC_PROG_LIBTOOL
> configure.ac:908: error: possibly undefined macro: AM_GNU_GETTEXT
> autoreconf: /home/yagnesh/local/bin/autoconf failed with exit status: 1
Make sure to install libtool-dev and gettext-dev (or similar packages).
They should provide the Autoconf macros mentioned above.
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-03-25 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 13:19 building guile problem (configure: possibly undefined macro) Yagnesh Raghava Yakkala
2013-03-25 14:33 ` Ludovic Courtès [this message]
2013-03-25 20:00 ` Yagnesh Raghava Yakkala
2013-03-25 15:24 ` Stefan Israelsson Tampe
2013-03-25 15:40 ` Yagnesh Raghava Yakkala
2013-03-25 15:43 ` Stefan Israelsson Tampe
2013-03-25 16:26 ` SOLVED; " Yagnesh Raghava Yakkala
2013-03-25 18:01 ` Mark H Weaver
2013-03-25 18:06 ` Mark H Weaver
2013-03-25 20:10 ` Yagnesh Raghava Yakkala
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=87ip4f35x8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.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).