Cron <gccadmin@sourceware> sh /home/gccadmin/scripts/gcc_release -s 4.0:branches/gcc-4_0-branch -l -d /sourceware/snapshot-tmp/gcc all

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 4.0:branches/gcc-4_0-branch -l -d /sourceware/snapshot-tmp/gcc all
Date: Thu, 05 Oct 2006 22:41:00 -0000	[thread overview]
Message-ID: <20061005223201.22931.qmail@sourceware.org> (raw)

gcc_release: Retrieving sources (svn export -r 117468 file:///svn/gcc/branches/gcc-4_0-branch)
Touching intl/configure...
Touching intl/config.h.in...
Touching gcc/cstamp-h.in...
Touching gcc/config.in...
Touching gcc/config/arm/arm-tune.md...
Touching boehm-gc/aclocal.m4...
Touching boehm-gc/Makefile.in...
Touching boehm-gc/configure...
Touching libffi/aclocal.m4...
Touching libffi/Makefile.in...
Touching libffi/configure...
Touching libffi/fficonfig.h.in...
Touching libgfortran/Makefile.in...
Touching libjava/aclocal.m4...
Touching libjava/Makefile.in...
Touching libjava/configure...
Touching libjava/libltdl/config-h.in...
Touching libcpp/aclocal.m4...
Touching libcpp/Makefile.in...
Touching libcpp/configure...
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
mv: cannot stat `../objdir/libcpp/po/*.gmo': No such file or directory
gcc_release: Building tarfiles
tar: gcc-4.0-20061005/gnattools: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors
Not building gcc-g77-4.0-20061005 tarfile
gcc_release: Building diffs against version 4.0-20060928
gcc_release: /var/ftp/pub/gcc/snapshots/4.0-20060928/gcc-g77-4.0-20060928.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:[~2006-10-05 22:41 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 22:41 Cron Daemon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-28 22:42 Cron Daemon
2007-01-21 22:41 Cron Daemon
2007-01-14 22:41 Cron Daemon
2007-01-07 22:42 Cron Daemon
2007-01-04 22:43 Cron Daemon
2006-12-28 22:40 Cron Daemon
2006-12-21 22:41 Cron Daemon
2006-12-14 22:40 Cron Daemon
2006-12-07 22:42 Cron Daemon
2006-11-30 22:45 Cron Daemon
2006-11-23 22:40 Cron Daemon
2006-11-16 22:40 Cron Daemon
2006-11-09 22:40 Cron Daemon
2006-11-02 22:41 Cron Daemon
2006-10-26 22:43 Cron Daemon
2006-10-19 22:42 Cron Daemon
2006-10-12 22:41 Cron Daemon
2006-09-28 22:41 Cron Daemon
2006-09-21 22:43 Cron Daemon
2006-09-14 22:39 Cron Daemon
2006-09-07 22:39 Cron Daemon
2006-08-31 22:40 Cron Daemon
2006-08-24 22:43 Cron Daemon
2006-08-17 22:39 Cron Daemon
2006-08-10 22:39 Cron Daemon
2006-08-03 22:40 Cron Daemon
2006-07-27 22:42 Cron Daemon
2006-07-20 22:40 Cron Daemon
2006-07-13 22:42 Cron Daemon
2006-07-06 22:42 Cron Daemon
2006-06-29 22:39 Cron Daemon
2006-06-22 22:41 Cron Daemon
2006-06-15 22:40 Cron Daemon
2006-06-08 22:41 Cron Daemon
2006-06-01 22:39 Cron Daemon
2006-05-25 22:40 Cron Daemon
2006-05-18 22:40 Cron Daemon
2006-05-11 22:39 Cron Daemon
2006-05-04 22:40 Cron Daemon
2006-04-27 22:44 Cron Daemon
2006-04-20 22:40 Cron Daemon
2006-04-13 22:41 Cron Daemon
2006-04-06 22:40 Cron Daemon
2006-03-30 22:42 Cron Daemon
2006-03-23 22:49 Cron Daemon
2006-03-16 22:41 Cron Daemon
2006-03-09 22:40 Cron Daemon
2006-03-02 22:40 Cron Daemon
2006-02-23 22:41 Cron Daemon
2006-02-16 22:39 Cron Daemon
2006-02-09 22:41 Cron Daemon
2006-02-02 22:42 Cron Daemon
2006-01-26 22:42 Cron Daemon
2006-01-19 22:42 Cron Daemon
2006-01-12 22:42 Cron Daemon
2006-01-05 22:39 Cron Daemon
2005-12-29 22:40 Cron Daemon
2005-12-22 22:40 Cron Daemon
2005-12-15 22:44 Cron Daemon
2005-12-08 22:42 Cron Daemon
2005-12-01 22:40 Cron Daemon
2005-11-24 22:39 Cron Daemon
2005-11-17 22:40 Cron Daemon
2005-11-10 22:39 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=20061005223201.22931.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: 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).