Re: compiling octave fails on building flex

[Sergei Steshenko]

________________________________
 From: John Donoghue <address@hidden>
To: Marshall Floyd <address@hidden> 
Cc: address@hidden
Sent: Sunday, December 10, 2017 3:07 PM
Subject: Re: compiling octave fails on building flex
 


On 12/10/2017 01:17 AM, Marshall Floyd wrote:
> running :
>
> # make clean
> # ./configure --enable-devel-tools --enable-binary-packages 
> --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64
> # make
>
> failed on both my machines on building flex.
>
> I tried the other configure command you suggested for a linux build 
> and it failed on something different, but got past it on a second make 
> command: It was building for a rather long time and I won't see if it 
> fails or succeeds until Monday, but I'm interested in building it for 
> Windows as well which fails. Using the windows configure and doing 
> make -j4 -k and similar ended up eventually building everything except 
> flex. I note a warning at the beginning of the build:
>
> Warning - could not find native build version 4.3.0+ of octave - some 
> packages may fail, but continuing
>
> Looking at log/build-flex I find warnings and errors:
>
> /home/marshall/mxe-octave/tmp-build-flex/flex-2.6.4/src/misc.c: In 
> function ‘allocate_array’:
> /home/marshall/mxe-octave/tmp-build-flex/flex-2.6.4/src/misc.c:147:8: 
> warning: implicit declaration of function ‘reallocarray’; did you mean 
> ‘reallocate_array’? [-Wimplicit-function-declaration]
>   mem = reallocarray(NULL, (size_t) size, element_size);
>         ^~~~~~~~~~~~
>         reallocate_array
> /home/marshall/mxe-octave/tmp-build-flex/flex-2.6.4/src/misc.c:147:6: 
> warning: assignment makes pointer from integer without a cast 
> [-Wint-conversion]
>   mem = reallocarray(NULL, (size_t) size, element_size);
>       ^
> /home/marshall/mxe-octave/tmp-build-flex/flex-2.6.4/src/misc.c: In 
> function ‘reallocate_array’:
> /home/marshall/mxe-octave/tmp-build-flex/flex-2.6.4/src/misc.c:664:12: 
> warning: assignment makes pointer from integer without a cast 
> [-Wint-conversion]
>   new_array = reallocarray(array, (size_t) size, element_size);
>             ^
> and
>
> Makefile:1696: recipe for target 'stage1scan.c' failed
> make[4]: *** [stage1scan.c] Segmentation fault (core dumped)
>
>
> I'm running Ubuntu 17.10 on VirtualBox 5.2.2r119230, on Windows 10 Pro 
> 1709 16299.98 and Windows 10 Pro 1703 15063.726.
>
>
>
> On 12/8/2017 1:09 PM, JohnD wrote:
>>
>>> -----Original Message-----
>>> From: Marshall Floyd [mailto:address@hidden
>>> Sent: Friday, December 08, 2017 1:40 PM
>>> To: JohnD
>>> Cc: address@hidden
>>> Subject: Re: compiling octave fails on building flex
>>>
>>> ./configure --enable-devel-tools --enable-binary-packages --enable-
>>> octave=default --enable-qt5 --enable-64 --enable-windows-64
>>>
>>> [build]    build-flex
>>>
>>> Failed to build package build-flex!
>>> ------------------------------------------------------------
>>> Makefile:533: recipe for target 'all-recursive' failed
>>> make[3]: *** [all-recursive] Error 1
>>> make[3]: Leaving directory
>>> '/home/marshall/mxe-octave-f89c67818a6b/tmp-build-flex/flex-2.6.4.build' 
>>>
>>> /home/marshall/mxe-octave-f89c67818a6b/Makefile:852: recipe for target
>>> 'build-only-build-flex' failed
>>> make[2]: *** [build-only-build-flex] Error 2
>>> make[2]: Leaving directory '/home/marshall/mxe-octave-f89c67818a6b'
>>> real    0m13.483s
>>> user    0m11.572s
>>> sys    0m1.533s
>>> ------------------------------------------------------------
>>> [log] /home/marshall/mxe-octave-f89c67818a6b/log/build-flex
>>>
>>> Makefile:852: recipe for target
>>> '/home/marshall/mxe-octave-f89c67818a6b/installed-packages/build-flex'
>>> failed
>>> make[1]: ***
>>> [/home/marshall/mxe-octave-f89c67818a6b/installed-packages/build-flex]
>>> Error 1
>>> make[1]: Leaving directory '/home/marshall/mxe-octave-f89c67818a6b'
>>> Makefile:565: recipe for target 'all' failed
>>> make: *** [all] Error 2
>>>
>>> (I can add info from the logs specified if that will be useful, I've 
>>> looked at the
>>> errors before).
>>> -------------
>>>
>>> ./configure --enable-devel-tools --enable-binary-packages --enable-
>>> octave=default --disable-system-opengl --enable-native-build 
>>> --enable-lib64-
>>> directory --enable-pic-flag --disable-system-x11-libs 
>>> --disable-system-fontconfig
>>> --disable-system-gcc --enable-qt5 gnu-linux
>>>
>>>
>>>
>>> [download] build-gcc
>>> [build]    build-gcc
>>>
>>> Failed to build package build-gcc!
>>> ------------------------------------------------------------
>>> Makefile:931: recipe for target 'all' failed
>>> make[3]: *** [all] Error 2
>>> make[3]: Leaving directory
>>> '/home/marshall/mxe-octave-f89c67818a6b/tmp-build-gcc/gcc-7.2.0.build'
>>> /home/marshall/mxe-octave-f89c67818a6b/Makefile:852: recipe for target
>>> 'build-only-build-gcc' failed
>>> make[2]: *** [build-only-build-gcc] Error 2
>>> make[2]: Leaving directory '/home/marshall/mxe-octave-f89c67818a6b'
>>> real    15m14.593s
>>> user    13m55.151s
>>> sys    0m57.155s
>>> ------------------------------------------------------------
>>> [log] /home/marshall/mxe-octave-f89c67818a6b/log/build-gcc
>>>
>>> Makefile:852: recipe for target
>>> '/home/marshall/mxe-octave-f89c67818a6b/installed-packages/build-gcc'
>>> failed
>>> make[1]: ***
>>> [/home/marshall/mxe-octave-f89c67818a6b/installed-packages/build-gcc]
>>> Error 1
>>> make[1]: Leaving directory '/home/marshall/mxe-octave-f89c67818a6b'
>>> Makefile:565: recipe for target 'all' failed
>>> make: *** [all] Error 2
>>>
>>>
>>> It has never failed on gcc before, but it didn't try building flex 
>>> this time either.
>>>
>>> On 12/8/2017 5:52 AM, JohnD wrote:
>>>>> Message: 5
>>>>> Date: Thu, 7 Dec 2017 21:33:17 -0700
>>>>> From: Marshall Floyd <address@hidden>
>>>>> To: address@hidden
>>>>> Subject: compiling octave fails on building flex
>>>>> Message-ID: <address@hidden>
>>>>> Content-Type: text/plain; charset=utf-8; format=flowed
>>>>>
>>>>> I have tried building mxe-octave in Ubuntu (in Virtual Box) with the
>>>>> intent of eventually cross compiling for Windows, but I'd be happy if
>>>>> I could get a linux version. I want many of the bug fixes and
>>>>> enhancements in the development version. I have used instructions
>>>>> from http://wiki.octave.org/Windows_Installer,
>>>>> http://wiki.octave.org/MXE, and
>>>>> http://wiki.octave.org/Octave_for_Debian_systems. Compilation fails
>>>>> while building flex. How can I fix the problem with building flex, or
>>>>> compile octave using the installed version of flex? I've tried a few
>>>>> things to avoid building flex, but I'm not sure exactly how to do
>>>>> that, e.g. ./configure --without-flex or make PKG_EXCLUDE='flex', and
>>>>> other variations. I can't find it now, but I've seen a partial answer
>>>>> on the help email list to a similar problem of setting some make
>>>>> option or looking at one of the .mk files for guidance suggesting 
>>>>> that
>>> building make shouldn't have to be done. How can I do that?
>>>>>
>>>> What options do you pass to configure when building, and what error 
>>>> occurs?
>>>>
>>>> For creating a 64 bit windows installer I use the following configure
>>>> options:
>>>>
>>>> ./configure --enable-devel-tools --enable-binary-packages
>>>> --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64
>>>>
>>>> For creating a linux native, I use:
>>>>
>>>> ../configure --enable-devel-tools --enable-binary-packages
>>>> --enable-octave=default --disable-system-opengl --enable-native-build
>>>> --enable-lib64-directory --enable-pic-flag --disable-system-x11-libs
>>>> --disable-system-fontconfig --disable-system-gcc --enable-qt5
>>>> gnu-linux
>>>>
>>>>
>>>>
>> For each was it a clean build ? ie:
>> # make clean
>> # ./configure --enable-devel-tools --enable-binary-packages 
>> --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64
>> # make
>>
>> What version of Ubuntu ?
>>
>
That looks more like a running out of memory during compile.

Increase the memory used by the VM, and perhaps use a smaller job count



_______________________________________________


The "reallocatearray" <-> "reallocate_array" and assigning pointer to integer 
do not sound like running out of memory, but they do sound like plain bugs.

--Sergei.