From: Matthias Koeppe <mkoeppe@mail.Math.Uni-Magdeburg.De>
Cc: automake@gnu.org
Subject: Problem building CVS Guile with automake 1.6.1
Date: Fri, 26 Apr 2002 11:03:27 +0200 [thread overview]
Message-ID: <uw5r8l2de74.fsf@lambda.math.uni-magdeburg.de> (raw)
Guile's `guile-aclocal.sh' script fails with automake 1.6.1. Here is
the relevant part:
| # copy all installed aclocal files into $temp
| cp `aclocal --print-ac-dir`/*.m4 $temp
|
| # remove the .m4 files installed by Guile from $temp, so they don't
| # cause conflicts
| rm -f ${temp}/guile.m4 ${temp}/qthreads.m4
|
| aclocal --acdir=$temp -I .
As far as I understand it, this fails with automake 1.6.1 because the
"aclocal" library location is versioned with the automake API version.
On my system, the location is
/localapp/imosoft/sparcv9-sun-solaris2.7/share/aclocal-1.6
but
aclocal --print-ac-dir
==> /localapp/imosoft/sparcv9-sun-solaris2.7/share/aclocal
which happens to point to an old (1.4) installation of the aclocal
library.
When aclocal is invoked with --acdir set to a copy of this library,
automake fails with these messages:
configure.in:28: your implementation of AM_INIT_AUTOMAKE comes from an
configure.in:28: old Automake version. You should recreate aclocal.m4
configure.in:28: with aclocal and run automake again.
Clearly something needs to be fixed. Is it aclocal (to return the
versioned "aclocal" directory) or Guile?
--
Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-04-26 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 9:03 Matthias Koeppe [this message]
2002-04-26 11:33 ` Problem building CVS Guile with automake 1.6.1 Alexandre Duret-Lutz
2002-04-26 14:37 ` Matthias Koeppe
2002-04-26 17:19 ` Marius Vollmer
2002-04-26 17:53 ` Thien-Thi Nguyen
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=uw5r8l2de74.fsf@lambda.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
--cc=automake@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).