From: Chong Yidong <cyd@physics.stanford.edu>
Subject: Re: options/config for the CVS built
Date: 08 Mar 2005 05:46:17 -0800 [thread overview]
Message-ID: <lcu0nml07q.fsf@physics.stanford.edu> (raw)
In-Reply-To: yf8psyadcv4.fsf@rayserv.ban.in.bosch.com
> I think this is the best time to come up with a document which
> describes the correct steps (under present circumstances... I mean
> about the location of tools and their links as of now). Most of us
> have a collection of MinGW32 tools collected over the years + built
> versions of tools which are not part of MinGW32. Hence, we (atleast
> I) have a non-standard MinGW32 setup which works fine for GNU Emacs
> build. Due to this, we fail to notice sour points which makes it
> impossible to proceed with the build.
FWIW, I compile CVS Emacs on a bog-standard MingW distribution, with
no other packages from GnuWin32 or anywhere else, and using
mingw32-make.exe (renamed to make.exe). However, I have to make two
small changes by hand to lisp/makefile to get it to bootstrap
properly.
On line 500 (in autoloads):
! $(DQUOTE)$(lisp)/loaddefs.el$(DQUOTE))$(ARGQUOTE) \
! -f batch-update-autoloads $(lisp) $(WINS)
-->
! $(DQUOTE)loaddefs.el$(DQUOTE))$(ARGQUOTE) \
! -f batch-update-autoloads . $(WINS)
I mentioned this on the list before, but Eli said that the problem was
with MingW make. Ah well.
next prev parent reply other threads:[~2005-03-08 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 12:15 options/config for the CVS built Gnooby
2005-03-07 12:28 ` Chong Yidong
2005-03-07 15:51 ` Gnooby
2005-03-08 3:40 ` Dhruva Krishnamurthy
2005-03-08 13:46 ` Chong Yidong [this message]
2005-03-08 4:40 ` Eli Zaretskii
2005-03-07 12:48 ` Thien-Thi Nguyen
2005-03-07 15:57 ` Gnooby
2005-03-07 12:59 ` Peter Dyballa
[not found] ` <mailman.2868.1110201986.32256.help-gnu-emacs@gnu.org>
2005-03-08 13:37 ` Chong Yidong
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=lcu0nml07q.fsf@physics.stanford.edu \
--to=cyd@physics.stanford.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).