From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: .DEFAULT: rule
Date: Wed, 14 Feb 2007 19:24:00 -0000 [thread overview]
Message-ID: <45D361E0.6040703@redhat.com> (raw)
A heads up (and of course better solution welcome).
Automake's generated dependencies cause a build to fail when a file is
removed. This occures because the generated .Po file retains references
to the removed files and make aborts the build with file not found.
I've now added this:
+.DEFAULT:
+ @echo " >>>>> .DEFAULT: $@ <<<<<"
to the build which tells make to ignore missing files. If a file was
really needed the build still dies but later when something goes to use
the file. If the file really wasn't needed, such as stale references in
.Po files, the problem gets flushed out.
lets see how it goes,
Andrew
next reply other threads:[~2007-02-14 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 19:24 Andrew Cagney [this message]
2007-02-14 21:25 ` Tom Tromey
2007-02-14 23:58 ` Andrew Cagney
2007-02-16 1:42 ` Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45D361E0.6040703@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.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).