From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Cc: Dhruva Krishnamurthy <dhruva.krishnamurthy@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Build error: "nmake info" in "emacs/man"
Date: Wed, 08 Sep 2004 18:59:44 +0200 [thread overview]
Message-ID: <v9hdq866in.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <01c495b8$Blat.v2.2.2$073bd7e0@zahav.net.il> (Eli Zaretskii's message of "Wed, 08 Sep 2004 18:24:07 +0300")
On Wed, Sep 08 2004, Eli Zaretskii wrote:
>> From: Dhruva Krishnamurthy <dhruva.krishnamurthy@gmail.com>
>>
>> I am trying to build GNU Emacs from CVS Head on W2K using MSVC
>> compiler. I get problems in "nmake info" in "emacs/man" directory. I
>> have diagnosed the cause and made a patch. Please review it and
>> install the same. This affects only the MSVC build on MS-Windows OS.
>
> I don't think this patch is good to install: it breaks the build
> outside the source tree.
Do you refer to "../info" instead of "$(infodir)"? Then it was my
mistake when adding the new Gnus manuals.
Probably it should read as follows (as the other entries
e.g. emacs-mime):
--8<---------------cut here---------------start------------->8---
$(infodir)/sieve: sieve.texi
$(MAKEINFO) sieve.texi
sieve.dvi: sieve.texi
$(ENVADD) $(TEXI2DVI) $(srcdir)/sieve.texi
$(infodir)/pgg: pgg.texi
$(MAKEINFO) pgg.texi
pgg.dvi: pgg.texi
$(ENVADD) $(TEXI2DVI) $(srcdir)/pgg.texi
--8<---------------cut here---------------end--------------->8---
> Why do you need to do that?
Note that Dhruva's change uses $(...) instead of ${...}. Maybe nmake
(MSVC) doesn't accept the latter.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-09-08 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 6:10 Build error: "nmake info" in "emacs/man" Dhruva Krishnamurthy
2004-09-08 12:58 ` Reiner Steib
2004-09-08 15:24 ` Eli Zaretskii
2004-09-08 16:59 ` Reiner Steib [this message]
2004-09-09 3:47 ` Eli Zaretskii
2004-09-09 4:58 ` Dhruva Krishnamurthy
2004-09-09 19:06 ` Eli Zaretskii
2004-09-10 5:57 ` Dhruva Krishnamurthy
2004-09-10 7:36 ` Jason Rumney
2004-09-10 9:22 ` Eli Zaretskii
2004-09-10 9:38 ` Dhruva Krishnamurthy
2004-09-10 11:20 ` Jason Rumney
2004-09-10 12:51 ` Dhruva Krishnamurthy
2004-09-10 13:44 ` Reiner Steib
2004-09-10 18:08 ` Benjamin Riefenstahl
2004-09-10 19:11 ` Peter 'Luna' Runestig
2004-09-11 13:57 ` Benjamin Riefenstahl
2004-09-09 10:44 ` Reiner Steib
2004-09-09 19:14 ` Eli Zaretskii
2004-09-09 7:34 ` Peter 'Luna' Runestig
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=v9hdq866in.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=Reiner.Steib@gmx.de \
--cc=dhruva.krishnamurthy@gmail.com \
--cc=emacs-devel@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.
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).