From: "Dhruva Krishnamurthy" <devel@member.fsf.org>
Subject: CVS Emacs - [n]make info fails
Date: Wed, 04 Feb 2004 16:17:50 +0530 [thread overview]
Message-ID: <20040204104750.B16C52F@frontend3.messagingengine.com> (raw)
Hello,
I am building CVS Emacs (HEAD) on W2K using both MSVC 6.0 and MinGW
environment. Building "info" fails in "emacs/lispref" as it fails to
find "index.perm" and "index.unperm". I just copied "index.texi" as
".perm" and ".unperm" to go through the build. Not sure this is correct.
with regards,
dhruva
________________________________________
Dhruva Krishnamurthy
Proud FSF member: #1935
http://schemer.fateback.com/
next reply other threads:[~2004-02-04 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 10:47 Dhruva Krishnamurthy [this message]
2004-02-04 11:12 ` CVS Emacs - [n]make info fails Eli Zaretskii
2004-02-04 11:17 ` Dhruva Krishnamurthy
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040204104750.B16C52F@frontend3.messagingengine.com \
--to=devel@member.fsf.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).