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 9:branches/gcc-9-branch -l -d /sourceware/snapshot-tmp/gcc all
Date: Sat, 25 May 2019 22:41:00 -0000	[thread overview]
Message-ID: <20190525223201.90832.qmail@sourceware.org> (raw)

gcc_release: Retrieving sources (svn export -r 271623 file:///svn/gcc/branches/gcc-9-branch)
Touching fixincludes/config.h.in...
Touching gcc/cstamp-h.in...
Touching gcc/config.in...
Touching gcc/config/aarch64/aarch64-tune.md...
Touching libobjc/configure...
Touching zlib/aclocal.m4...
Touching zlib/Makefile.in...
Touching zlib/configure...
Touching libada/configure...
Touching libgfortran/aclocal.m4...
Touching libgfortran/Makefile.in...
Touching libquadmath/Makefile.in...
Touching libgfortran/configure...
Touching libgomp/configure.ac...
Touching libgomp/aclocal.m4...
Touching libgomp/Makefile.am...
Touching libgomp/Makefile.in...
Touching libgomp/testsuite/Makefile.in...
Touching libgomp/configure...
Touching libgomp/config.h.in...
Touching libhsail-rt/target-config.h.in...
Touching libitm/aclocal.m4...
Touching libitm/Makefile.in...
Touching libitm/testsuite/Makefile.in...
Touching libitm/configure...
Touching libitm/config.h.in...
Touching libatomic/aclocal.m4...
Touching libatomic/Makefile.in...
Touching libatomic/testsuite/Makefile.in...
Touching libatomic/configure...
Touching libatomic/auto-config.h.in...
Touching libvtv/Makefile.in...
Touching libbacktrace/aclocal.m4...
Touching libbacktrace/Makefile.in...
Touching libbacktrace/configure...
Touching libbacktrace/config.h.in...
Touching libphobos/aclocal.m4...
Touching libphobos/Makefile.in...
Touching libphobos/config.h.in...
Touching libphobos/configure...
Touching libphobos/src/Makefile.in...
Touching libphobos/testsuite/Makefile.in...
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
gcc_release: Building diffs against version 9-20190518
gcc_release: Uploading files
gcc_release: Updating links and READMEs on the FTP server
gcc_release: Sending mail


             reply	other threads:[~2019-05-25 22:41 UTC|newest]

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