From: "Dhruva Krishnamurthy" <devel@member.fsf.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: gmake info: makefile patch
Date: Mon, 03 May 2004 16:58:35 +0530 [thread overview]
Message-ID: <1083583715.8682.185530670@webmail.messagingengine.com> (raw)
In-Reply-To: <ur7u1aix0.fsf@jasonrumney.net>
> > Also, I noticed "gmake info" failes on MinGW-GCC on W2K. The problem is
> > with backslash ("\") in makefile.w32-in at target "info:". Changing it
> > to forward slashes "/", fixes this problem.
>
> nmake seems to accept either, so I've installed this fix.
It has to be done in emacs/nt/makefile.w32-in file (not in
man/makefile.w32-in). Sorry for not being more specific.
-dhruva
Diff for original versus modified [diff -p
\tmp\cvs\emacs\nt\makefile.w32-in makefile.w32-in]
*** \tmp\cvs\emacs\nt\makefile.w32-in Fri Apr 23 09:16:57 2004
--- makefile.w32-in Mon May 3 12:59:23 2004
*************** force-info:
*** 218,226 ****
# put the info files in $(infodir),
# so we can do ok running make in the build dir.
info: force-info
! (cd ..\man && $(MAKE) $(MFLAGS) info)
! (cd ..\lispref && $(MAKE) $(MFLAGS) info)
! (cd ..\lispintro && $(MAKE) $(MFLAGS) info)
#
# Maintenance
--- 218,226 ----
# put the info files in $(infodir),
# so we can do ok running make in the build dir.
info: force-info
! (cd ../man && $(MAKE) $(MFLAGS) info)
! (cd ../lispref && $(MAKE) $(MFLAGS) info)
! (cd ../lispintro && $(MAKE) $(MFLAGS) info)
#
# Maintenance
________________________________________
Dhruva Krishnamurthy
Proud FSF member: #1935
http://schemer.fateback.com/
next prev parent reply other threads:[~2004-05-03 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 6:07 addpm.c: DdeConnect() without timeout Dhruva Krishnamurthy
2004-05-03 10:45 ` Jason Rumney
2004-05-03 11:28 ` Dhruva Krishnamurthy [this message]
2004-05-03 11:35 ` Dhruva Krishnamurthy
2004-05-03 14:51 ` Benjamin Riefenstahl
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=1083583715.8682.185530670@webmail.messagingengine.com \
--to=devel@member.fsf.org \
--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).