public inbox for gccadmin@sourceware.org help / color / mirror / Atom feed
From: root@sourceware.org (Cron Daemon) To: gccadmin@sourceware.org Subject: Cron <gccadmin@sourceware> sh /home/gccadmin/scripts/gcc_release -s 3.3:gcc-3_3-branch -l -d /sourceware/snapshot-tmp/gcc all Date: Wed, 08 Dec 2004 23:19:00 -0000 [thread overview] Message-ID: <20041208223201.8270.qmail@sourceware.org> (raw) gcc_release: Tagging sources as gcc-ss-3_3-20041208 cvs rtag: [22:57:54] waiting for rth's lock in /cvs/gcc/gcc/libstdc++-v3/testsuite/27_io/basic_ostream/put cvs rtag: [22:58:24] obtained lock in /cvs/gcc/gcc/libstdc++-v3/testsuite/27_io/basic_ostream/put gcc_release: Retrieving sources (cvs export -rgcc-ss-3_3-20041208 gcc) Touching gcc/cstamp-h.in... Touching gcc/config.in... Touching gcc/ada/treeprs.ads... Touching gcc/ada/einfo.h... Touching gcc/ada/sinfo.h... Touching gcc/ada/nmake.adb... Touching gcc/ada/nmake.ads... Touching libf2c/libI77/stamp-h.in... Touching libf2c/libI77/config.h.in... Touching libf2c/libU77/stamp-h.in... Touching fastjar/Makefile.in... Touching fastjar/stamp-h.in... Touching boehm-gc/aclocal.m4... Touching boehm-gc/Makefile.in... Touching boehm-gc/configure... Touching libjava/aclocal.m4... Touching libjava/Makefile.in... Touching libjava/configure... Touching libjava/libltdl/aclocal.m4... Touching libjava/libltdl/Makefile.in... Touching libjava/libltdl/configure... Touching libjava/libltdl/stamp-h.in... gcc_release: Retrieving HTML documentation gcc_release: Generating plain-text documentation from HTML mv: cannot stat `../objdir/gcc/po/*.gmo': No such file or directory gcc_release: Building tarfiles tar: gcc-3.3-20041208/libada: Cannot stat: No such file or directory tar: Error exit delayed from previous errors Not building gcc-fortran-3.3-20041208 tarfile gcc_release: Building diffs against version 3.3-20041201 gcc_release: /var/ftp/pub/gcc/snapshots/3.3-20041201/gcc-fortran-3.3-20041201.tar.bz2 not found; not generating diff file gcc_release: Uploading files gcc_release: Updating links and READMEs on the FTP server gcc_release: Sending mail
next reply other threads:[~2004-12-08 23:19 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-08 23:19 Cron Daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2005-05-18 23:53 Cron Daemon 2005-05-11 23:46 Cron Daemon 2005-05-05 0:22 Cron Daemon 2005-04-27 23:49 Cron Daemon 2005-04-20 23:43 Cron Daemon 2005-04-13 23:59 Cron Daemon 2005-04-07 0:50 Cron Daemon 2005-03-30 23:50 Cron Daemon 2005-03-23 23:50 Cron Daemon 2005-03-16 23:26 Cron Daemon 2005-03-09 23:29 Cron Daemon 2005-03-02 23:26 Cron Daemon 2005-02-23 23:50 Cron Daemon 2005-02-16 23:21 Cron Daemon 2005-02-10 0:06 Cron Daemon 2005-01-26 23:47 Cron Daemon 2005-01-20 0:15 Cron Daemon 2005-01-12 23:24 Cron Daemon 2005-01-05 23:33 Cron Daemon 2004-12-29 23:22 Cron Daemon 2004-12-22 23:24 Cron Daemon 2004-12-15 23:42 Cron Daemon 2004-12-01 23:26 Cron Daemon 2004-11-24 23:17 Cron Daemon 2004-11-17 23:32 Cron Daemon 2004-11-10 23:35 Cron Daemon 2004-11-03 23:12 Cron Daemon 2004-10-27 23:33 Cron Daemon 2004-10-20 22:38 Cron Daemon 2004-10-13 23:19 Cron Daemon 2004-10-06 23:25 Cron Daemon 2004-09-29 23:14 Cron Daemon 2004-09-22 23:17 Cron Daemon 2004-09-15 23:45 Cron Daemon 2004-09-08 23:13 Cron Daemon 2004-09-01 23:24 Cron Daemon 2004-08-25 23:37 Cron Daemon 2004-08-18 23:39 Cron Daemon 2004-08-11 23:31 Cron Daemon 2004-07-28 23:11 Cron Daemon 2004-07-21 23:10 Cron Daemon 2004-07-14 23:14 Cron Daemon 2004-07-07 23:42 Cron Daemon 2004-06-30 23:10 Cron Daemon 2004-06-23 23:21 Cron Daemon 2004-06-16 23:18 Cron Daemon 2004-06-09 23:00 Cron Daemon 2004-06-02 23:03 Cron Daemon 2004-05-26 23:28 Cron Daemon 2004-05-19 23:11 Cron Daemon 2004-05-12 22:54 Cron Daemon 2004-05-05 23:15 Cron Daemon
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=20041208223201.8270.qmail@sourceware.org \ --to=root@sourceware.org \ --cc=gccadmin@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: linkBe 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).