[Top][All Lists]

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

Re: Re: Buildbot success in GNU pspp CI on debian-buster-amd64

From: Harry Thijssen
Subject: Re: Re: Buildbot success in GNU pspp CI on debian-buster-amd64
Date: Tue, 5 Jan 2021 18:42:14 +0100


You can do a fresh install of openSUSE and run the included procedure to install the needed MingW environment and most of the needed dependencies.  mingw-configure and mingw-make will be installed in that process. 

The way it is used is calling 
  mingw32-configure    instead of    ./configure
  mingw32-make          instead of    make
the same for mingw64. 

Stay safe


Op ma 4 jan. 2021 om 12:18 schreef John Darrington <>:
All I can say is that I have performed cross build targeting mingw many, many,
many times in the last few weeks using the standard method of building, and I
have not encountered any serious issues.  Certainly nothing like the ones that
both you and Fritz have encountered using these wrappers.

So it seems reasonable to me, to suspect that these wrappers are relevant to
the problem.   I don't have these wrappers.  If someone can give me access to
them, then perhaps I can try to pinpoint the problem a little more precisely.

Until then,  I would urge anyone trying to cross build for mingw (or any other
platform) to use the standard method described in the INSTALL file, since that
is what we recommend and what has always worked, and is the GNU standard.


On Mon, Jan 04, 2021 at 11:27:56AM +0100, Harry Thijssen wrote:

     It seems a bit bold to me to state that the developers of Mingw on openSUSE
     release macros for calling Mingw with incorrect flags. Especially as this
     always worked.

     The current situation is that the source of PSPP and the routines of Mingw,
     as released on openSUSE, are incompatible.  I don't know if this can be
     solved and I am far from sure I can solve it. Especially as the configure
     for cross-compiling triggers a native build  looks to me as a problem.

     I would prefer the option as Fritz suggested or a pre-condition of a native
     current PSPP build which can be called for cross-compiling.

     I think these problems will disappear, if the pspp is built in the way
     > recommended in the
     > INSTALL file.  Just make sure the build and source directories are not the
     > same.

     If someone wants to work on this, I am happy to support him/here with my

     Stay safe

Description: Bourne shell script

reply via email to

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