From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: gcc@gcc.gnu.org
Cc: Mark Mitchell <mark@codesourcery.com>
Subject: `contrib/gcc_update --touch` and snapshots
Date: Sat, 19 Aug 2000 13:49:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.21.0008192241340.56714-100000@deneb.dbai.tuwien.ac.at> (raw)
I'm afraid the following change breaks `contrib/gcc_update --touch`
when used with snapshots, which do contain generated files:
2000-07-13 Mark Mitchell <mark@codesourcery.com>
* gcc_update (files_and_dependencies): Remove generated YACC files.
An example sent to me privately by some user:
# contrib/gcc_update --touch
Touching gcc/config.in...
Touching gcc/java/parse.h...
Touching libf2c/configure...
Touching libf2c/libU77/configure...
# cd $objdir
# make
gmake[1]: Entering directory `/work/egcs-20000814/libiberty'
...snip...
cd cp && gmake ./parse.c
gmake[3]: Entering directory `/work/egcs-20000814/gcc/cp'
expect 33 shift/reduce conflicts and 58 reduce/reduce conflicts.
cd .; bison -d -o parse.c parse.y
bison: not found
gmake[3]: *** [parse.c] Error 127
Perhaps we can/should touch generated files if and only if they already
exist in the local source tree? Thoughts?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next reply other threads:[~2000-08-19 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-19 13:49 Gerald Pfeifer [this message]
2000-08-20 9:23 ` Gerald Pfeifer
2000-08-20 11:09 ` Mark Mitchell
2000-08-20 15:59 ` Bruce Korb
2000-08-23 8:35 ` Jeffrey A Law
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=Pine.BSF.4.21.0008192241340.56714-100000@deneb.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).