FS#40098 - [octave] cannot compile modules

Attached to Project: Arch Linux
Opened by Michel (xantares) - Saturday, 26 April 2014, 11:37 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 12 June 2016, 10:04 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

I've got the bug as reported to:
http://savannah.gnu.org/bugs/?41027
when compiling a module, it is due to angled brackets, and recently I proposed a patch to fix it (comment #11)
Unfortunately it hasn't been reviewed nor pushed yet.

Here the compilation error for record:
[100%] Building CXX object octave/CMakeFiles/example_oct.dir/__/exampleOCTAVE_wrap.cxx.o
In file included from /home/xantares/projects/myquakeconfig/trunk/swig_test/build/octave/../exampleOCTAVE_wrap.cxx:154:0:
/usr/include/octave-3.8.1/octave/oct.h:31:20: fatal error: config.h: No such file or directory
#include <config.h>
^
compilation terminated.
octave/CMakeFiles/example_oct.dir/build.make:63: recipe for target 'octave/CMakeFiles/example_oct.dir/__/exampleOCTAVE_wrap.cxx.o' failed
make[2]: *** [octave/CMakeFiles/example_oct.dir/__/exampleOCTAVE_wrap.cxx.o] Error 1
CMakeFiles/Makefile2:301: recipe for target 'octave/CMakeFiles/example_oct.dir/all' failed
make[1]: *** [octave/CMakeFiles/example_oct.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 12 June 2016, 10:04 GMT
Reason for closing:  Upstream
Comment by Samantha McVey (samcv) - Thursday, 09 June 2016, 08:51 GMT
Tue 15 Mar 2016 was the last post in the linked ticket on the gnu octave bugtracker and in post #33 it is stated: "It seems that Octave is pretty close, or maybe already at the point where this bug can be closed." I am guessing this bug can probably be closed due to it being dealt with upstream and seems to be completely or mostly resolved. If there is a reason this should still stay open as it effects ArchLinux *specifically* as a distro and can't be dealt with upstream please comment back/reopen depending on which is applicable based on current status.

Loading...