[DRE-maint] Bug#1075466: ruby-mmap2: ftbfs with GCC-14

Matthias Klose doko at debian.org
Wed Jul 3 13:42:46 BST 2024


Package: src:ruby-mmap2
Version: 2.2.9-1
Severity: important
Tags: sid trixie
User: debian-gcc at lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/ruby-mmap2_2.2.9-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
mmap.c:2125:46: error: passing argument 3 of ‘rb_iterate’ from incompatible pointer type [-Wincompatible-pointer-types]
 2125 |     rb_iterate(mm_internal_each, (VALUE)tmp, rb_yield, 0);
      |                                              ^~~~~~~~
      |                                              |
      |                                              VALUE (*)(VALUE) {aka long unsigned int (*)(long unsigned int)}
/usr/include/ruby-3.1.0/ruby/internal/iterator.h:283:75: note: expected ‘rb_block_call_func_t’ {aka ‘long unsigned int (*)(long unsigned int,  long unsigned int,  int,  const long unsigned int *, long unsigned int)’} but argument is of type ‘VALUE (*)(VALUE)’ {aka ‘long unsigned int (*)(long unsigned int)’}
  283 | VALUE rb_iterate(VALUE (*func1)(VALUE), VALUE data1, rb_block_call_func_t proc, VALUE data2);
      |                                                      ~~~~~~~~~~~~~~~~~~~~~^~~~
mmap.c: In function ‘mm_each_line’:
mmap.c:2147:5: warning: ‘rb_iterate’ is deprecated: by: rb_block_call since 1.9 [-Wdeprecated-declarations]
 2147 |     rb_iterate(mm_internal_each, (VALUE)tmp, rb_yield, 0);
      |     ^~~~~~~~~~
/usr/include/ruby-3.1.0/ruby/internal/iterator.h:283:7: note: declared here
  283 | VALUE rb_iterate(VALUE (*func1)(VALUE), VALUE data1, rb_block_call_func_t proc, VALUE data2);
      |       ^~~~~~~~~~
mmap.c:2147:46: error: passing argument 3 of ‘rb_iterate’ from incompatible pointer type [-Wincompatible-pointer-types]
 2147 |     rb_iterate(mm_internal_each, (VALUE)tmp, rb_yield, 0);
      |                                              ^~~~~~~~
      |                                              |
      |                                              VALUE (*)(VALUE) {aka long unsigned int (*)(long unsigned int)}
/usr/include/ruby-3.1.0/ruby/internal/iterator.h:283:75: note: expected ‘rb_block_call_func_t’ {aka ‘long unsigned int (*)(long unsigned int,  long unsigned int,  int,  const long unsigned int *, long unsigned int)’} but argument is of type ‘VALUE (*)(VALUE)’ {aka ‘long unsigned int (*)(long unsigned int)’}
  283 | VALUE rb_iterate(VALUE (*func1)(VALUE), VALUE data1, rb_block_call_func_t proc, VALUE data2);
      |                                                      ~~~~~~~~~~~~~~~~~~~~~^~~~
mmap.c: In function ‘mm_each_byte’:
mmap.c:2165:5: warning: ‘rb_iterate’ is deprecated: by: rb_block_call since 1.9 [-Wdeprecated-declarations]
 2165 |     rb_iterate(mm_internal_each, (VALUE)tmp, rb_yield, 0);
      |     ^~~~~~~~~~
/usr/include/ruby-3.1.0/ruby/internal/iterator.h:283:7: note: declared here
  283 | VALUE rb_iterate(VALUE (*func1)(VALUE), VALUE data1, rb_block_call_func_t proc, VALUE data2);
      |       ^~~~~~~~~~
mmap.c:2165:46: error: passing argument 3 of ‘rb_iterate’ from incompatible pointer type [-Wincompatible-pointer-types]
 2165 |     rb_iterate(mm_internal_each, (VALUE)tmp, rb_yield, 0);
      |                                              ^~~~~~~~
      |                                              |
      |                                              VALUE (*)(VALUE) {aka long unsigned int (*)(long unsigned int)}
/usr/include/ruby-3.1.0/ruby/internal/iterator.h:283:75: note: expected ‘rb_block_call_func_t’ {aka ‘long unsigned int (*)(long unsigned int,  long unsigned int,  int,  const long unsigned int *, long unsigned int)’} but argument is of type ‘VALUE (*)(VALUE)’ {aka ‘long unsigned int (*)(long unsigned int)’}
  283 | VALUE rb_iterate(VALUE (*func1)(VALUE), VALUE data1, rb_block_call_func_t proc, VALUE data2);
      |                                                      ~~~~~~~~~~~~~~~~~~~~~^~~~
make[1]: *** [Makefile:246: mmap.o] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>/debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/mmap2-2.2.9/ext/mmap'
ERROR:  Error installing /tmp/d20240702-2322959-e4lt0l/mmap2-2.2.9.gem:
	ERROR: Failed to build gem native extension.

    current directory: /<<PKGBUILDDIR>>/debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/mmap2-2.2.9/ext/mmap
/usr/bin/ruby3.1 -I/usr/lib/ruby/vendor_ruby extconf.rb
current directory: /<<PKGBUILDDIR>>/debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/mmap2-2.2.9/ext/mmap
make V\=1 CC\=gcc\ -fdebug-prefix-map\=/<<PKGBUILDDIR>>\=. CXX\=g++\ -fdebug-prefix-map\=/<<PKGBUILDDIR>>\=. DESTDIR\= sitearchdir\=./.gem.20240702-2322964-oey4bj sitelibdir\=./.gem.20240702-2322964-oey4bj clean
current directory: /<<PKGBUILDDIR>>/debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/mmap2-2.2.9/ext/mmap
make V\=1 CC\=gcc\ -fdebug-prefix-map\=/<<PKGBUILDDIR>>\=. CXX\=g++\ -fdebug-prefix-map\=/<<PKGBUILDDIR>>\=. DESTDIR\= sitearchdir\=./.gem.20240702-2322964-oey4bj sitelibdir\=./.gem.20240702-2322964-oey4bj
Building has failed. See above output for more information on the failure.
make failed, exit code 2

Gem files will remain installed in /<<PKGBUILDDIR>>/debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/mmap2-2.2.9 for inspection.
Results logged to /<<PKGBUILDDIR>>/debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/extensions/x86_64-linux/3.1.0/mmap2-2.2.9/gem_make.out
/usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `run': /usr/bin/ruby3.1 -S gem install --config-file /dev/null --verbose --local --verbose --no-document --ignore-dependencies --install-dir debian/ruby-mmap2/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 /tmp/d20240702-2322959-e4lt0l/mmap2-2.2.9.gem (Gem2Deb::CommandFailed)
	from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:213:in `block in run_gem'
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:87:in `maybe_crossbuild'
	from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:212:in `run_gem'
	from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:121:in `block in install_files_and_build_extensions'
	from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:69:in `each'
	from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:69:in `install_files_and_build_extensions'
	from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:28:in `build'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:54:in `block in install'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:52:in `each'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:52:in `install'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:163:in `install'
	from /usr/bin/dh_ruby:89:in `<main>'
dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-mmap2 returned exit code 1
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



More information about the Pkg-ruby-extras-maintainers mailing list