From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Subject: install-data-local scheduling not guaranteed
Date: Fri, 03 May 2002 16:01:21 -0700 [thread overview]
Message-ID: <E173m3E-00004q-00@giblet> (raw)
in branch_release-1-6 ice-9/Makefile.am, we use `install-data-local' to
install "and-let*.scm". w/ automake 1.5 (no idea what was before), this
frag is run before the rest of the install, and fails if there is no
destination directory already set up. the failure is masked by the "-"
action prefix, which is fine (considering the reason for using this
mechanism in the first place -- slackful handling of sites where "*" is
not a valid file name).
automake documentation sez:
> Extending installation
> ======================
>
> It is possible to extend this mechanism by defining an
> `install-exec-local' or `install-data-local' target. If these targets
> exist, they will be run at `make install' time. These rules can do
> almost anything; care is required.
>
> Automake also supports two install hooks, `install-exec-hook' and
> `install-data-hook'. These hooks are run after all other install rules
> of the appropriate type, exec or data, have completed. So, for
> instance, it is possible to perform post-installation modifications
> using an install hook.
so probably we should use `install-data-hook' instead. i'll test this
and commit changes shortly, presuming all goes well.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
reply other threads:[~2002-05-03 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E173m3E-00004q-00@giblet \
--to=ttn@giblet.glug.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).