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

[John D]

-----Original Message-----
From: Philip Nienhuis [mailto:address@hidden 
Sent: Tuesday, June 11, 2013 5:18 PM
To: John W. Eaton
Cc: John D; address@hidden; 'Clemens Buchacher'
Subject: Re: Building on MinGW using MXE-built dependencies [WAS: Re:
mxe-installer try 2]

Philip Nienhuis wrote:
> John W. Eaton wrote:
>> On 06/11/2013 04:18 PM, Philip Nienhuis wrote:
>>
>>> On my list is finding out how to build using mxe-octave on Windows 7 
>>> 64-bit,
>>
>> I'm starting to try the same thing now, so maybe we can help each 
>> other and make it work.
>>
>> > as that runs on my fastest dev box (the build I referred to runs
>>> on an older Core Duo desktop).
>>> I consistently get configure messages that "gcc cannot build 
>>> executables", with the log mentioning that ld cannot find a.o., 
>>> -ladvapi32. Now, advapi32.dll and friends are in the 
>>> C:\Windows\system32 dir which *is* in the MinGW PATH as 
>>> /c/windows/system32. I've experimented with LDFLAGS and other tricks 
>>> to no avail :-) Google didn't turn up a solution yet.
>>> I think this is a very MinGW-specific issue.
>>
>> This is with the 64-bit mingw and tools? Why is it trying to link 
>> with advapi32? If that is normal, then where is that dependency coming
from?
>> Is it explicitly listed in some Makefiles?
>
> Turns out a "mingw-get mingw32-gcc" fixed it. That installed a load of 
> dependencies I apparently overlooked and skipped. mxe-octave just 
> succeeded building bison, now it is building cmake (on Win7 64-bit).
> Tomorrow morning I'll check the results.

The results came faster than I hoped:

address@hidden ~/mxe-octave
$ ./mk-dist --jobs 1
deleting previous dist directory...
building octave and dependencies...
[check requirements]
[build]    build-bison
[done]     build-bison
[download] build-cmake
[build]    build-cmake
[done]     build-cmake
[download] build-flex
[build]    build-flex

(## Why does mxe-octave say building "[build]  build-bison" rather than
"[build] bison" etc?)

Failed to build package build-flex!
------------------------------------------------------------
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37.build'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37.build'
make[1]: *** [build-only-build-flex] Error 2
make[1]: Leaving directory `/home/Philip/mxe-octave'


...and the log says:

:
gcc -DHAVE_CONFIG_H -I. 
-I/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37
-DLOCALEDIR=\"/home/Philip/mxe-octave/usr/share/locale\" 
-I/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/intl   -g -O2 -MT 
ccl.o -MD -MP -MF .deps/ccl.Tpo -c -o ccl.o
/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/ccl.c
In file included from
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/ccl.c:34
:0:
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1195:1: 
fout: unknown type name 'regex_t'
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1197:19: 
fout: unknown type name 'regex_t'
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1198:23: 
fout: unknown type name 'regmatch_t'
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1199:23: 
fout: unknown type name 'regmatch_t'
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1200:19: 
fout: unknown type name 'regmatch_t'
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1201:22: 
fout: unknown type name 'regmatch_t'
C:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-build-flex/flex-2.5.37/flexdef.
h:1202:22: 
fout: unknown type name 'regmatch_t'

I do have msys-regex installed.



----

I had the same issue when I tried - the native mingw mxe now doesn't try to
compile flex, instead I just install the msys-flex.