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.1:branches/gcc-4_1-branch -l -d /sourceware/snapshot-tmp/gcc all Date: Fri, 19 May 2006 22:42:00 -0000 [thread overview] Message-ID: <20060519223202.30880.qmail@sourceware.org> (raw) gcc_release: Retrieving sources (svn export -r 113915 file:///svn/gcc/branches/gcc-4_1-branch) Touching fixincludes/config.h.in... 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 libobjc/configure... 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/configure... 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 Not building gcc-g77-4.1-20060519 tarfile gcc_release: Building diffs against version 4.1-20060512 gcc_release: /var/ftp/pub/gcc/snapshots/4.1-20060512/gcc-g77-4.1-20060512.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-05-19 22:42 UTC|newest] Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-19 22:42 Cron Daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2008-06-30 22:40 Cron Daemon 2008-06-23 22:43 Cron Daemon 2008-06-16 22:40 Cron Daemon 2008-06-09 22:40 Cron Daemon 2008-06-02 22:43 Cron Daemon 2008-05-26 22:41 Cron Daemon 2008-05-19 22:44 Cron Daemon 2008-05-12 22:42 Cron Daemon 2008-05-05 22:41 Cron Daemon 2008-04-28 22:44 Cron Daemon 2008-04-21 22:43 Cron Daemon 2008-04-14 22:43 Cron Daemon 2008-04-07 22:49 Cron Daemon 2008-03-31 22:41 Cron Daemon 2008-03-24 22:42 Cron Daemon 2008-03-17 22:46 Cron Daemon 2008-03-10 22:42 Cron Daemon 2008-03-03 22:40 Cron Daemon 2008-02-25 22:43 Cron Daemon 2008-02-18 22:40 Cron Daemon 2008-02-11 22:42 Cron Daemon 2008-02-04 22:42 Cron Daemon 2008-01-28 22:41 Cron Daemon 2008-01-21 22:40 Cron Daemon 2008-01-14 22:42 Cron Daemon 2008-01-07 22:44 Cron Daemon 2007-12-31 22:44 Cron Daemon 2007-12-24 22:42 Cron Daemon 2007-12-17 22:45 Cron Daemon 2007-12-10 22:44 Cron Daemon 2007-12-03 22:41 Cron Daemon 2007-11-26 22:43 Cron Daemon 2007-11-19 22:43 Cron Daemon 2007-11-12 22:43 Cron Daemon 2007-11-05 22:41 Cron Daemon 2007-10-29 22:43 Cron Daemon 2007-10-22 22:44 Cron Daemon 2007-10-15 22:41 Cron Daemon 2007-10-08 22:44 Cron Daemon 2007-10-01 22:40 Cron Daemon 2007-09-24 22:42 Cron Daemon 2007-09-17 22:48 Cron Daemon 2007-09-10 22:41 Cron Daemon 2007-09-03 22:44 Cron Daemon 2007-08-27 22:45 Cron Daemon 2007-08-20 22:45 Cron Daemon 2007-08-13 22:45 Cron Daemon 2007-08-06 22:46 Cron Daemon 2007-07-30 22:40 Cron Daemon 2007-07-23 22:41 Cron Daemon 2007-07-16 22:39 Cron Daemon 2007-07-09 22:43 Cron Daemon 2007-07-02 22:40 Cron Daemon 2007-06-25 22:41 Cron Daemon 2007-06-18 22:41 Cron Daemon 2007-06-11 22:42 Cron Daemon 2007-06-04 22:40 Cron Daemon 2007-05-28 22:41 Cron Daemon 2007-05-21 22:57 Cron Daemon 2007-05-14 22:52 Cron Daemon 2007-04-30 21:44 Cron Daemon 2007-04-23 21:41 Cron Daemon 2007-04-16 21:42 Cron Daemon 2007-04-09 21:42 Cron Daemon 2007-04-02 21:41 Cron Daemon 2007-03-26 21:44 Cron Daemon 2007-03-19 22:44 Cron Daemon 2007-03-12 22:42 Cron Daemon 2007-03-05 22:45 Cron Daemon 2007-02-26 22:43 Cron Daemon 2007-02-19 22:44 Cron Daemon 2007-02-12 22:43 Cron Daemon 2007-02-05 22:48 Cron Daemon 2007-01-29 22:44 Cron Daemon 2007-01-22 22:42 Cron Daemon 2007-01-15 22:43 Cron Daemon 2007-01-08 22:45 Cron Daemon 2006-12-29 22:40 Cron Daemon 2006-12-22 22:43 Cron Daemon 2006-12-15 22:43 Cron Daemon 2006-12-08 22:43 Cron Daemon 2006-12-01 22:42 Cron Daemon 2006-11-24 22:43 Cron Daemon 2006-11-17 22:42 Cron Daemon 2006-11-10 22:45 Cron Daemon 2006-11-03 22:43 Cron Daemon 2006-10-27 22:46 Cron Daemon 2006-10-20 22:41 Cron Daemon 2006-10-13 22:41 Cron Daemon 2006-10-06 22:43 Cron Daemon 2006-09-29 22:41 Cron Daemon 2006-09-22 22:41 Cron Daemon 2006-09-15 22:41 Cron Daemon 2006-09-08 22:41 Cron Daemon 2006-09-01 22:40 Cron Daemon 2006-08-25 22:42 Cron Daemon 2006-08-18 22:43 Cron Daemon 2006-08-11 22:40 Cron Daemon 2006-08-04 22:43 Cron Daemon 2006-07-28 22:43 Cron Daemon 2006-07-21 22:41 Cron Daemon 2006-07-14 22:41 Cron Daemon 2006-07-07 22:41 Cron Daemon 2006-06-30 22:47 Cron Daemon 2006-06-23 22:41 Cron Daemon 2006-06-16 22:43 Cron Daemon 2006-06-09 22:45 Cron Daemon 2006-06-02 22:47 Cron Daemon 2006-05-26 22:40 Cron Daemon 2006-05-12 22:41 Cron Daemon 2006-05-05 22:41 Cron Daemon 2006-04-28 22:41 Cron Daemon 2006-04-21 22:41 Cron Daemon 2006-04-14 22:41 Cron Daemon 2006-04-07 22:40 Cron Daemon 2006-03-31 22:42 Cron Daemon 2006-03-24 22:43 Cron Daemon 2006-03-17 22:44 Cron Daemon 2006-03-10 22:40 Cron Daemon 2006-03-03 22:46 Cron Daemon 2006-02-24 22:43 Cron Daemon 2006-02-17 22:41 Cron Daemon 2006-02-10 22:44 Cron Daemon 2006-02-03 22:42 Cron Daemon 2006-01-27 22:44 Cron Daemon 2006-01-20 22:40 Cron Daemon 2006-01-13 22:41 Cron Daemon 2006-01-06 22:41 Cron Daemon 2005-12-30 22:41 Cron Daemon 2005-12-23 22:41 Cron Daemon 2005-12-16 22:40 Cron Daemon 2005-12-09 22:39 Cron Daemon 2005-12-02 22:46 Cron Daemon 2005-11-25 22:41 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=20060519223202.30880.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).