From: Dhruva Krishnamurthy <dhruva.krishnamurthy@gmail.com>
Cc: emacs-devel@gnu.org, reiner.steib@gmx.de, Jason Rumney <jasonr@gnu.org>
Subject: Re: Build error: "nmake info" in "emacs/man"
Date: Fri, 10 Sep 2004 15:08:51 +0530 [thread overview]
Message-ID: <68c73b1a04091002386f3c5419@mail.gmail.com> (raw)
In-Reply-To: <01c49717$Blat.v2.2.2$cb768280@zahav.net.il>
On Fri, 10 Sep 2004 12:22:04 +0300, Eli Zaretskii <eliz@gnu.org> wrote:
> > Cc: Eli Zaretskii <eliz@gnu.org>, reiner.steib@gmx.de, emacs-devel@gnu.org
> > From: Jason Rumney <jasonr@gnu.org>
> > Date: Fri, 10 Sep 2004 08:36:10 +0100
>
>
> >
> > Dhruva Krishnamurthy <dhruva.krishnamurthy@gmail.com> writes:
> >
> > > The combination of commands fails in CMD.exe. A simple way to test is
> > > as follows:
> > > D:\tmp\build\emacs\emacs\lisp
> > > dky@MATRIXDEI$ cd . ; dir
> > > The system cannot find the path specified.
> > >
> > > If you need "cd .", we have to do it on seperate lines.
I found an alternate way to do that:
cd $(srcdir) & $(MAKEINFO) pgg.texi
Replace the ';' with '&' and things works with nmake! I tried it in
the makefile.w32-in
> > Right, and that fails in GNU make, which is why the Windows build does
> > not support building Emacs out of the tree.
>
> Okay, if out-of-source builds are not supported on Windows, then I
> withdraw my objections.
>
> (One way to support the out of source tree build is to invoke CMD
> explicitly and use the CMD's method of chaining multiple commands on
> the same command line. A project for a volunteer, I guess.)
>
Let me know the desired behaviour (what out of source build means), I
will be able to do that.
-dhruva
--
Proud FSF member: #1935
http://schemer.fateback.com/
next prev parent reply other threads:[~2004-09-10 9:38 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
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 [this message]
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=68c73b1a04091002386f3c5419@mail.gmail.com \
--to=dhruva.krishnamurthy@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=reiner.steib@gmx.de \
/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).