From: Jean-Pierre Radley <jpr@jpr.com>
To: EGCS Developers <egcs@cygnus.com>
Subject: failed compilation.
Date: Sat, 04 Apr 1998 20:05:00 -0000 [thread overview]
Message-ID: <19980404204936.10889@jpr.com> (raw)
SCO Openserver 5.0.4.
I just did a totally new fetch, with 'cvs checkout egcs'.
I'm compiling in the directory /s/tools/egcs/obj.
It crashes, as it has all this past week, like so:
Making all in po
make[3]: Entering directory `/s/tools/egcs/obj/texinfo/po'
PATH=../src:$PATH : --default-domain=texinfo --directory=../../../texinfo \
--add-comments --keyword=_ --keyword=N_ \
--files-from=../../../texinfo/po/POTFILES.in
rm -f ../../../texinfo/po/texinfo.pot
mv texinfo.po ../../../texinfo/po/texinfo.pot
mv: cannot access texinfo.po: No such file or directory (error 2)
make[3]: *** [../../../texinfo/po/texinfo.pot] Error 2
make[3]: Leaving directory `/s/tools/egcs/obj/texinfo/po'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/s/tools/egcs/obj/texinfo'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/s/tools/egcs/obj/texinfo'
make: *** [all-texinfo] Error 2
--
Jean-Pierre Radley <jpr@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
next reply other threads:[~1998-04-04 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-04 20:05 Jean-Pierre Radley [this message]
1998-04-05 9:02 ` Gerald Pfeifer
1998-04-05 17:27 ` Jean-Pierre Radley
-- strict thread matches above, loose matches on Subject: below --
1998-05-20 19:03 Failed compilation Jean-Pierre Radley
1998-05-20 23:27 ` Jeffrey A Law
1998-04-04 14:20 K. Berry
1998-04-29 16:08 ` Ulrich Drepper
1998-03-28 19:24 Jean-Pierre Radley
1998-03-30 16:18 ` Robert Lipe
1998-03-31 0:46 ` Jean-Pierre Radley
1998-04-04 11:01 ` Philippe De Muyter
1998-04-03 21:52 ` Jim Wilson
1998-04-04 11:01 ` Philippe De Muyter
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=19980404204936.10889@jpr.com \
--to=jpr@jpr.com \
--cc=egcs@cygnus.com \
/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).