From: Gerald Pfeifer <gerald@pfeifer.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: overseers@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: /usr/bin/sphinx-1.0-build: Command not found
Date: Sun, 15 Mar 2020 09:55:24 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2003150953260.4184@anthias.pfeifer.com> (raw)
In-Reply-To: <02a6a5c8a7dd0b30502912c0eb6989d6a1a0615d.camel@redhat.com>
On Sat, 14 Mar 2020, David Malcolm wrote:
> [CCing Jakub]
>
> Jakub committed a patch for this on Thursday to the gcc repository:
>
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=a0ae4cbe9d1430b32f674b862a6d8dce0ed81f2a
>
> which I believe ought to fix it (assuming the box in question is now
> running RHEL 8).
Yes, last night I then noticed that the script on gcc.gnu.org had not
been updated - alas my follow-up mail got stuck.
I updated the script in the gccadmin account and ran it again -
successfully this time.
And I will also make the script itself a bit more resilient.
Thanks,
Gerald
next prev parent reply other threads:[~2020-03-15 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 22:46 Gerald Pfeifer
2020-03-15 1:46 ` David Malcolm
2020-03-15 8:55 ` Gerald Pfeifer [this message]
2020-03-15 14:27 ` David Malcolm
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=alpine.LSU.2.21.2003150953260.4184@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=dmalcolm@redhat.com \
--cc=jakub@redhat.com \
--cc=overseers@gcc.gnu.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).