From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: Final version of newmake.bat
Date: Wed, 19 Mar 2003 23:36:14 +0100 [thread overview]
Message-ID: <ufzpj3rxd.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <uu1dz5rd4.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> The compilation buffer ends with
> "Compilation exited abnormally with code 1 at Wed Mar 19 08:51:57"
No idea about this one, however this is an Emacs message and I don't
think we can blame newmake.bat for this. This one comes before the
processing of info files, does it?
>> The error message above means that newmake.bat couldn't find the files
>> message-1 and message-2 in the texi directory so it seems that
>> generation of info files failed.
>
> It appears, to me at least, that message.texi generated only one file "message".
Indeed, if infohack.el is used to create the info files, only message
is created, while makeinfo creates message, message-1 and message-2.
This is weird and looks like a bug to me, but again I don't think that
newmake.bat is responsible but either infohack.el or message.texi.
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
next prev parent reply other threads:[~2003-03-19 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 23:43 Frank Schmitt
2003-03-19 6:43 ` Kevin Greiner
2003-03-19 7:16 ` Frank Schmitt
2003-03-19 15:05 ` Kevin Greiner
2003-03-19 22:36 ` Frank Schmitt [this message]
2003-03-20 0:25 ` Kevin Greiner
2003-03-20 9:00 ` Frank Schmitt
2003-03-20 22:57 ` But this one really is final (was: Final version of newmake.bat) Frank Schmitt
2003-03-21 5:59 ` But this one really is final Kevin Greiner
2003-03-21 7:50 ` Frank Schmitt
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=ufzpj3rxd.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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 NNTP newsgroup(s).