From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: specifying workbook dir for dist-hook
Date: 08 Apr 2002 02:06:14 +0200 [thread overview]
Message-ID: <871ydrjbpl.fsf@zagadka.ping.de> (raw)
In-Reply-To: <E16uLZX-0000SQ-00@giblet>
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> * 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).
However, automake-1.4-p4 incorrectly does _not_ handle include
directives with filenames that contain a '-'. It copies these lines
unchanged to the Makefile.in.
Automake 1.5 handles them correctly.
> here, the root cause of the bug seems to lie in how automake handles
> nested "if MAINTAINER_MODE" sections.
Automake 1.5 handles inclusions inside ifs correctly.
> you'll also note from point 1 above that none of this has anything to do
> w/ GNU make (thankfully :-).
It has, unfortunately, because GNU make also handles include
directives and thus covers up for the bug in automake 1.4. It will
execute the include directive that automake missed.
Sooo, I'd say we should just require automake 1.5.
I'm in the process of committing some fixes that will make us survive
a "distcheck" with automake 1.5. That version seems to put more
restrictive (but reasonable) permissions on the created distdirs and
not all our dist-hooks play nice. It also fails to handle 'deep'
directories in EXTRA_DIST properly, something which 1.4 had no problem
with. Ach, the joys of software...
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-08 0:06 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
2002-04-08 0:06 ` Marius Vollmer [this message]
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=871ydrjbpl.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).