Your message dated Thu, 14 May 2026 22:23:28 +0200
with message-id <[email protected]>
and subject line autoconf fixed in sid
has caused the Debian Bug report #1133582,
regarding octave-dicom: ftbfs with GCC-16
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1133582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133582
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:octave-dicom
Version: 0.7.1-1
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: ftbfs-gcc-16
Hi,
octave-dicom fails to build in a test rebuild on at least amd64 and arm64 with
gcc-16/g++-16, but builds properly with gcc-15/g++-15. The severity of this
report will be raised before the forky release.
The full build log can be found at:
https://people.debian.org/~ema/gcc-16-rebuilds/output-1/octave-dicom_arm64.build.xz
The last lines of the build log are at the end of this report.
To build with GCC 16, either set CC=gcc-16 CXX=g++-16 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures include unused (but set) variables, array subscripts
partly outside array bounds, and new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-16/porting_to.html
Please only close this issue after double-checking that the package can be
built correctly with GCC 16.
Please do not reassign this bug to another package. If a fix in another package
is required, then file a bug for the other package (or clone), and mark this
bug as blocked by the bug in the other package.
[...]
dicomdict.cpp: In function ‘void load_dicom_dict(const char*)’:
dicomdict.cpp:335:21: error: ‘load_path’ has not been declared
335 | resolved_filename=load_path::find_file(std::string(filename));
| ^~~~~~~~~
In file included from dicomdict.cpp:34:
config.h:43:34: error: ‘valid_identifier’ was not declared in this scope; did
you mean ‘octave::valid_identifier’?
43 | #define OCTAVE__VALID_IDENTIFIER valid_identifier
| ^~~~~~~~~~~~~~~~
dicomdict.cpp:385:13: note: in expansion of macro ‘OCTAVE__VALID_IDENTIFIER’
385 | if (! OCTAVE__VALID_IDENTIFIER (key))
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/octave-11.1.0/octave/../octave/oct.h:42,
from dicomdict.cpp:29:
/usr/include/octave-11.1.0/octave/../octave/utils.h:47:27: note:
‘octave::valid_identifier’ declared here
47 | extern OCTINTERP_API bool valid_identifier (const std::string& s);
| ^~~~~~~~~~~~~~~~
dicomdict.cpp: In function ‘void load_dicom_dict(const char*)’:
dicomdict.cpp:335:21: error: ‘load_path’ has not been declared
335 | resolved_filename=load_path::find_file(std::string(filename));
| ^~~~~~~~~
In file included from dicomdict.cpp:34:
config.h:43:34: error: ‘valid_identifier’ was not declared in this scope; did
you mean ‘octave::valid_identifier’?
43 | #define OCTAVE__VALID_IDENTIFIER valid_identifier
| ^~~~~~~~~~~~~~~~
dicomdict.cpp:385:13: note: in expansion of macro ‘OCTAVE__VALID_IDENTIFIER’
385 | if (! OCTAVE__VALID_IDENTIFIER (key))
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/octave-11.1.0/octave/../octave/oct.h:42,
from dicomdict.cpp:29:
/usr/include/octave-11.1.0/octave/../octave/utils.h:47:27: note:
‘octave::valid_identifier’ declared here
47 | extern OCTINTERP_API bool valid_identifier (const std::string& s);
| ^~~~~~~~~~~~~~~~
In file included from isdicom.cpp:28:
isdicom.cpp: In function ‘bool isdicom(const std::string&)’:
config.h:40:27: error: ‘file_stat’ was not declared in this scope; did you mean
‘octave::sys::file_stat’?
40 | #define OCTAVE__FILE_STAT file_stat
| ^~~~~~~~~
isdicom.cpp:47:10: note: in expansion of macro ‘OCTAVE__FILE_STAT’
47 | return OCTAVE__FILE_STAT (namebuff).exists () && reader.Read ();
| ^~~~~~~~~~~~~~~~~
In file included from isdicom.cpp:25:
/usr/include/octave-11.1.0/octave/../octave/file-stat.h:208:18: note:
‘octave::sys::file_stat’ declared here
208 | class OCTAVE_API file_stat : public base_file_stat
| ^~~~~~~~~
In file included from dicomread.cpp:29:
dicomread.cpp: In function ‘octave_value_list Fdicomread(const
octave_value_list&, int)’:
config.h:49:18: error: ‘const class octave_value’ has no member named ‘is_map’
49 | #define OV_ISMAP is_map
| ^~~~~~
dicomread.cpp:97:21: note: in expansion of macro ‘OV_ISMAP’
97 | if (! args(0).OV_ISMAP ())
| ^~~~~~~~
make[1]: *** [Makefile:17: dicomdict.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:23: isdicom.oct] Error 1
make[1]: *** [Makefile:23: dicomread.oct] Error 1
make[1]: *** [Makefile:23: dicomdict.oct] Error 1
g++ -I/usr/include/octave-11.1.0/octave/.. -I/usr/include/octave-11.1.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-dicom-0.7.1=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -o dicomuid.oct
/tmp/oct-NCNYCy.o -lgdcmCommon -lgdcmDICT -lgdcmDSED -lgdcmIOD -lgdcmMSFF
-shared -Wl,-Bsymbolic -Wl,-z,relro -flto=auto -ffat-lto-objects -Wl,-z,relro
g++ -I/usr/include/octave-11.1.0/octave/.. -I/usr/include/octave-11.1.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-dicom-0.7.1=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -o
__dicom_decodeuid__.oct /tmp/oct-q42oUW.o -lgdcmCommon -lgdcmDICT -lgdcmDSED
-lgdcmIOD -lgdcmMSFF -shared -Wl,-Bsymbolic -Wl,-z,relro -flto=auto
-ffat-lto-objects -Wl,-z,relro
g++ -I/usr/include/octave-11.1.0/octave/.. -I/usr/include/octave-11.1.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-dicom-0.7.1=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -o _gendicomdict.oct
/tmp/oct-yjUBYM.o -lgdcmCommon -lgdcmDICT -lgdcmDSED -lgdcmIOD -lgdcmMSFF
-shared -Wl,-Bsymbolic -Wl,-z,relro -flto=auto -ffat-lto-objects -Wl,-z,relro
make[1]: Leaving directory '/tmp/oct-O5oToD/octave-dicom-0.7.1/src'
error: pkg: error running 'make' for the dicom package
error: called from
configure_make at line 121 column 9
install at line 202 column 7
pkg at line 692 column 9
/usr/share/dh-octave/install-pkg.m at line 45 column 1
dh_auto_install: error: octave --no-gui --no-history --silent --no-init-file
--no-window-system /usr/share/dh-octave/install-pkg.m
/build/reproducible-path/octave-dicom-0.7.1/debian/octave-dicom/usr/share/octave/packages
/build/reproducible-path/octave-dicom-0.7.1/debian/octave-dicom/usr/lib/aarch64-linux-gnu/octave/packages
returned exit code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--- End Message ---
--- Begin Message ---
Hi,
these bugs were blocked by #1133694 in autoconf.
autoconf 0.73-1 was fixed and 0.73-2 got uploaded to unstable now so those bugs
can be closed.
(I also closed the autoconf one properly now)
Regards,
Rene
--- End Message ---
