Re: NT mingw/msys build problem

[Guy Gascoigne-Piggford]

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 exits.

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.

Guy


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 problem:
> >
> > 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.
> .