From: Alexandre Duret-Lutz <duret_g@lrde.epita.fr>
Cc: guile-devel@gnu.org, automake@gnu.org
Subject: Re: Problem building CVS Guile with automake 1.6.1
Date: Fri, 26 Apr 2002 13:33:12 +0200 [thread overview]
Message-ID: <2002-04-26-13-33-13+29271+duret_g@epita.fr> (raw)
In-Reply-To: <uw5r8l2de74.fsf@lambda.math.uni-magdeburg.de> (Matthias Koeppe's message of "Fri, 26 Apr 2002 11:03:27 +0200")
>>> "Matthias" == Matthias Koeppe <mkoeppe@saturn.Math.Uni-Magdeburg.De> writes:
Matthias> Guile's `guile-aclocal.sh' script fails with automake
Matthias> 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 .
This is a work-around makes sense up to Automake 1.4.
It still works with 1.5.
It breaks with recent versions.
aclocal from Automake 1.4 chokes when a -I supplied macro
override a /usr/share/aclocal/ macro, hence your script.
Starting with Automake 1.5, a macro supplied with -I will
override any macro installed in /usr/share/aclocal/, so
you simply have to run
aclocal -I .
(no cp, rm, or --acdir)
Matthias> As far as I understand it, this fails with automake
Matthias> 1.6.1 because the "aclocal" library location is
Matthias> versioned with the automake API version.
Starting with Automake 1.6, there are TWO places:
$datadir/aclocal-1.6/
The directory where Automake puts its internal macros
(AM_INIT_AUTOMAKE and the like). This needs to be versioned.
$datadir/aclocal/
This is the directory where third-party packages are expected
to put their macros. This is not versioned, since these
macros are really independent of Automake.
Matthias> On my system, the location is
Matthias> /localapp/imosoft/sparcv9-sun-solaris2.7/share/aclocal-1.6
This is Automake's own macro repository. The user should not
have to fiddle with it.
Matthias> but
Matthias> aclocal --print-ac-dir
Matthias> ==> /localapp/imosoft/sparcv9-sun-solaris2.7/share/aclocal
This prints the directory when third-party packages are expected
to install their macros.
Matthias> which happens to point to an old (1.4) installation of the aclocal
Matthias> library.
If you haven't uninstalled Automake 1.4/1.5, their files are
still here. This is harmless: the macros found in the versioned
directory have priority.
Matthias> When aclocal is invoked with --acdir set to a copy of this library,
Matthias> automake fails with these messages:
--acdir overrides both the private (versioned) and public
(unversioned) aclocal directories, hence the failure. (This
switch is needed in Automake's testsuite which has to run
aclocal before the macros are installed.)
[...]
--
Alexandre Duret-Lutz
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-26 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 9:03 Problem building CVS Guile with automake 1.6.1 Matthias Koeppe
2002-04-26 11:33 ` Alexandre Duret-Lutz [this message]
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=2002-04-26-13-33-13+29271+duret_g@epita.fr \
--to=duret_g@lrde.epita.fr \
--cc=automake@gnu.org \
--cc=guile-devel@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).