Your message dated Tue, 12 Oct 2021 10:48:48 +0000
with message-id <e1mafky-000bek...@fasolo.debian.org>
and subject line Bug#984109: fixed in libgetdata 0.10.0-11
has caused the Debian Bug report #984109,
regarding libgetdata: ftbfs with GCC-11
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 ow...@bugs.debian.org
immediately.)


-- 
984109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgetdata
Version: 0.10.0-9
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libgetdata_0.10.0-9_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  435 |   GD_COMPLEX128, data_out)
      |                 2                                                   
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(COMPLEX(4)/COMPLEX(8)).
getdata.f90:406:66:

  406 |   first_frame, first_sample, num_frames, num_samples, GD_FLOAT64, 
data_out)
      |                                                                  1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                                 
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(REAL(8)/COMPLEX(8)).
getdata.f90:392:66:

  392 |   first_frame, first_sample, num_frames, num_samples, GD_FLOAT32, 
data_out)
      |                                                                  1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                                 
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(REAL(4)/COMPLEX(8)).
getdata.f90:378:64:

  378 |   first_frame, first_sample, num_frames, num_samples, GD_INT64, 
data_out)
      |                                                                1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                               
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(8)/COMPLEX(8)).
getdata.f90:364:64:

  364 |   first_frame, first_sample, num_frames, num_samples, GD_INT32, 
data_out)
      |                                                                1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                               
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/COMPLEX(8)).
getdata.f90:350:64:

  350 |   first_frame, first_sample, num_frames, num_samples, GD_INT16, 
data_out)
      |                                                                1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                               
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(2)/COMPLEX(8)).
getdata.f90:336:63:

  336 |   first_frame, first_sample, num_frames, num_samples, GD_INT8, data_out)
      |                                                               1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                              
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(1)/COMPLEX(8)).
getdata.f90:322:63:

  322 |   first_frame, first_sample, num_frames, num_samples, GD_NULL, 0)
      |                                                               1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                              
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/COMPLEX(8)).
make[4]: *** [Makefile:665: getdata.o] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build-main/bindings/f77'
make[3]: *** [Makefile:581: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build-main/bindings'
make[2]: *** [Makefile:587: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build-main'
dh_auto_build: error: cd build-main && make -j4 returned exit code 2
make[1]: *** [debian/rules:43: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:28: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.10.0-11
Done: Alastair McKinstry <mckins...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libgetdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 984...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated libgetdata 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 12 Oct 2021 11:16:35 +0100
Source: libgetdata
Architecture: source
Version: 0.10.0-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 984109
Changes:
 libgetdata (0.10.0-11) unstable; urgency=medium
 .
   * Upsdate gfortran detection;set flags for gf11 too. Closes: #984109
Checksums-Sha1:
 ad3574d5fcf05210cc4883e3250f085742fd8c76 2756 libgetdata_0.10.0-11.dsc
 242ffa2aca8c07f4bed80b12e91e53c061f70921 7100 
libgetdata_0.10.0-11.debian.tar.xz
Checksums-Sha256:
 3bc0446c7d20d2e565cb1a1a718ec3bf5333429d324a9196145e40555decd6ff 2756 
libgetdata_0.10.0-11.dsc
 4078e2c3ebf377b3f45b7024e545dc83cccfeef1c5f39d28a2c529af531b33de 7100 
libgetdata_0.10.0-11.debian.tar.xz
Files:
 5e3c720466d01632154a099cfd996100 2756 science optional libgetdata_0.10.0-11.dsc
 89654b31a5eaa3033031ad5e76ba3206 7100 science optional 
libgetdata_0.10.0-11.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmFlZXYACgkQy+a7Tl2a
06X8Fw/+PtZyzG65baiTnlLmor2owcnM30hOlHqdKTW7+PA3ZqtjqeV4CMxy36P3
FYV7XEP39juExBe17IbDKDgRAalQaxjLdzlax4govJ0f4iUXzlbWsbU6ogIOddi8
MrvRwWtTtXJVqrBVIChBBZKWIUVlEnnVlotMbfCUDH5oBZ5qeATARe9N0/LNiSEQ
ikNqz8l20b+KAcveYL5aHGNCcX2gnEWsCJemvtWPMekaS1vsXyIo5Cy8/ysq0fro
IOvA8MqliT0nUfY9Krg6bvy1A7i8JP3EiOxHuhO29DPcYj9wVoqMFS2WJkcGViGW
YGAZboy8wLwtu9RZFa80wl+A344qomjf6wDIjsKvOo3SwK48DtIg7M9O7mUSd6PE
N2QAfwvoL9po6hZDm5QHajXnbZc+aIL1yIUZU1fKezimoGQ/gREnFf6i8xGqPrm1
uelwcG3Lybb19Ba2UuocK8gjgmKqIT5JtwpBEb3ZguNlbpXPeipPEI9zQamglW6T
Jq1bUvcfBKSDgNxdVVUbjXcT9reiFS+tAbLjBG7onoW0tNkT8kfPIeUKVyrexnoK
OQaLexjHNcai2FalIvodX69wbh+ywbfSYQrRZ3OctUghYqgV92iLS0mTfleUyKgg
cDhD2a491J7oWt4s3vJS/7alb01xxK5WJmGuTX4CaRrxH+J0uSI=
=aSZz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to