public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Nightly GCC documentation build broken -- gnatmake lost?
Date: Sun, 01 Apr 2007 01:17:00 -0000	[thread overview]
Message-ID: <20070401011715.GA23554@ednor.casa.cgf.cx> (raw)
In-Reply-To: <Pine.LNX.4.64.0704010216010.8297@acrux.dbai.tuwien.ac.at>

On Sun, Apr 01, 2007 at 02:23:40AM +0200, Gerald Pfeifer wrote:
>Recently, the nightly script building GCC documentation in HTML and
>other formats (/home/gccadmin/scripts/update_web_docs_svn) stopped
>working.
>
>The last successfull run I could find in the gccadmin archives:
>  http://gcc.gnu.org/ml/gccadmin/2007-q1/msg00203.html
>
>And the first broken run:
>  http://gcc.gnu.org/ml/gccadmin/2007-q1/msg00205.html
>
>According to the latter, and my manual attempts, the problem is that
>the gnatmake program seems to have disappeared from the gcc.gnu.org/
>sourceware.org machine:
>
>  /home/gccadmin/scripts/update_web_docs_svn: line 117: gnatmake: command not found
>
>I temporarily disabled this part of the documentation build in
>/home/gccadmin/scripts/update_web_docs_svn, and performed a manual run
>to catch up.

Huh.  I thought I fixed this the last time it was reported but I
probably got caught in some interdependency problems and lost track of
what I was doing.

In any event, gnatmake is back.  Sorry for the confusion.

cgf

  reply	other threads:[~2007-04-01  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01  0:23 Gerald Pfeifer
2007-04-01  1:17 ` Christopher Faylor [this message]
2007-04-01 12:15   ` Gerald Pfeifer

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=20070401011715.GA23554@ednor.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=gerald@pfeifer.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).