From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: specifying workbook dir for dist-hook
Date: Sun, 07 Apr 2002 15:55:43 -0700 [thread overview]
Message-ID: <E16uLZX-0000SQ-00@giblet> (raw)
In-Reply-To: <87vgb31wz6.fsf@zagadka.ping.de> (message from Marius Vollmer on 07 Apr 2002 15:04:13 +0200)
From: Marius Vollmer <mvo@zagadka.ping.de>
Date: 07 Apr 2002 15:04:13 +0200
Is this a real fix? As far as I can see, it only works 'accidentally'
when using GNU make. Do we want to require GNU make?
the mechanisms and times are as follows:
* automake scanning happens at autogen.sh time. automake instantiates a
Makefile.in from templates, handling "include" directives by diverting
(recursively) scanning to the included file and omitting the directive
in the output, and handling "if MAINTAINER_MODE" sections by prefixing
"@MAINTAINER_MODE_TRUE@" to makefile var definitions (and using other
generally portable constructs).
* expansion of @MAINTAINER_MODE_TRUE@ happens at configure time.
configure creates portable Makefile from portable Makefile.in, etc.
* execution of Makefile actions happens at make time by whichever
make(1) is either available on the system or specified by the user.
here, the root cause of the bug seems to lie in how automake handles
nested "if MAINTAINER_MODE" sections.
because we see different behaviors in different versions of automake and
because the documentation does not explicitly support our funky usage, i
figured that the most slackful fix would be to "don't do that"; the
nature of the fix is to fall back on well-supported (documented, stable)
automake features and avoid conflating them.
you'll also note from point 1 above that none of this has anything to do
w/ GNU make (thankfully :-).
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-07 22:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 21:17 specifying workbook dir for dist-hook Thien-Thi Nguyen
2002-03-31 1:27 ` Thien-Thi Nguyen
2002-04-01 0:09 ` Marius Vollmer
2002-04-01 2:05 ` Rob Browning
2002-04-01 8:53 ` Thien-Thi Nguyen
2002-04-01 18:47 ` Neil Jerram
2002-04-01 19:41 ` Thien-Thi Nguyen
2002-04-01 22:08 ` Neil Jerram
2002-04-03 18:43 ` Marius Vollmer
2002-04-03 20:06 ` Thien-Thi Nguyen
2002-04-07 13:04 ` Marius Vollmer
2002-04-07 22:55 ` Thien-Thi Nguyen [this message]
2002-04-08 0:06 ` Marius Vollmer
2002-04-08 2:50 ` Thien-Thi Nguyen
2002-04-08 16:28 ` Marius Vollmer
2002-04-08 19:26 ` Thien-Thi Nguyen
2002-04-08 23:56 ` Thien-Thi Nguyen
2002-04-09 16:58 ` Marius Vollmer
2002-04-09 17:09 ` Marius Vollmer
2002-04-01 20:07 ` 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=E16uLZX-0000SQ-00@giblet \
--to=ttn@giblet.glug.org \
--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).