|Subject:||Re: compiling octave fails on building flex|
|Date:||Sat, 16 Dec 2017 13:10:04 -0700|
|User-agent:||Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0|
On 12/15/2017 10:55 AM, Dmitri A. Sergatskov wrote:
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:
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:
= 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: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'.
make: *** No rule to make target '../opcodes/libopcodes.a', needed by 'gdb'.
make: 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.
|[Prev in Thread]||Current Thread||[Next in Thread]|