[Top][All Lists]

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

Re: Building Emacs from a new MinGW environment

From: Dani Moncayo
Subject: Re: Building Emacs from a new MinGW environment
Date: Tue, 17 Sep 2013 22:29:43 +0200

>> > OK, then we could put this line
>> >
>> >   test "$MSYSTEM" = "MINGW32" && srcdir=`(cd "$srcdir"; pwd -W)`
>> >
>> > immediately below the 'esac' in the fragment I've shown.  Does that do
>> > the job for you?
>> I've tried it but the bootstrap fails.  I'm attaching the output of
>> the corresponding "make bootstrap" .
> I don't understand where did the
> C:/msys/home/d.moncayo.melgar/emacs/emacs.git/ directory come from?
> Does directory by such name indeed exist on your disk, and Windows
> (not MSYS) can find it?  Did you try this from a directory different
> from where you made your previous trials?

That directory is simply the root of my local Emacs source code tree.
I guess that what confused you is the "d.moncayo.melgar" part, which
was "dani" in previous messages.  Well, the difference is due that one
is the desktop I use at work, and the other is my personal laptop.
But the build environment is equal in both machines (modulo the user

> If the directory exists, I don't understand the reason for these
> failures:
>   /bin/makeinfo --force --enable-encoding -I 
> C:/msys/home/d.moncayo.melgar/emacs/emacs.git/doc/lispref/../emacs -I 
> C:/msys/home/d.moncayo.melgar/emacs/emacs.git/doc/lispref --no-split -o 
> C:/msys/home/d.moncayo.melgar/emacs/emacs.git/doc/lispref/../../info/elisp.info
>  C:/msys/home/d.moncayo.melgar/emacs/emacs.git/doc/lispref/elisp.texi
>   C:/msys/home/d.moncayo.melgar/emacs/emacs.git/doc/lispref/elisp.texi:58: 
> @include `emacsver.texi': No such file or directory.
> Is this some problem with the MSYS port of makeinfo, perhaps?

I've always used the makeinfo that comes with MSYS, yes.  But that
version have always worked fine for me.  This problem appears just
when I try your proposed change in "configure.ac".

>> But the general principle is that, it is conceptually wrong to do
>> conversions of pathnames from MSYS format to native windows format
>> based on pattern substitution, assuming that the MSYS paths will
>> always be either in "/X/whatever" format or in "X:/whatever" format.
> If the change in configure.ac works, we will be able to remove almost
> all of that stuff in top-level Makefile.

Great.  I hope we will get this to work  ;).

>> Therefore, whenever we need to convert pathnames from any
>> MSYS-compliant format to the windows-native counterpart, the only
>> reliable way is using the "pwd -W" feature.
> That's what my suggestion tries to do, but in a single place.

Mmmm but your suggested change doesn't to work for me.

I've tried it again:  autogen.sh + msysconfig.sh + "make bootstrap",
with this single change in my Emacs tree:

  diff --git a/configure.ac b/configure.ac
  index 86a5f30..cb8f6d6 100644
  --- a/configure.ac
  +++ b/configure.ac
  @@ -443,6 +443,8 @@ case "${srcdir}" in
     *  ) srcdir=`(cd "$srcdir"; pwd)` ;;

  +test "$MSYSTEM" = "MINGW32" && srcdir=`(cd "$srcdir"; pwd -W)`
   ### Canonicalize the configuration name.


The result in my laptop seems to be the same than in my office
desktop: autogen ok, configure ok, but bootstrap failure  (new logfile

Perhaps you could try this yourself.  It should be pretty easy.  Just
move or copy the emacs source code under your MSYS' home directory,
and try to configure & bootstrap avoiding "long" pathnames.

>> > In any case, the problem with src/.gdbinit in the build tree still
>> > needs to be solved; no amount of changes in the Makefile's can do
>> > that, because that file is created by config.status.  So we still need
>> > something in configure.ac as well.
>> FWIW, with the last change you suggested, the file "src/.gdbinit" in
>> the build tree now contains this:
>>    source C:/msys/home/d.moncayo.melgar/emacs/emacs.git/src/.gdbinit
> Is this the correct file name, or isn't it?

Yes, that is correct.

Dani Moncayo

Attachment: make-bootstrap.zip
Description: Zip archive

reply via email to

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