* Steffen Grunewald <[email protected]> [2021-02-22 09:25]:
Package: liboctave-dev
Version: 6.1.1~hg.2021.01.26-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Building Octave interfaces for one of our software packages, in a
Bullseye environment (pbuilder)
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
Failure to build:
In file included from /usr/include/octave-6.1.1~hg.2021.01.26/octave/../octave/defun-int.h:35,
from /usr/include/octave-6.1.1~hg.2021.01.26/octave/../octave/defun-dld.h:35,
from /usr/include/octave-6.1.1~hg.2021.01.26/octave/../octave/oct.h:35,
from swiglal_octave.cpp:175:
/usr/include/octave-6.1.1~hg.2021.01.26/octave/../octave/version.h:39:31: error: missing binary operator before token "~"
39 | #define OCTAVE_PATCH_VERSION 1~hg.2021.01.26
| ^
swiglal_octave.cpp:181:63: note: in expansion of macro 'OCTAVE_PATCH_VERSION'
181 | ( (OCTAVE_MAJOR_VERSION<<16) + (OCTAVE_MINOR_VERSION<<8) + (OCTAVE_PATCH_VERSION + 0) >= ((major)<<16) + ((minor)<<8) + (patch) )
| ^~~~~~~~~~~~~~~~~~~~
swiglal_octave.cpp:268:5: note: in expansion of macro 'SWIG_OCTAVE_PREREQ'
268 | #if SWIG_OCTAVE_PREREQ(4,2,0)
| ^~~~~~~~~~~~~~~~~~
swiglal_octave.cpp:271:10: fatal error: octave/toplev.h: No such file or directory
271 | #include <octave/toplev.h>
| ^~~~~~~~~~~~~~~~~
compilation terminated.
swiglal_octave.cpp is generated by SWIG and therefore not part of our
software package.
* What outcome did you expect instead?
OCTAVE_PATCH_VERSION needs to be santized better than just adding 0.
The same code works with Stretch and Buster.
Previous versions of Octave sometimes also had a "~" in the _build_ version
number but
never in the "patch" version itself.
I know that this is not the right answer to the raised issued, but are
you aware that SWIG does not work with Octave >= 6.0?
See: https://github.com/swig/swig/issues/1893
Even if the the present bug is fixed, any program using SWIG and the
version of Octave currently in bullseye will fail.
So, I may be wrong, but I do not see the point in fixing this bug.
Best,
Rafael Laboissière
