From: Joe Buck <jbuck@synopsys.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Greg Schafer <gschafer@zip.com.au>,
Paolo Carlini <pcarlini@unitus.it>,
gcc@gcc.gnu.org
Subject: Re: GCC-3.2.2 pre-release (second iteration)
Date: Fri, 31 Jan 2003 02:44:00 -0000 [thread overview]
Message-ID: <20030130175358.A23185@synopsys.com> (raw)
In-Reply-To: <m3ptqeyudx.fsf@uniton.integrable-solutions.net>; from gdr@integrable-solutions.net on Fri, Jan 31, 2003 at 02:34:34AM +0100
Greg Schafer <gschafer@zip.com.au> writes:
> | It is probably the bison thing as Paolo suggested. But I thought the
> | maintainer scripts were supposed to adjust the timestamps so as not to rely
> | on the bison in the user's environment. Dunno.
On Fri, Jan 31, 2003 at 02:34:34AM +0100, Gabriel Dos Reis wrote:
> I believe that the maintainer scripts aren't that smart :-(
In that case, run
contrib/gcc_update --touch
before making tarballs. This will update the times of dependent files
to be newer than those that are depended on (I'm not certain if it
gets everything, but it can't hurt).
next prev parent reply other threads:[~2003-01-31 1:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 17:07 Gabriel Dos_Reis
2003-01-29 22:45 ` Joe Buck
2003-01-30 1:28 ` Paolo Carlini
2003-01-30 23:34 ` Gabriel Dos Reis
2003-01-31 0:59 ` Gabriel Dos Reis
2003-01-31 1:58 ` Bison-1.875, again! (Re: GCC-3.2.2 pre-release (second iteration)) Paolo Carlini
2003-01-31 2:04 ` Gabriel Dos Reis
2003-01-31 1:59 ` GCC-3.2.2 pre-release (second iteration) Joe Buck
2003-01-31 2:14 ` Greg Schafer
2003-01-31 2:21 ` Gabriel Dos Reis
2003-01-31 2:44 ` Joe Buck [this message]
2003-01-31 13:53 ` Joseph S. Myers
2003-01-31 14:43 ` Gabriel Dos Reis
2003-01-31 18:28 ` Joe Buck
2003-01-31 19:13 ` Joseph S. Myers
2003-02-01 16:19 ` Gabriel Dos Reis
2003-02-03 16:55 ` Joe Buck
2003-01-31 3:51 ` Greg Schafer
2003-01-31 5:28 ` Gabriel Dos Reis
2003-01-31 13:51 ` Joseph S. Myers
2003-01-31 14:18 ` Paolo Carlini
2003-01-30 15:56 Volker Reichelt
2003-01-30 17:57 ` Gabriel Dos_Reis
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=20030130175358.A23185@synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=gschafer@zip.com.au \
--cc=pcarlini@unitus.it \
/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).