compiling octave fails on building flex

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

compiling octave fails on building flex

Marshall Floyd
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?


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

RE: compiling octave fails on building flex

JohnD
> Message: 5
> Date: Thu, 7 Dec 2017 21:33:17 -0700
> From: Marshall Floyd <[hidden email]>
> To: [hidden email]
> Subject: compiling octave fails on building flex
> Message-ID: <[hidden email]>
> 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




_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
./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 <[hidden email]>
>> To: [hidden email]
>> Subject: compiling octave fails on building flex
>> Message-ID: <[hidden email]>
>> 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
>
>
>


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

RE: compiling octave fails on building flex

JohnD


> -----Original Message-----
> From: Marshall Floyd [mailto:[hidden email]]
> Sent: Friday, December 08, 2017 1:40 PM
> To: JohnD
> Cc: [hidden email]
> 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 <[hidden email]>
> >> To: [hidden email]
> >> Subject: compiling octave fails on building flex
> >> Message-ID: <[hidden email]>
> >> 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 ?


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
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:[hidden email]]
>> Sent: Friday, December 08, 2017 1:40 PM
>> To: JohnD
>> Cc: [hidden email]
>> 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 <[hidden email]>
>>>> To: [hidden email]
>>>> Subject: compiling octave fails on building flex
>>>> Message-ID: <[hidden email]>
>>>> 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 ?
>


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

JohnD
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:[hidden email]]
>>> Sent: Friday, December 08, 2017 1:40 PM
>>> To: JohnD
>>> Cc: [hidden email]
>>> 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 <[hidden email]>
>>>>> To: [hidden email]
>>>>> Subject: compiling octave fails on building flex
>>>>> Message-ID: <[hidden email]>
>>>>> 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


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Sergei Steshenko





________________________________
 From: John Donoghue <[hidden email]>
To: Marshall Floyd <[hidden email]>
Cc: [hidden email]
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:[hidden email]]
>>> Sent: Friday, December 08, 2017 1:40 PM
>>> To: JohnD
>>> Cc: [hidden email]
>>> 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 <[hidden email]>
>>>>> To: [hidden email]
>>>>> Subject: compiling octave fails on building flex
>>>>> Message-ID: <[hidden email]>
>>>>> 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.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

JohnD
On 12/10/2017 12:40 PM, Sergei Steshenko wrote:

>
>
>
>
> ________________________________
>   From: John Donoghue <[hidden email]>
> To: Marshall Floyd <[hidden email]>
> Cc: [hidden email]
> 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:[hidden email]]
>>>> Sent: Friday, December 08, 2017 1:40 PM
>>>> To: JohnD
>>>> Cc: [hidden email]
>>>> 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 <[hidden email]>
>>>>>> To: [hidden email]
>>>>>> Subject: compiling octave fails on building flex
>>>>>> Message-ID: <[hidden email]>
>>>>>> 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.
>
That is only a warning.

The segfault sounds a lot worse to me.





_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
In reply to this post by Marshall Floyd
Adding more Ram, from8GB to 16GB, with nearly 30GB free hard drive space for the VM, and running only make ( one job ), still fails in the same place. 
The gnu linux configure build ended up failing on building mesa, which I thought was successfully built for the other configure with make -j4 -k. It claimed missing headers.

------ Original message------
From: John Donoghue
Date: Sun, Dec 10, 2017 3:50 PM
To: Sergei Steshenko;Marshall Floyd;
Subject:Re: compiling octave fails on building flex

On
12/10/2017 12:40 PM, Sergei Steshenko wrote:>>>>>
________________________________>   From: John Donoghue
> To: Marshall Floyd
> Cc:[hidden email]> 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>> <a href="tel:1709
16299.98">1709 16299.98 and Windows 10 Pro <a href="tel:1703
15063.726">1703 15063.726.>>>>>>>> On
12/8/2017 1:09 PM, JohnD wrote:>>>> -----Original
Message----->>>> From: Marshall Floyd [mailto[hidden email]]>>>>
Sent: Friday, December 08, 2017 1:40 PM>>>> To:
JohnD>>>> Cc:[hidden email]>>>> 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: recip
 e 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 >>>>>> To:[hidden email]>>>>>> Subject: compiling
octave fails on building flex>>>>>> Message-ID:
>>>>>>
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.>That is only a warning.The segfault sounds a lot worse to
me.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

mmuetzel
Google helps, for example here:
https://bugs.lede-project.org/index.php?do=details&task_id=1003

This is a known bug in flex that prevents it from being compiled with gcc
7.2. It will be fixed in version 2.6.5 of flex.

I am seeing the same error. I temporarily reverted to version 2.6.3 in my
local mxe-octave. (Change version and remove checksum in src/build-flex.mk).
That version still builds without the error.
The thread I linked also has a patch. But I haven't tried it.

Markus



--
Sent from: http://octave.1599824.n4.nabble.com/Octave-General-f1599825.html

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
In reply to this post by Marshall Floyd
I changed the required version for flex to 2.6.3 (and changed the checksum) in build-flex.mk, and then it compiled successfully. I found the same error mentioned here:  
https://github.com/westes/flex/issues/219. So supposedly it is a bug that doesn't exist in 2.6.3, but does in 2.6.4, and has been fixed for at least one kind of system. 

So now i supposedly have it built for Windows, what files do i have to move to Windows to run it? Or do I have to run 'make nsis-installer' now?


------ Original message------
From: John Donoghue
Date: Sun, Dec 10, 2017 3:50 PM
To: Sergei Steshenko;Marshall Floyd;
Subject:Re: compiling octave fails on building flex

On
12/10/2017 12:40 PM, Sergei Steshenko wrote:>>>>>
________________________________>   From: John Donoghue
> To: Marshall Floyd
> Cc:[hidden email]> 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>> <a href="tel:1709
16299.98">1709 16299.98 and Windows 10 Pro <a href="tel:1703
15063.726">1703 15063.726.>>>>>>>> On
12/8/2017 1:09 PM, JohnD wrote:>>>> -----Original
Message----->>>> From: Marshall Floyd [mailto[hidden email]]>>>>
Sent: Friday, December 08, 2017 1:40 PM>>>> To:
JohnD>>>> Cc:[hidden email]>>>> 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] Erro
 r 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 >>>>>> To:[hidden email]>>>>>> Subject: compiling
octave fails on building flex>>>>>> Message-ID:
>>>>>>
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.>That is only a warning.The segfault sounds a lot worse to
me.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
In reply to this post by Marshall Floyd
So now compiling with 'make' works I haven't found what to run. Copying the usr folder including octave executables to windows does not work (maybe i missed some files or setup?): running any of the octave*.exe do not work. There is no vbs entry point like there is now for octave 4.2.1. There is no run-active command to run it on linux. Running 'make nsis-installer' fails to build many of the forge packages, so I can't get an installer for it. 
Is there a way to exclude all forge packages from the installer? It's convenient, but I only use a few that I can try to install from within octave later. 

------ Original message------
From: John Donoghue
Date: Sun, Dec 10, 2017 3:50 PM
To: Sergei Steshenko;Marshall Floyd;
Subject:Re: compiling octave fails on building flex

On
12/10/2017 12:40 PM, Sergei Steshenko wrote:>>>>>
________________________________>   From: John Donoghue
> To: Marshall Floyd
> Cc:[hidden email]> 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>> <a href="tel:1709
16299.98">1709 16299.98 and Windows 10 Pro <a href="tel:1703
15063.726">1703 15063.726.>>>>>>>> On
12/8/2017 1:09 PM, JohnD wrote:>>>> -----Original
Message----->>>> From: Marshall Floyd [mailto[hidden email]]>>>>
Sent: Friday, December 08, 2017 1:40 PM>>>> To:
JohnD>>>> Cc:[hidden email]>>>> 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 >>>>>> To:[hidden email]>>>>>> Subject: compiling
octave fails on building flex>>>>>> Message-ID:
>>>>>>
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.>That is only a warning.The segfault sounds a lot worse to
me.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

RE: compiling octave fails on building flex

JohnD

>From: [hidden email] [mailto:[hidden email]]
>Sent: Tuesday, December 12, 2017 1:50 PM
>To: John Donoghue; Sergei Steshenko
>Cc: [hidden email]
>Subject: Re: compiling octave fails on building flex
>
> So now compiling with 'make' works I haven't found what to run. Copying the usr folder including octave executables to windows does not work (maybe i missed some files or setup?): running any of the octave*.exe do not work. There is no vbs entry point like there is now for octave 4.2.1. There is no run-active command to run it on linux. Running 'make nsis-installer' fails to build many of the forge packages, so I can't get an installer for it.
> Is there a way to exclude all forge packages from the installer? It's convenient, but I only use a few that I can try to install from within octave later.
>


Can you bottom post replies to make it easier to follow?

For the questions, you need to either create the installer, using 'make nsis-installer' and install that, or create a dist zip with 'make zip-dist' and unpack that in windows.

If you ran configure without the --enable-binary-packages, it would not install the binary packages and so not include them in the dist zip/installer.




_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
In reply to this post by Marshall Floyd

Can you bottom post replies to make it easier to follow?

For the questions, you need to either create the installer, using 'make nsis-installer' and install that, or create a dist zip with 'make zip-dist' and unpack that in windows.

If you ran configure without the --enable-binary-packages, it would not install the binary packages and so not include them in the dist zip/installer

------

Thanks! That worked, I was able to build and install it. That makes me pretty happy, and I like having the new features.

I noticed that only some of the bugs that have supposedly been fixed in the bug tracker are working or implemented, is the mxe somehow behind the non mxe octave? Or maybe they don't work in mxe? Can I apply arbitrary patches or are they somehow two separate code bases? I had looked up the source file for one bug, but couldn't find it in mxe-octave directory, but did find it in the octave repository. Maybe I'm getting the wrong branch? Or it was cleaned up when building? What is the relationship between different versions and branches, and how can I make sure I'm pulling from the one with the changes I'm interested in ( newest...)?

Should i post a bug report about the build failure on flex? That seems like the only real problem for building I encountered besides user error, and maybe the forge package compatibility/compiling that I skipped. I'm not sure whether that's an octave and/or flex problem.

P.S.: I'll make an effort for bottom posting, but apparently one of my email apps doesn't have the option to change it: I have to manually copy and paste prior emails to the top of the message to emulate bottom posting.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

JohnD


On Wed, Dec 13, 2017 at 11:54 AM, [hidden email] <[hidden email]> wrote:

Can you bottom post replies to make it easier to follow?

For the questions, you need to either create the installer, using 'make nsis-installer' and install that, or create a dist zip with 'make zip-dist' and unpack that in windows.

If you ran configure without the --enable-binary-packages, it would not install the binary packages and so not include them in the dist zip/installer

------

Thanks! That worked, I was able to build and install it. That makes me pretty happy, and I like having the new features.

I noticed that only some of the bugs that have supposedly been fixed in the bug tracker are working or implemented, is the mxe somehow behind the non mxe octave? Or maybe they don't work in mxe? Can I apply arbitrary patches or are they somehow two separate code bases? I had looked up the source file for one bug, but couldn't find it in mxe-octave directory, but did find it in the octave repository. Maybe I'm getting the wrong branch? Or it was cleaned up when building? What is the relationship between different versions and branches, and how can I make sure I'm pulling from the one with the changes I'm interested in ( newest...)?

Should i post a bug report about the build failure on flex? That seems like the only real problem for building I encountered besides user error, and maybe the forge package compatibility/compiling that I skipped. I'm not sure whether that's an octave and/or flex problem.

P.S.: I'll make an effort for bottom posting, but apparently one of my email apps doesn't have the option to change it: I have to manually copy and paste prior emails to the top of the message to emulate bottom posting.

If you run 'make hg-octave-dist', it will attempt to create a updated octave dev tarball that then will be used when running make nsis-installer. If you don't run that, it will use the tarball that it downloaded the first time it compiled the dev octave files.

When running the previous configure commands the --enable-octave=default told it to attempt to compile the dev version of octave (4.3) , without that option, it would have tried to compile the released version of octave (4.2)  (which may or may not compile with the current mxe files now)

In addition to pulling the latest sources, you can provide patches that will be applied by putting them in the src/ directory. For the default-octave target, it would be something like default-octave-X.patch, where X is a number to provide unique patch files.




_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
In reply to this post by Marshall Floyd
> If you run 'make hg-octave-dist', it will attempt to create a updated octave dev tarball that then will be used when running make nsis-installer. If you don't run that, it will use the tarball that it downloaded the first time it compiled the dev octave files.

I have been having troubles building with 'make hg-octave-dist' AND 'make nsis-installer'. I've already reported that I got the make nsis-installer working on one machine. On my other machine I got 'make hg-octave-dist' to work and was able to run it with './run-octave', and see that the last few features I had wanted worked on the linux version. However, I can't get either machine to run the alternate 'make' command to work. I continually get errors on one for building the native, and on the other can't get the windows installer. I should have saved the linux version when I had it working, to move it to the machine where the windows installer worked, but now it won't compile it again for some reason. I feel like somehow the order of building affected things because running things again have different errors, and I think that was the difference between the two machines, or maybe which dependencies I installed (the various lists of apt-get install ... lists). I'll try again from the start with a clean repo, but I expect I'll run against the same errors so maybe someone already knows the causes and how to fix some of these.

 

The following commands result in the following errors:

$make clean

$./configure --enable-devel-tools --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64 --disable-docs

$make hg-octave-dist -j6 <or without -jN>

...

running: libtoolize --install --copy

libtoolize:   error: 'build-aux/config.guess' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/config.sub' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/install-sh' is newer: use '--force' to overwrite

libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

...

GEN      doc/interpreter/interpft.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    interpimages at line 43 column 5

warning: division by zero

warning: called from

    legend at line 831 column 20

    interpimages at line 43 column 5

...

GEN      doc/interpreter/splinefit1.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    splineimages at line 52 column 5

warning: division by zero

warning: called from

    legend at line 840 column 20

    splineimages at line 52 column 5

...

warning: division by zero

warning: called from

    legend at line 831 column 20

    splineimages at line 162 column 5

warning: division by zero

warning: called from

    legend at line 916 column 11

    splineimages at line 162 column 5

  TEXI2DVI doc/interpreter/octave.dvi

/usr/bin/texi2dvi: etex exited with bad status, quitting.

Makefile:28017: recipe for target 'doc/interpreter/octave.dvi' failed

make[3]: *** [doc/interpreter/octave.dvi] Error 1

...

 

------------------------------

On the other machine, it doesn't choke on octave.dvi (and had worked all the way through once, but now gives the following:

 

...

  TEXI2DVI doc/interpreter/octave.dvi

  DVIPS    doc/interpreter/octave.ps

  GEN      doc/interpreter/voronoi.pdf

warning: division by zero

warning: called from

    legend at line 655 column 14

    geometryimages at line 54 column 5

...

warning: division by zero

warning: called from

    legend at line 916 column 11

    geometryimages at line 54 column 5

Error: /undefined in -nan

Operand stack:

   --nostringval--

Execution stack:

   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1999   1   3   %oparray_pop   1998   1   3   %oparray_pop   --nostringval--   1982   1   3   %oparray_pop   1868   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--

Dictionary stack:

   --dict:1215/1684(ro)(G)--   --dict:0/20(G)--   --dict:83/200(L)--   --dict:41/64(L)--

Current allocation mode is local

GPL Ghostscript 9.21: Unrecoverable error, exit code 1

  GEN      doc/interpreter/triplot.pdf

  GEN      doc/interpreter/griddata.pdf

...

<with more division by zero warnings and GPL Ghostscript errors and other files>

...

  MAKEINFO doc/interpreter/octave.html/.octave-html-stamp

doc/interpreter/poly.texi:790: warning: @image fi le `splinefit1' (for HTML) not found, using `splinefit1.jpg'

doc/interpreter/poly.texi:834: warning: @image file `splinefit2' (for HTML) not found, using `splinefit2.jpg'

doc/interpreter/poly.texi:871: warning: @image file `splinefit3' (for HTML) not found, using `splinefit3.jpg'

doc/interpreter/poly.texi:910: warning: @image file `splinefit4' (for HTML) not found, using `splinefit4.jpg'

doc/interpreter/poly.texi:954: warning: @image file `splinefit6' (for HTML) not found, using `splinefit6.jpg'

doc/interpreter/interp.texi:168: warning: @image file `interpderiv1' (for HTML) not found, using `interpderiv1.jpg'

doc/interpreter/interp.texi:174: warning: @image file `interpderiv2' (for HTML) not found, using `interpderiv2.jpg'

doc/interpreter/interp.texi:233: warning: @image file `interpft' (for HTML) not found, using `interpft.jpg'

doc/interpreter/geometry.texi:649: warning: @image file `voronoi' (for HTML) not found, using `voronoi.jpg'

  GEN      doc/interpreter/octave.html/voronoi.png

cp: cannot stat 'doc/interpreter/voronoi.png': No such file or directory

Makefile:28045: recipe for target 'doc/interpreter/octave.html/voronoi.png' failed

make[3]: *** [doc/interpreter/octave.html/voronoi.png] Error 1

...

 

-----------------

The division by zero- warnings didn't use to show up in my first failed attempts at make hg-octave-dist, so I'm not sure why they started showing up. The failure on octave.dvi is the critical failure that has always showed up on the one machine however. I note that there's an octave bug, bug #48172, that mentions the same error, but was supposedly fixed for an older version of Ubuntu. I try some of the same things there and they haven't worked (e.g. configuring with "--disable-docs", which doesn't seem to do anything, or running make again, or replacing the symlink to texinfo.tex). Looking at a log when  make V=1 is done, gives a different set of errors than in that bug report (I wish I had copied that before trying other builds, because now I don't have that log anymore).


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Dmitri A. Sergatskov


On Fri, Dec 15, 2017 at 10:26 AM, [hidden email] <[hidden email]> wrote:
> If you run 'make hg-octave-dist', it will attempt to create a updated octave dev tarball that then will be used when running make nsis-installer. If you don't run that, it will use the tarball that it downloaded the first time it compiled the dev octave files.

I have been having troubles building with 'make hg-octave-dist' AND 'make nsis-installer'. I've already reported that I got the make nsis-installer working on one machine. On my other machine I got 'make hg-octave-dist' to work and was able to run it with './run-octave', and see that the last few features I had wanted worked on the linux version. However, I can't get either machine to run the alternate 'make' command to work. I continually get errors on one for building the native, and on the other can't get the windows installer. I should have saved the linux version when I had it working, to move it to the machine where the windows installer worked, but now it won't compile it again for some reason. I feel like somehow the order of building affected things because running things again have different errors, and I think that was the difference between the two machines, or maybe which dependencies I installed (the various lists of apt-get install ... lists). I'll try again from the start with a clean repo, but I expect I'll run against the same errors so maybe someone already knows the causes and how to fix some of these.

 

The following commands result in the following errors:

$make clean

$./configure --enable-devel-tools --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64 --disable-docs

$make hg-octave-dist -j6 <or without -jN>

...

running: libtoolize --install --copy

libtoolize:   error: 'build-aux/config.guess' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/config.sub' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/install-sh' is newer: use '--force' to overwrite

libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

...

GEN      doc/interpreter/interpft.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    interpimages at line 43 column 5

warning: division by zero

warning: called from

    legend at line 831 column 20

    interpimages at line 43 column 5

...

GEN      doc/interpreter/splinefit1.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    splineimages at line 52 column 5

warning: division by zero

warning: called from

    legend at line 840 column 20

    splineimages at line 52 column 5

...

warning: division by zero

warning: called from

    legend at line 831 column 20

    splineimages at line 162 column 5

warning: division by zero

warning: called from

    legend at line 916 column 11

    splineimages at line 162 column 5

  TEXI2DVI doc/interpreter/octave.dvi

/usr/bin/texi2dvi: etex exited with bad status, quitting.

Makefile:28017: recipe for target 'doc/interpreter/octave.dvi' failed

make[3]: *** [doc/interpreter/octave.dvi] Error 1

...

 

------------------------------

On the other machine, it doesn't choke on octave.dvi (and had worked all the way through once, but now gives the following:

 

...

  TEXI2DVI doc/interpreter/octave.dvi

  DVIPS    doc/interpreter/octave.ps

  GEN      doc/interpreter/voronoi.pdf

warning: division by zero

warning: called from

    legend at line 655 column 14

    geometryimages at line 54 column 5

...

warning: division by zero

warning: called from

    legend at line 916 column 11

    geometryimages at line 54 column 5

Error: /undefined in -nan

Operand stack:

   --nostringval--

Execution stack:

   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1999   1   3   %oparray_pop   1998   1   3   %oparray_pop   --nostringval--   1982   1   3   %oparray_pop   1868   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--

Dictionary stack:

   --dict:1215/1684(ro)(G)--   --dict:0/20(G)--   --dict:83/200(L)--   --dict:41/64(L)--

Current allocation mode is local

GPL Ghostscript 9.21: Unrecoverable error, exit code 1

  GEN      doc/interpreter/triplot.pdf

  GEN      doc/interpreter/griddata.pdf

...

<with more division by zero warnings and GPL Ghostscript errors and other files>

...

  MAKEINFO doc/interpreter/octave.html/.octave-html-stamp

doc/interpreter/poly.texi:790: warning: @image file `splinefit1' (for HTML) not found, using `splinefit1.jpg'

doc/interpreter/poly.texi:834: warning: @image file `splinefit2' (for HTML) not found, using `splinefit2.jpg'

doc/interpreter/poly.texi:871: warning: @image file `splinefit3' (for HTML) not found, using `splinefit3.jpg'

doc/interpreter/poly.texi:910: warning: @image file `splinefit4' (for HTML) not found, using `splinefit4.jpg'

doc/interpreter/poly.texi:954: warning: @image file `splinefit6' (for HTML) not found, using `splinefit6.jpg'

doc/interpreter/interp.texi:168: warning: @image file `interpderiv1' (for HTML) not found, using `interpderiv1.jpg'

doc/interpreter/interp.texi:174: warning: @image file `interpderiv2' (for HTML) not found, using `interpderiv2.jpg'

doc/interpreter/interp.texi:233: warning: @image file `interpft' (for HTML) not found, using `interpft.jpg'

doc/interpreter/geometry.texi:649: warning: @image file `voronoi' (for HTML) not found, using `voronoi.jpg'

  GEN      doc/interpreter/octave.html/voronoi.png

cp: cannot stat 'doc/interpreter/voronoi.png': No such file or directory

Makefile:28045: recipe for target 'doc/interpreter/octave.html/voronoi.png' failed

make[3]: *** [doc/interpreter/octave.html/voronoi.png] Error 1

...

 

-----------------

The division by zero- warnings didn't use to show up in my first failed attempts at make hg-octave-dist, so I'm not sure why they started showing up. The failure on octave.dvi is the critical failure that has always showed up on the one machine however. I note that there's an octave bug, bug #48172, that mentions the same error, but was supposedly fixed for an older version of Ubuntu. I try some of the same things there and they haven't worked (e.g. configuring with "--disable-docs", which doesn't seem to do anything, or running make again, or replacing the symlink to texinfo.tex). Looking at a log when  make V=1 is done, gives a different set of errors than in that bug report (I wish I had copied that before trying other builds, because now I don't have that log anymore).




​This looks like OpenGL/gl2ps issue to me -- the figures are not generated.

Try
​LIBGL_ALWAYS_SOFTWARE=1 make

may be also try to preload mesa libs (though I think the error is usually different)

LD_PRELOAD=/usr/lib64/libGLX_mesa.so.0 LIBGL_ALWAYS_SOFTWARE=1 make

​(path and name of the mesa lib may be different on your system)

​Dmitri.
--


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
On 12/15/2017 10:55 AM, Dmitri A. Sergatskov wrote:


On Fri, Dec 15, 2017 at 10:26 AM, [hidden email] <[hidden email]> wrote:
> If you run 'make hg-octave-dist', it will attempt to create a updated octave dev tarball that then will be used when running make nsis-installer. If you don't run that, it will use the tarball that it downloaded the first time it compiled the dev octave files.

I have been having troubles building with 'make hg-octave-dist' AND 'make nsis-installer'. I've already reported that I got the make nsis-installer working on one machine. On my other machine I got 'make hg-octave-dist' to work and was able to run it with './run-octave', and see that the last few features I had wanted worked on the linux version. However, I can't get either machine to run the alternate 'make' command to work. I continually get errors on one for building the native, and on the other can't get the windows installer. I should have saved the linux version when I had it working, to move it to the machine where the windows installer worked, but now it won't compile it again for some reason. I feel like somehow the order of building affected things because running things again have different errors, and I think that was the difference between the two machines, or maybe which dependencies I installed (the various lists of apt-get install ... lists). I'll try again from the start with a clean repo, but I expect I'll run against the same errors so maybe someone already knows the causes and how to fix some of these.

 

The following commands result in the following errors:

$make clean

$./configure --enable-devel-tools --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64 --disable-docs

$make hg-octave-dist -j6 <or without -jN>

...

running: libtoolize --install --copy

libtoolize:   error: 'build-aux/config.guess' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/config.sub' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/install-sh' is newer: use '--force' to overwrite

libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

...

GEN      doc/interpreter/interpft.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    interpimages at line 43 column 5

warning: division by zero

warning: called from

    legend at line 831 column 20

    interpimages at line 43 column 5

...

GEN      doc/interpreter/splinefit1.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    splineimages at line 52 column 5

warning: division by zero

warning: called from

    legend at line 840 column 20

    splineimages at line 52 column 5

...

warning: division by zero

warning: called from

    legend at line 831 column 20

    splineimages at line 162 column 5

warning: division by zero

warning: called from

    legend at line 916 column 11

    splineimages at line 162 column 5

  TEXI2DVI doc/interpreter/octave.dvi

/usr/bin/texi2dvi: etex exited with bad status, quitting.

Makefile:28017: recipe for target 'doc/interpreter/octave.dvi' failed

make[3]: *** [doc/interpreter/octave.dvi] Error 1

...

 

------------------------------

On the other machine, it doesn't choke on octave.dvi (and had worked all the way through once, but now gives the following:

 

...

  TEXI2DVI doc/interpreter/octave.dvi

  DVIPS    doc/interpreter/octave.ps

  GEN      doc/interpreter/voronoi.pdf

warning: division by zero

warning: called from

    legend at line 655 column 14

    geometryimages at line 54 column 5

...

warning: division by zero

warning: called from

    legend at line 916 column 11

    geometryimages at line 54 column 5

Error: /undefined in -nan

Operand stack:

   --nostringval--

Execution stack:

   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1999   1   3   %oparray_pop   1998   1   3   %oparray_pop   --nostringval--   1982   1   3   %oparray_pop   1868   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--

Dictionary stack:

   --dict:1215/1684(ro)(G)--   --dict:0/20(G)--   --dict:83/200(L)--   --dict:41/64(L)--

Current allocation mode is local

GPL Ghostscript 9.21: Unrecoverable error, exit code 1

  GEN      doc/interpreter/triplot.pdf

  GEN      doc/interpreter/griddata.pdf

...

<with more division by zero warnings and GPL Ghostscript errors and other files>

...

  MAKEINFO doc/interpreter/octave.html/.octave-html-stamp

doc/interpreter/poly.texi:790: warning: @image file `splinefit1' (for HTML) not found, using `splinefit1.jpg'

doc/interpreter/poly.texi:834: warning: @image file `splinefit2' (for HTML) not found, using `splinefit2.jpg'

doc/interpreter/poly.texi:871: warning: @image file `splinefit3' (for HTML) not found, using `splinefit3.jpg'

doc/interpreter/poly.texi:910: warning: @image file `splinefit4' (for HTML) not found, using `splinefit4.jpg'

doc/interpreter/poly.texi:954: warning: @image file `splinefit6' (for HTML) not found, using `splinefit6.jpg'

doc/interpreter/interp.texi:168: warning: @image file `interpderiv1' (for HTML) not found, using `interpderiv1.jpg'

doc/interpreter/interp.texi:174: warning: @image file `interpderiv2' (for HTML) not found, using `interpderiv2.jpg'

doc/interpreter/interp.texi:233: warning: @image file `interpft' (for HTML) not found, using `interpft.jpg'

doc/interpreter/geometry.texi:649: warning: @image file `voronoi' (for HTML) not found, using `voronoi.jpg'

  GEN      doc/interpreter/octave.html/voronoi.png

cp: cannot stat 'doc/interpreter/voronoi.png': No such file or directory

Makefile:28045: recipe for target 'doc/interpreter/octave.html/voronoi.png' failed

make[3]: *** [doc/interpreter/octave.html/voronoi.png] Error 1

...

 

-----------------

The division by zero- warnings didn't use to show up in my first failed attempts at make hg-octave-dist, so I'm not sure why they started showing up. The failure on octave.dvi is the critical failure that has always showed up on the one machine however. I note that there's an octave bug, bug #48172, that mentions the same error, but was supposedly fixed for an older version of Ubuntu. I try some of the same things there and they haven't worked (e.g. configuring with "--disable-docs", which doesn't seem to do anything, or running make again, or replacing the symlink to texinfo.tex). Looking at a log when  make V=1 is done, gives a different set of errors than in that bug report (I wish I had copied that before trying other builds, because now I don't have that log anymore).




​This looks like OpenGL/gl2ps issue to me -- the figures are not generated.

Try
​LIBGL_ALWAYS_SOFTWARE=1 make

may be also try to preload mesa libs (though I think the error is usually different)

LD_PRELOAD=/usr/lib64/libGLX_mesa.so.0 LIBGL_ALWAYS_SOFTWARE=1 make

​(path and name of the mesa lib may be different on your system)

​Dmitri.
--

​LIBGL_ALWAYS_SOFTWARE=1 make, didn't seem to make a difference. I've started to keep track of exactly what order of commands I do while building to avoid repeating or get intuition of what changes between and that's help narrow things down. After a while and looking at errors and getting other errors resolved, the only remaining errors appear to be those relating to errors in generating the images needed for the docs.

On my other machine though, I got the linux version compiled again, and ./octave-hg-repo/.build/run-octave opens octave and has the new bug fixes I was looking for. make nsis-installer -j4 -k after multiple runs fails with the following three errors:

[build]    nsis
[build]    of-general
[build]    gdb

Failed to build package nsis!
------------------------------------------------------------
scons: *** Path for option APPEND_LIBPATH does not exist: /home/marshall/mxe-octave/usr/lib32
File "/home/marshall/mxe-octave/tmp-nsis/nsis-2.50-src/SConstruct", line 177, in <module>
/home/marshall/mxe-octave/Makefile:851: recipe for target 'build-only-nsis' failed
make[1]: *** [build-only-nsis] Error 2
make[1]: Leaving directory '/home/marshall/mxe-octave'
real    0m2.981s
user    0m1.862s
sys    0m0.458s
------------------------------------------------------------
[log]      /home/marshall/mxe-octave/log/nsis

Makefile:851: recipe for target '/home/marshall/mxe-octave/installed-packages/nsis' failed
make: *** [/home/marshall/mxe-octave/installed-packages/nsis] Error 1

Failed to build package of-general!
------------------------------------------------------------
  File "/home/marshall/mxe-octave/tools/pkg-install.py", line 237, in configure_make
    raise Exception, "make failed during build - stopping install"
Exception: make failed during build - stopping install
/home/marshall/mxe-octave/Makefile:851: recipe for target 'build-only-of-general' failed
make[1]: *** [build-only-of-general] Error 1
make[1]: Leaving directory '/home/marshall/mxe-octave'
real    0m12.185s
user    0m10.556s
sys    0m0.802s
------------------------------------------------------------
[log]      /home/marshall/mxe-octave/log/of-general

Makefile:851: recipe for target '/home/marshall/mxe-octave/installed-packages/of-general' failed
make: *** [/home/marshall/mxe-octave/installed-packages/of-general] Error 1

Failed to build package gdb!
------------------------------------------------------------
Makefile:849: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/home/marshall/mxe-octave/tmp-gdb/gdb-8.0.1'
/home/marshall/mxe-octave/Makefile:851: recipe for target 'build-only-gdb' failed
make[1]: *** [build-only-gdb] Error 2
make[1]: Leaving directory '/home/marshall/mxe-octave'
real    8m22.099s
user    7m20.136s
sys    0m47.410s
------------------------------------------------------------
[log]      /home/marshall/mxe-octave/log/gdb

Makefile:851: recipe for target '/home/marshall/mxe-octave/installed-packages/gdb' failed
make: *** [/home/marshall/mxe-octave/installed-packages/gdb] Error 1
make: Target 'nsis-installer' not remade because of errors.



nsis fails I think because it tries to access the non-existent directory mxe-octave/usr/lib32

of-general fails according to the log because of , though there are other warnings of deprecated calls:

packfields.cc:54:39: error: conversion from ‘octave::symbol_table::scope*’ to non-scalar type ‘octave::symbol_table::scope’ requested
        = interp.require_current_scope ("packfields");
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
...
unpackfields.cc:60:39: error: conversion from ‘octave::symbol_table::scope*’ to non-scalar type ‘octave::symbol_table::scope’ requested
        = interp.require_current_scope ("unpackfields");
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
(I'm surprised though that this time through all the other of-* packages built, they almost all failed miserably before on one of the machines)
gdb failed becaue of :
...
make[4]: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'.
make[4]: *** No rule to make target '../opcodes/libopcodes.a', needed by 'gdb'.
make[4]: Target 'all' not remade because of errors.

Any suggestions? The other machine doesn't fail on these (gdb and nsis, I haven't built package binaries on the other one, and only accidentally let it slip on this one), so I must have setup dependencies inconsistently? I'll move the successful octave-4.3.0+.tar.gz to the other machine which successfully does make nsis-installer and see if I can combine them. But I'd still like to solve this so I can reliably build all the way through on both machines individually.


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

JohnD
On 12/16/2017 03:10 PM, Marshall Floyd wrote:
On 12/15/2017 10:55 AM, Dmitri A. Sergatskov wrote:


On Fri, Dec 15, 2017 at 10:26 AM, [hidden email] <[hidden email]> wrote:
> If you run 'make hg-octave-dist', it will attempt to create a updated octave dev tarball that then will be used when running make nsis-installer. If you don't run that, it will use the tarball that it downloaded the first time it compiled the dev octave files.

I have been having troubles building with 'make hg-octave-dist' AND 'make nsis-installer'. I've already reported that I got the make nsis-installer working on one machine. On my other machine I got 'make hg-octave-dist' to work and was able to run it with './run-octave', and see that the last few features I had wanted worked on the linux version. However, I can't get either machine to run the alternate 'make' command to work. I continually get errors on one for building the native, and on the other can't get the windows installer. I should have saved the linux version when I had it working, to move it to the machine where the windows installer worked, but now it won't compile it again for some reason. I feel like somehow the order of building affected things because running things again have different errors, and I think that was the difference between the two machines, or maybe which dependencies I installed (the various lists of apt-get install ... lists). I'll try again from the start with a clean repo, but I expect I'll run against the same errors so maybe someone already knows the causes and how to fix some of these.

 

The following commands result in the following errors:

$make clean

$./configure --enable-devel-tools --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64 --disable-docs

$make hg-octave-dist -j6 <or without -jN>

...

running: libtoolize --install --copy

libtoolize:   error: 'build-aux/config.guess' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/config.sub' is newer: use '--force' to overwrite

libtoolize:   error: 'build-aux/install-sh' is newer: use '--force' to overwrite

libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

...

GEN      doc/interpreter/interpft.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    interpimages at line 43 column 5

warning: division by zero

warning: called from

    legend at line 831 column 20

    interpimages at line 43 column 5

...

GEN      doc/interpreter/splinefit1.eps

warning: division by zero

warning: called from

    legend at line 655 column 14

    splineimages at line 52 column 5

warning: division by zero

warning: called from

    legend at line 840 column 20

    splineimages at line 52 column 5

...

warning: division by zero

warning: called from

    legend at line 831 column 20

    splineimages at line 162 column 5

warning: division by zero

warning: called from

    legend at line 916 column 11

    splineimages at line 162 column 5

  TEXI2DVI doc/interpreter/octave.dvi

/usr/bin/texi2dvi: etex exited with bad status, quitting.

Makefile:28017: recipe for target 'doc/interpreter/octave.dvi' failed

make[3]: *** [doc/interpreter/octave.dvi] Error 1

...

 

------------------------------

On the other machine, it doesn't choke on octave.dvi (and had worked all the way through once, but now gives the following:

 

...

  TEXI2DVI doc/interpreter/octave.dvi

  DVIPS    doc/interpreter/octave.ps

  GEN      doc/interpreter/voronoi.pdf

warning: division by zero

warning: called from

    legend at line 655 column 14

    geometryimages at line 54 column 5

...

warning: division by zero

warning: called from

    legend at line 916 column 11

    geometryimages at line 54 column 5

Error: /undefined in -nan

Operand stack:

   --nostringval--

Execution stack:

   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1999   1   3   %oparray_pop   1998   1   3   %oparray_pop   --nostringval--   1982   1   3   %oparray_pop   1868   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--

Dictionary stack:

   --dict:1215/1684(ro)(G)--   --dict:0/20(G)--   --dict:83/200(L)--   --dict:41/64(L)--

Current allocation mode is local

GPL Ghostscript 9.21: Unrecoverable error, exit code 1

  GEN      doc/interpreter/triplot.pdf

  GEN      doc/interpreter/griddata.pdf

...

<with more division by zero warnings and GPL Ghostscript errors and other files>

...

  MAKEINFO doc/interpreter/octave.html/.octave-html-stamp

doc/interpreter/poly.texi:790: warning: @image file `splinefit1' (for HTML) not found, using `splinefit1.jpg'

doc/interpreter/poly.texi:834: warning: @image file `splinefit2' (for HTML) not found, using `splinefit2.jpg'

doc/interpreter/poly.texi:871: warning: @image file `splinefit3' (for HTML) not found, using `splinefit3.jpg'

doc/interpreter/poly.texi:910: warning: @image file `splinefit4' (for HTML) not found, using `splinefit4.jpg'

doc/interpreter/poly.texi:954: warning: @image file `splinefit6' (for HTML) not found, using `splinefit6.jpg'

doc/interpreter/interp.texi:168: warning: @image file `interpderiv1' (for HTML) not found, using `interpderiv1.jpg'

doc/interpreter/interp.texi:174: warning: @image file `interpderiv2' (for HTML) not found, using `interpderiv2.jpg'

doc/interpreter/interp.texi:233: warning: @image file `interpft' (for HTML) not found, using `interpft.jpg'

doc/interpreter/geometry.texi:649: warning: @image file `voronoi' (for HTML) not found, using `voronoi.jpg'

  GEN      doc/interpreter/octave.html/voronoi.png

cp: cannot stat 'doc/interpreter/voronoi.png': No such file or directory

Makefile:28045: recipe for target 'doc/interpreter/octave.html/voronoi.png' failed

make[3]: *** [doc/interpreter/octave.html/voronoi.png] Error 1

...

 

-----------------

The division by zero- warnings didn't use to show up in my first failed attempts at make hg-octave-dist, so I'm not sure why they started showing up. The failure on octave.dvi is the critical failure that has always showed up on the one machine however. I note that there's an octave bug, bug #48172, that mentions the same error, but was supposedly fixed for an older version of Ubuntu. I try some of the same things there and they haven't worked (e.g. configuring with "--disable-docs", which doesn't seem to do anything, or running make again, or replacing the symlink to texinfo.tex). Looking at a log when  make V=1 is done, gives a different set of errors than in that bug report (I wish I had copied that before trying other builds, because now I don't have that log anymore).




​This looks like OpenGL/gl2ps issue to me -- the figures are not generated.

Try
​LIBGL_ALWAYS_SOFTWARE=1 make

may be also try to preload mesa libs (though I think the error is usually different)

LD_PRELOAD=/usr/lib64/libGLX_mesa.so.0 LIBGL_ALWAYS_SOFTWARE=1 make

​(path and name of the mesa lib may be different on your system)

​Dmitri.
--

​LIBGL_ALWAYS_SOFTWARE=1 make, didn't seem to make a difference. I've started to keep track of exactly what order of commands I do while building to avoid repeating or get intuition of what changes between and that's help narrow things down. After a while and looking at errors and getting other errors resolved, the only remaining errors appear to be those relating to errors in generating the images needed for the docs.

On my other machine though, I got the linux version compiled again, and ./octave-hg-repo/.build/run-octave opens octave and has the new bug fixes I was looking for. make nsis-installer -j4 -k after multiple runs fails with the following three errors:

[build]    nsis
[build]    of-general
[build]    gdb

Failed to build package nsis!
------------------------------------------------------------
scons: *** Path for option APPEND_LIBPATH does not exist: /home/marshall/mxe-octave/usr/lib32
File "/home/marshall/mxe-octave/tmp-nsis/nsis-2.50-src/SConstruct", line 177, in <module>
/home/marshall/mxe-octave/Makefile:851: recipe for target 'build-only-nsis' failed
make[1]: *** [build-only-nsis] Error 2
make[1]: Leaving directory '/home/marshall/mxe-octave'
real    0m2.981s
user    0m1.862s
sys    0m0.458s
------------------------------------------------------------
[log]      /home/marshall/mxe-octave/log/nsis

Makefile:851: recipe for target '/home/marshall/mxe-octave/installed-packages/nsis' failed
make: *** [/home/marshall/mxe-octave/installed-packages/nsis] Error 1

Failed to build package of-general!
------------------------------------------------------------
  File "/home/marshall/mxe-octave/tools/pkg-install.py", line 237, in configure_make
    raise Exception, "make failed during build - stopping install"
Exception: make failed during build - stopping install
/home/marshall/mxe-octave/Makefile:851: recipe for target 'build-only-of-general' failed
make[1]: *** [build-only-of-general] Error 1
make[1]: Leaving directory '/home/marshall/mxe-octave'
real    0m12.185s
user    0m10.556s
sys    0m0.802s
------------------------------------------------------------
[log]      /home/marshall/mxe-octave/log/of-general

Makefile:851: recipe for target '/home/marshall/mxe-octave/installed-packages/of-general' failed
make: *** [/home/marshall/mxe-octave/installed-packages/of-general] Error 1

Failed to build package gdb!
------------------------------------------------------------
Makefile:849: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/home/marshall/mxe-octave/tmp-gdb/gdb-8.0.1'
/home/marshall/mxe-octave/Makefile:851: recipe for target 'build-only-gdb' failed
make[1]: *** [build-only-gdb] Error 2
make[1]: Leaving directory '/home/marshall/mxe-octave'
real    8m22.099s
user    7m20.136s
sys    0m47.410s
------------------------------------------------------------
[log]      /home/marshall/mxe-octave/log/gdb

Makefile:851: recipe for target '/home/marshall/mxe-octave/installed-packages/gdb' failed
make: *** [/home/marshall/mxe-octave/installed-packages/gdb] Error 1
make: Target 'nsis-installer' not remade because of errors.



nsis fails I think because it tries to access the non-existent directory mxe-octave/usr/lib32

of-general fails according to the log because of , though there are other warnings of deprecated calls:

packfields.cc:54:39: error: conversion from ‘octave::symbol_table::scope*’ to non-scalar type ‘octave::symbol_table::scope’ requested
        = interp.require_current_scope ("packfields");
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
...
unpackfields.cc:60:39: error: conversion from ‘octave::symbol_table::scope*’ to non-scalar type ‘octave::symbol_table::scope’ requested
        = interp.require_current_scope ("unpackfields");
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
(I'm surprised though that this time through all the other of-* packages built, they almost all failed miserably before on one of the machines)
gdb failed becaue of :
...
make[4]: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'.
make[4]: *** No rule to make target '../opcodes/libopcodes.a', needed by 'gdb'.
make[4]: Target 'all' not remade because of errors.

Any suggestions? The other machine doesn't fail on these (gdb and nsis, I haven't built package binaries on the other one, and only accidentally let it slip on this one), so I must have setup dependencies inconsistently? I'll move the successful octave-4.3.0+.tar.gz to the other machine which successfully does make nsis-installer and see if I can combine them. But I'd still like to solve this so I can reliably build all the way through on both machines individually.

Do you have the latest mxe-octave? JWE pushed a patch for of-general a few days ago that may have fixed the issues for that package.

For gdb, there was probally a previous error in the build that prevented bfd/libbfd.a etc from being built that may be actual cause of the error

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: compiling octave fails on building flex

Marshall Floyd
In reply to this post by Marshall Floyd
Any suggestions? The other machine doesn't fail on these (gdb and nsis, I haven't built package binaries on the other one, and only accidentally let it slip on this one), so I must have setup dependencies inconsistently? I'll move the successful octave-4.3.0+.tar.gz to the other machine which successfully does make nsis-installer and see if I can combine them. But I'd still like to solve this so I can reliably build all the way through on both machines individually.

Do you have the latest mxe-octave? JWE pushed a patch for of-general a few days ago that may have fixed the issues for that package.

For gdb, there was probally a previous error in the build that prevented bfd/libbfd.a etc from being built that may be actual cause of the error

----

I thought I did have that patch applied. When I tried to look to see what the failing lines were, I thought they came from the patch, but I wasn't sure. My next builds will update the repo first to make sure. 

The failure with gdb and nsis was most likely what you said, because after make clean, they eventually built fine with make nsis-installer and ./configure --enable-devel-tools --enable-binary-packages --enable-octave=default --enable-qt5 --enable-64 --enable-windows-64.  Oddly this time it got caught on of-image and of-gsl as well as of-general. Image and gsl claimed to fail on the same error that they couldn't find "octave". In any case I skipped building each by commenting out the build lines in the three associated build files. All other of- packages built fine, and the installer worked, but it didn't have the bug fixes that i just verified on the same machine in the linux vm build. Maybe I wasn't careful enough to make sure it built with the newly built linux version when it made the Windows installer? If my record keeping is accurate, it shows I built with make and not make  hg-octave-dist like I thought, so likely the octave tar wasn't moved to the pkg directory automatically. The successful prior build of the linux build might have still been hanging around when I tested it after the successful make command making me assume it was going to be used in the nsis- installer build. I'll try to repeat the successful build process on the other machine today and double check I use the right octave tar for it.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
12