Re: Building on MinGW using MXE-built dependencies [WAS: Re: mxe-installer try 2]

[Philip Nienhuis]

John W. Eaton wrote:
> On 06/10/2013 09:52 PM, John D wrote:
>
> > My assumption as well - and I deleted the file and redownloaded a
> > couple of
> > times just for the kick of it.
> > When you installed mingw, do you recall what packages/options you
> > installed?
> > Ming32 or 64?
>
> I've been working with mingw32, but I'm about to try the 64-bit compiler
> so I can try the --enable-64 option for Octave.
>
> > I believe I installed mingw32 with the C,C++ and fortran compiler, as
> > well
> > as MSYS basic, after selecting the option to download the latest updated
> > lists. (I ran the update and upgrade later to verify)
> >
> > I also installed the following packages afterwards to meet
> > dependencies/fix
> > issues with compiling:
> >
> > msys-wget
> > msys-unzip
> > msys-m4
> > msys-openssl
> > msys-patch
> > msys-perl
> > msys-regex
> > msys-flex
> > gettext (for bison to compile)
> > libiconv (for libiconv to compile)
>
> About the same, but msys-regex did not work for me because I couldn't
> figure out how to tell flex to find the header files and libraries since
> they are apparently installed in different location from other mingw
> headers and libraries and the compiler doesn't look there by default
> (weird, if you ask me).

Picking up from where I left 2.5 weeks ago. Or rather starting over. (in 
WinXP SP3 on 'bare metal", i.e. not in a virtual box.)

Here I didn't even get as far as you did. I installed mingw + above 
dependencies, updated/upgraded, cloned mxe-octave.
The mxe build breaks while building gcc.

The log (which is in <mxe-octave>/log, not in 
<mxe-octave>/log/<date-time> as when cross-compiling on Linux) says:

:
checking for mp_limb_t... no
checking size of mp_limb_t... 0
configure: error: Oops, mp_limb_t doesn't seem to work
make[4]: *** [configure-stage1-gmp] Error 1
make[4]: Leaving directory `/home/Philip/mxe-octave/tmp-gcc/gcc-4.7.2.build'
make[3]: *** [stage1-bubble] Error 2
make[3]: Leaving directory `/home/Philip/mxe-octave/tmp-gcc/gcc-4.7.2.build'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/Philip/mxe-octave/tmp-gcc/gcc-4.7.2.build'
make[1]: *** [build-only-gcc] Error 2
make[1]: Leaving directory `/home/Philip/mxe-octave'

Googling a bit turns up that this could be related to using absolute 
rather than relative paths for configure:

http://list-archives.org/2013/03/24/gmp-bugs-gmplib-org/posix-paths-in-%23include-directives-dont-work-with-mingw/f/5946233946

That's as far as I could grasp.
PATH doesn't look defective; in MinGW/MSYS:

$ echo $PATH
.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/Programs/TortoiseSVN/bin:/c/Programs/gs/gs9.02/bin:/c/Programs/QuickTime/QTSystem/:/c/Programs/Mercurial:.

Philip