This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
PATCH: maintainer-scripts/gcc_release and problems with diff generation
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Mark Mitchell <mark at codesourcery dot com>,Ranjit Mathew <rmathew at hotmail dot com>
- Date: Tue, 27 May 2003 15:32:07 +0200 (CEST)
- Subject: PATCH: maintainer-scripts/gcc_release and problems with diff generation
After I tweaked gcc_release, yesterday's snapshot did not come with diff
files, yet http://gcc.gnu.org/ml/gccadmin/2003-q2/msg00119.html and my
local tests did not indicate any problem.
Clearly, we should warn in case of such problems, so I committed the
following change to mainline and will also commit to the 3.3-branch
after the next snapshot exercising this code-path has been generated
flawlessly (unless Mark strongly prefers otherwise).
2003-05-27 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* gcc_release (build_diffs): Add diagnostics in case we cannot
generate a specific diff file.
Gerald
Index: gcc_release
===================================================================
RCS file: /cvs/gcc/gcc/maintainer-scripts/gcc_release,v
retrieving revision 1.25
diff -u -3 -p -r1.25 gcc_release
--- gcc_release 23 May 2003 22:55:50 -0000 1.25
+++ gcc_release 27 May 2003 10:12:29 -0000
@@ -306,7 +306,11 @@ build_diffs() {
for f in gcc gcc-ada gcc-g++ gcc-g77 gcc-java gcc-objc gcc-testsuite gcc-core; do
old_tar=${old_dir}/${f}-${old_vers}.tar.gz
new_tar=${WORKING_DIRECTORY}/${f}-${RELEASE}.tar.gz
- if [ -e $old_tar ] && [ -e $new_tar ]; then
+ if [ ! -e $old_tar ]; then
+ inform "$old_tar not found; not generating diff file"
+ elif [ ! -e $new_tar ]; then
+ inform "$new_tar not found; not generating diff file"
+ else
build_diff $old_tar gcc-${old_vers} $new_tar gcc-${RELEASE} \
${f}-${old_vers}-${RELEASE}.diff.gz
fi