From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: duret_g@lrde.epita.fr, guile-devel@gnu.org
Subject: Re: Problem building CVS Guile with automake 1.6.1
Date: Fri, 26 Apr 2002 10:53:25 -0700 [thread overview]
Message-ID: <E1719uP-0002MH-00@giblet> (raw)
In-Reply-To: <uw5lmbacyqe.fsf@lambda.math.uni-magdeburg.de> (message from Matthias Koeppe on Fri, 26 Apr 2002 16:37:29 +0200)
From: Matthias Koeppe <mkoeppe@mail.Math.Uni-Magdeburg.De>
Date: Fri, 26 Apr 2002 16:37:29 +0200
Dear Guile maintainers: I have prepared the patch below, which checks
for Automake 1.4, for which the work-around is still used; for newer
automake, aclocal is called directly. (Alternatively, one could
require Automake 1.5 for hacking Guile and get rid of the work-around
altogether.)
yeah, i think we're going w/ automake 1.5 at the moment (as encoded by
guile-core/Makefile.am AUTOMAKE_OPTIONS) to address the include-file
bug. i notice 1.6 has been released since early march. if HACKING is
to believed, we should soon migrate to 1.6, so it would be nice to get a
patch to make everything work w/ 1.6.
[cc trimmed.]
(btw, i thought you had guile write privs?)
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-04-26 17:53 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
2002-04-26 14:37 ` Matthias Koeppe
2002-04-26 17:19 ` Marius Vollmer
2002-04-26 17:53 ` Thien-Thi Nguyen [this message]
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=E1719uP-0002MH-00@giblet \
--to=ttn@giblet.glug.org \
--cc=duret_g@lrde.epita.fr \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).