From: <guerby@acm.org>
To: bosch@gnat.com
Cc: gcc@gcc.gnu.org
Subject: Re: [Ada]: failure to build on Mandrake 8.1 / x86
Date: Thu, 11 Oct 2001 16:31:00 -0000 [thread overview]
Message-ID: <200110112329.f9BNTlR31192@ulmo.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.10.10110111852320.27247-100000@nile.gnat.com>
> That is strange, since these are automatically generated files,
> and there are correct rules to update them.
But I'd say incorrect (or a least random) time stamps from CVS update.
The only way to get this right for CVS users is to force a generation
and to copy the generated files in the build dir iff they differ from
the $(srcdir) ones using move-if-change.
--
Laurent Guerby <guerby@acm.org>
next prev parent reply other threads:[~2001-10-11 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 12:28 guerby
2001-10-11 10:40 ` guerby
2001-10-11 11:55 ` Geert Bosch
2001-10-11 15:46 ` guerby
2001-10-11 15:53 ` Geert Bosch
2001-10-11 16:31 ` guerby [this message]
2001-10-11 18:04 ` Richard Henderson
2001-10-11 18:07 ` Geert Bosch
2001-10-11 18:17 ` Joseph S. Myers
2001-10-11 18:22 ` Geert Bosch
2001-10-11 18:38 ` Joseph S. Myers
2001-10-11 18:39 ` Zack Weinberg
2001-10-11 14:32 ` Florian Weimer
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=200110112329.f9BNTlR31192@ulmo.localdomain \
--to=guerby@acm.org \
--cc=bosch@gnat.com \
--cc=gcc@gcc.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).