[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: NT mingw/msys build problem

From: Fred Kunz
Subject: RE: NT mingw/msys build problem
Date: Mon, 25 Oct 2004 18:15:36 -0700

I also should point out that you need GNUWin32 texinfo to build the info
stuff. I needed to make some minor changes to the generated (after
running configure) makefiles in the lispref and man. I haven't had time
to investigate this further to determine whether there is really a bug
here or not.

-----Original Message-----
From: Fred Kunz 
Sent: Monday, October 25, 2004 6:08 PM
To: Guy Gascoigne-Piggford; Emacs Devel
Subject: RE: NT mingw/msys build problem

Release version of emacs 21.3 builds fine with MinGW
(http://www.mingw.org/download.shtml) and GNUWin32
(http://gnuwin32.sourceforge.net/packages.html) fileutils. The CVS
version also builds and if you want image support you also need to
install the GNUWin32 image libraries. NOTE: You need to make sure the
image library dlls are in your path when you run emacs if you build with
the image libraries. I currently use GNU make 3.80 and gcc 3.4 but I
have also build both the release and the CVS versions of EMACS with GNU
make 3.79 and numerous earlier version of GCC.

Guy if you or anyone else needs more details they can be provided.

-----Original Message-----
From: Guy Gascoigne-Piggford [mailto:address@hidden 
Sent: Monday, October 25, 2004 3:42 PM
To: Emacs Devel
Subject: Re: NT mingw/msys build problem

Hmm, when I try doing a "make SHELL=cmd.exe" all I get is make hanging 
indefinately.  If I try to rename the msys /bin/sh.exe and just run make

then I get a slew of errors about /bin/sh not existing and then make

I'll take a more detailed look at this tonight when I get out of work.

As an aside though, can someone who can actually build emacs on NT tell 
me what environment they use for this?  I thought that I'd make my life 
easier by using mingw and msys, but I'm beginning to realise that this 
was a bit too optimistic.  Clearly there is some way to make this work, 
but it's not particularly obvious to me I'm afraid.


Jason Rumney wrote:

> Guy Gascoigne-Piggford wrote:
>> I've been trying to track down a problem that my NT build has when 
>> building with the latest mingw+msys environment.  Emacs builds and 
>> runs, but certain autoloads seem to be missing, after much hunting 
>> through build logs I ended out with this being the cause of the
>> Eventually make runs this:
>> "./../bin/emacs.exe" -batch --no-init-file --no-site-file --multibyte

>> -l autoload \
>>    --eval '(setq find-file-hooks nil \
>>        find-file-suppress-same-file-warnings t \
>>        generated-autoload-file \
>>          "c:/dev/emacs-src/emacs/lisp/loaddefs.el")' \
>>    -f batch-update-autoloads c:/dev/emacs-src/emacs/lisp calc 
>> calendar emacs-lisp emulation eshell gnus international language mail

>> mh-e net obsolete play progmodes term textmodes toolbar url
>> the output of which is:
>> Wrote 
>> c:/dev/emacs-src/emacs/lisp/c;C:Devmsys.0evacs-srcacslisploaddefs.el
>> Loading vc-cvs...
>> Wrote 
>> c:/dev/emacs-src/emacs/lisp/c;C:Devmsys.0evacs-srcacslisploaddefs.el
>> Autoloads file 
>> c:/dev/emacs-src/emacs/lisp/c;C:Devmsys.0evacs-srcacslisploaddefs.el 
>> does not exist
> I think that looks like what I got when I tried msys several months 
> ago. The workaround I used was "make SHELL=cmd.exe", or rename sh.exe 
> from msys to some other name.
> .

Emacs-devel mailing list

Emacs-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]