Make check in trunk

Make check in trunk

[Fabrice Popineau]

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Hi all,

I compiled the latest trunk revno: 117656 with mingw64, so I'm running
under Windows.
At the moment, running 'make check' stops waiting and I have to interrupt
it.

It gets stuck at the end of Python test.
This is the end of test/automates/python-tests.log:

   passed  103/145  python-shell-calculate-process-environment-1
   passed  104/145  python-shell-calculate-process-environment-2
   passed  105/145  python-shell-calculate-process-environment-3
Can't guess python-indent-offset, using defaults: 4
Can't guess python-indent-offset, using defaults: 4
Making python-shell-interpreter local to
*Python[c:/Users/Fabrice/AppData/Local/Temp/python-tests18084jIp.py]* while
let-bound!
Making python-shell-interpreter-args local to
*Python[c:/Users/Fabrice/AppData/Local/Temp/python-tests18084jIp.py]* while
let-bound!

Any idea of what's going on?

Best regards,

Fabrice

[-- Attachment #2: Type: text/html, Size: 1194 bytes --]

Re: Make check in trunk

[Fabrice Popineau]

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

Well, a long time after mentioning this problem.

It seems that what's going on is a bug in msys2 ncurses:
http://sourceforge.net/p/msys2/tickets/32/?limit=25

FWIW, I have added a couple of "-i" arguments to the python that is
launched during 'make check'
and things are running.

Best regards;

Fabrice



2014-08-06 22:51 GMT+02:00 Fabrice Popineau <fabrice.popineau@gmail.com>:

> Hi all,
>
> I compiled the latest trunk revno: 117656 with mingw64, so I'm running
> under Windows.
> At the moment, running 'make check' stops waiting and I have to interrupt
> it.
>
> It gets stuck at the end of Python test.
> This is the end of test/automates/python-tests.log:
>
>    passed  103/145  python-shell-calculate-process-environment-1
>    passed  104/145  python-shell-calculate-process-environment-2
>    passed  105/145  python-shell-calculate-process-environment-3
> Can't guess python-indent-offset, using defaults: 4
> Can't guess python-indent-offset, using defaults: 4
> Making python-shell-interpreter local to
> *Python[c:/Users/Fabrice/AppData/Local/Temp/python-tests18084jIp.py]* while
> let-bound!
> Making python-shell-interpreter-args local to
> *Python[c:/Users/Fabrice/AppData/Local/Temp/python-tests18084jIp.py]* while
> let-bound!
>
> Any idea of what's going on?
>
> Best regards,
>
> Fabrice
>

[-- Attachment #2: Type: text/html, Size: 2123 bytes --]

Re: Make check in trunk

[Eli Zaretskii]

> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Tue, 2 Sep 2014 08:01:20 +0200
> 
> Well, a long time after mentioning this problem.
> 
> It seems that what's going on is a bug in msys2 ncurses:
> http://sourceforge.net/p/msys2/tickets/32/?limit=25
> 
> FWIW, I have added a couple of "-i" arguments to the python that is
> launched during 'make check'
> and things are running.

Thanks.

What would be the reasons for anyone to switch from MSYS to MSYS2?

Re: Make check in trunk

[Óscar Fuentes]

Eli Zaretskii <eliz@gnu.org> writes:

> What would be the reasons for anyone to switch from MSYS to MSYS2?

MSYS2 has lots of up-to-date packages which are straightforward to
install. Starting from zero, you can setup the complete requirements for
building Emacs as fast as your Internet connection allows.

And the same applies to the 64 bits environment.

Re: Make check in trunk

[Eli Zaretskii]

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Tue, 02 Sep 2014 17:59:53 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What would be the reasons for anyone to switch from MSYS to MSYS2?
> 
> MSYS2 has lots of up-to-date packages which are straightforward to
> install. Starting from zero, you can setup the complete requirements for
> building Emacs as fast as your Internet connection allows.

OK, but I asked about switching from MSYS, which presumes that such an
environment based on MSYS is already set up.  Why would one want to
switch?

Re: Make check in trunk

[Óscar Fuentes]

Eli Zaretskii <eliz@gnu.org> writes:

>> > What would be the reasons for anyone to switch from MSYS to MSYS2?
>> 
>> MSYS2 has lots of up-to-date packages which are straightforward to
>> install. Starting from zero, you can setup the complete requirements for
>> building Emacs as fast as your Internet connection allows.
>
> OK, but I asked about switching from MSYS, which presumes that such an
> environment based on MSYS is already set up.  Why would one want to
> switch?

As mentioned, you have updates (MSYS2 maintainers are very quick at
following upstream releases) and a 64 bit environment (something that
MSYS/MinGW doesn't provide.)

Now speaking from the user or prospective contributor, including a MSYS2
bash script that installs the requirements would lower the threshold for
those who wants to track the development sources. Do you think it is a
good idea?

Re: Make check in trunk

[Andy Moreton]

On Tue 02 Sep 2014, Eli Zaretskii wrote:

>> From: Óscar Fuentes <ofv@wanadoo.es>
>> Date: Tue, 02 Sep 2014 17:59:53 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > What would be the reasons for anyone to switch from MSYS to MSYS2?
>> 
>> MSYS2 has lots of up-to-date packages which are straightforward to
>> install. Starting from zero, you can setup the complete requirements for
>> building Emacs as fast as your Internet connection allows.
>
> OK, but I asked about switching from MSYS, which presumes that such an
> environment based on MSYS is already set up.  Why would one want to
> switch?

I switched over last week, in order to start using the Mingw64 compiler
in a painless way. The MSYS2 environment can be setup in very little
time, and a GUI installer is available to get started.

The package manager (pacman, ported from Arch Linux) handles installing
the toolchains and their dependencies. The package archives include all
of the optional dependencies for emacs on Windows (image libaries, XML,
GnuTLS etc).

HTH,

    AndyM

Re: Make check in trunk

[Eli Zaretskii]

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Tue, 02 Sep 2014 18:34:18 +0200
> 
> As mentioned, you have updates (MSYS2 maintainers are very quick at
> following upstream releases) and a 64 bit environment (something that
> MSYS/MinGW doesn't provide.)

Why is it important to have a 64-bit environment in MSYS?  (I'm not
talking about GCC and Binutils, I'm asking about MSYS itself.)

> Now speaking from the user or prospective contributor, including a MSYS2
> bash script that installs the requirements would lower the threshold for
> those who wants to track the development sources. Do you think it is a
> good idea?

I wouldn't know.

Re: Make check in trunk

[Eli Zaretskii]

> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Tue, 02 Sep 2014 18:52:30 +0100
> 
> I switched over last week, in order to start using the Mingw64 compiler
> in a painless way.

Are you saying that MSYS cannot run MinGW64?

If not, what do you mean by "painless"?  What kind of pain did you
experience before?

Re: Make check in trunk

[Óscar Fuentes]

Eli Zaretskii <eliz@gnu.org> writes:

>> As mentioned, you have updates (MSYS2 maintainers are very quick at
>> following upstream releases) and a 64 bit environment (something that
>> MSYS/MinGW doesn't provide.)
>
> Why is it important to have a 64-bit environment in MSYS?  (I'm not
> talking about GCC and Binutils, I'm asking about MSYS itself.)

I guess there is not much about it. Maybe it runs faster than a 32 bits
MSYS on 64 bit OSes, but I have no data. The convenience of having
MinGW-w64 64 bits along with MSYS2 (32 or 64) is a different matter,
because the MSYS2 maintainers certainly will do whatever is in their
power for ensuring a seamless MSYS2/MinGW-w64 experience.

Re: Make check in trunk

[Fabrice Popineau]

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

2014-09-02 16:47 GMT+02:00 Eli Zaretskii <eliz@gnu.org>:

>
> What would be the reasons for anyone to switch from MSYS to MSYS2?
>

To switch ? I don't know. I have installed MSYS2+MINGW64 because it was
newer, very easy to install and use, and provided 64bits gcc.
Up to now, it has been proven reliable. This bug is recent (afaik). I hope
it will be solved soon, but it doesn't prevent
Emacs to run fine.

Fabrice

[-- Attachment #2: Type: text/html, Size: 893 bytes --]

Re: Make check in trunk

[Andy Moreton]

On Tue 02 Sep 2014, Eli Zaretskii wrote:

>> From: Andy Moreton <andrewjmoreton@gmail.com>
>> Date: Tue, 02 Sep 2014 18:52:30 +0100
>> 
>> I switched over last week, in order to start using the Mingw64 compiler
>> in a painless way.
>
> Are you saying that MSYS cannot run MinGW64?
>
> If not, what do you mean by "painless"?  What kind of pain did you
> experience before?

The mingw project is rudderless, and up until only a couple of weeks ago
had been advertising a broken compiler and runtime as its current
release for months.

Setting up a working MSYS/mingw build environment with a consistent set
of libraries for optional emacs features (images, XML, etc.) is a
pain. The mingw/MSYS world does not have any package management worth
the name.

MSYS2 is simply a more recent fork from Cygwin than MSYS. The project
has 32bit and 64bit MSYS2 environments, and packages including mingw and mingw64
(32 and 64bit) toolchains and libs. It is far easier to install a full
consistent set of dependencies with a working package manager.

I want a simple way to get a full featured up to date emacs build, and
then use it for productive work. I do not want to spend my time tracking
down the right combination of tools and libraries (or have to build all
of them myself). At the moment, MSYS2 with a mingw64 toolchain fits that
requirement far better than mingw/MSYS.

    AndyM

Re: Make check in trunk

[Eli Zaretskii]

> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Wed, 03 Sep 2014 00:24:46 +0100
> 
> On Tue 02 Sep 2014, Eli Zaretskii wrote:
> 
> >> From: Andy Moreton <andrewjmoreton@gmail.com>
> >> Date: Tue, 02 Sep 2014 18:52:30 +0100
> >> 
> >> I switched over last week, in order to start using the Mingw64 compiler
> >> in a painless way.
> >
> > Are you saying that MSYS cannot run MinGW64?
> >
> > If not, what do you mean by "painless"?  What kind of pain did you
> > experience before?
> 
> The mingw project is rudderless, and up until only a couple of weeks ago
> had been advertising a broken compiler and runtime as its current
> release for months.
> 
> Setting up a working MSYS/mingw build environment with a consistent set
> of libraries for optional emacs features (images, XML, etc.) is a
> pain. The mingw/MSYS world does not have any package management worth
> the name.
> 
> MSYS2 is simply a more recent fork from Cygwin than MSYS. The project
> has 32bit and 64bit MSYS2 environments, and packages including mingw and mingw64
> (32 and 64bit) toolchains and libs. It is far easier to install a full
> consistent set of dependencies with a working package manager.
> 
> I want a simple way to get a full featured up to date emacs build, and
> then use it for productive work. I do not want to spend my time tracking
> down the right combination of tools and libraries (or have to build all
> of them myself). At the moment, MSYS2 with a mingw64 toolchain fits that
> requirement far better than mingw/MSYS.

Thanks.

Re: Make check in trunk

[Stephen Leake]

Andy Moreton <andrewjmoreton@gmail.com> writes:

> On Tue 02 Sep 2014, Eli Zaretskii wrote:
>
>>> From: Andy Moreton <andrewjmoreton@gmail.com>
>>> Date: Tue, 02 Sep 2014 18:52:30 +0100
>>> 
>>> I switched over last week, in order to start using the Mingw64 compiler
>>> in a painless way.
>>
>> Are you saying that MSYS cannot run MinGW64?

I was under the impression that it could not. It would certainly require
compiling the 64 bit gcc toolchain from scratch; it is _far_ easier to
install MSYS2.

>> If not, what do you mean by "painless"?  What kind of pain did you
>> experience before?
>
> The mingw project is rudderless, and up until only a couple of weeks ago
> had been advertising a broken compiler and runtime as its current
> release for months.
>
> Setting up a working MSYS/mingw build environment with a consistent set
> of libraries for optional emacs features (images, XML, etc.) is a
> pain. The mingw/MSYS world does not have any package management worth
> the name.
>
> MSYS2 is simply a more recent fork from Cygwin than MSYS. The project
> has 32bit and 64bit MSYS2 environments, and packages including mingw and mingw64
> (32 and 64bit) toolchains and libs. It is far easier to install a full
> consistent set of dependencies with a working package manager.
>
> I want a simple way to get a full featured up to date emacs build, and
> then use it for productive work. I do not want to spend my time tracking
> down the right combination of tools and libraries (or have to build all
> of them myself). At the moment, MSYS2 with a mingw64 toolchain fits that
> requirement far better than mingw/MSYS.

+2 :)

-- 
-- Stephe

Re: Make check in trunk

[Eli Zaretskii]

> From: Stephen Leake <stephen_leake@stephe-leake.org>
> Date: Thu, 04 Sep 2014 14:09:57 -0500
> 
> >> Are you saying that MSYS cannot run MinGW64?
> 
> I was under the impression that it could not. It would certainly require
> compiling the 64 bit gcc toolchain from scratch

I don't see why: 32-bit programs (MSYS Bash and Make) can easily
invoke 64-bit programs (MinGW64 GCC and Binutils).

MSYS and MinGW32/MinGW64 are 2 separate parts, and do not depend on
each other.  I was talking only about the MSYS part.