From: Peter Wu <peterwu@canada.com>
Cc: ding@gnus.org
Subject: Re: New make.bat, give it a try
Date: Sat, 08 Mar 2003 22:51:39 +0800 [thread overview]
Message-ID: <86el5hq5c4.fsf@vanilla.bsd> (raw)
In-Reply-To: <ullzr1161.fsf@pille.fhaun.de> (Frank Haun's message of "Fri, 07 Mar 2003 19:28:38 +0100")
Frank Haun <pille3003@fhaun.de> writes:
> "Peter Wu" <peterwu@canada.com> writes:
>
>> I tried to execute 'newmake C:\emacs-21.2 /copy' and got the following
>> prompt to ask me to use make.bat.
>>
>> <newmake.bat>
>> Usage: make.bat :emacs-dir: [/copy]
>>
>> where: :emacs-dir: is the directory your emacs.exe respectively xemacs.exe
>> resides in, e.g. G:\Programme\XEmacs\XEmacs-21.4.11\i586-pc-win32\
>> or G:\Emacs\bin
> ^^^^
>
> Therefore you've to say
>
> »newmake C:\emacs-21.2\bin /copy«
Sorry for my carelessness. :(
Your newmake.bat works fine but I don't see anything different from the
make.bat included in the tarball.
--
Peter Wu
Powered by FreeBSD 4.8-RC
This posting is provided "AS IS" with no warranties, and confers no rights.
next prev parent reply other threads:[~2003-03-08 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 10:49 Frank Schmitt
2003-03-05 17:16 ` Peter Wu
2003-03-05 17:40 ` Frank Schmitt
[not found] ` <86heag1wph.fsf@vanilla.zzz>
2003-03-06 15:22 ` Frank Schmitt
2003-03-07 5:27 ` Peter Wu
2003-03-07 17:02 ` Kai Großjohann
2003-03-07 18:28 ` Frank Haun
2003-03-08 14:51 ` Peter Wu [this message]
2003-03-08 17:40 ` Frank Haun
2003-03-06 11:00 ` Han Pilmeyer
2003-03-06 11:29 ` Frank Schmitt
2003-03-06 12:00 ` Even newer make.bat (was: New make.bat, give it a try) Frank Schmitt
2003-03-06 23:33 ` Even newer make.bat Frank Haun
2003-03-07 8:41 ` Frank Schmitt
2003-03-07 18:22 ` Frank Haun
2003-03-09 14:14 ` Reiner Steib
2003-03-10 7:04 ` Frank Schmitt
2003-03-06 12:15 ` New make.bat, give it a try Norbert Koch
2003-03-06 12:22 ` Han Pilmeyer
2003-03-06 16:21 ` Frank Schmitt
2003-03-06 17:23 ` Han Pilmeyer
2003-03-06 18:37 ` Frank Schmitt
2003-03-06 21:56 ` Han Pilmeyer
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=86el5hq5c4.fsf@vanilla.bsd \
--to=peterwu@canada.com \
--cc=ding@gnus.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.
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).