Your message dated Thu, 22 Aug 2019 11:05:57 +0200
with message-id <2fde7e62-f29b-7855-358e-6b4e42265...@debian.org>
and subject line Re: Fixed : skiboot: ftbfs with GCC-9
has caused the Debian Bug report #925831,
regarding skiboot: ftbfs with GCC-9
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.)


-- 
925831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:skiboot
Version: 6.2-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/skiboot_6.2-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
        libc/test/run-snprintf-gcov libc/test/run-memops-gcov 
libc/test/run-stdlib-gcov libc/test/run-ctype-gcov \
        libc/test/run-snprintf-gcov.gcda libc/test/run-memops-gcov.gcda 
libc/test/run-stdlib-gcov.gcda libc/test/run-ctype-gcov.gcda \
        libc/test/run-snprintf-gcov.gcno libc/test/run-memops-gcov.gcno 
libc/test/run-stdlib-gcov.gcno libc/test/run-ctype-gcov.gcno \
        libc/test/run-snprintf-gcov-test.gcda 
libc/test/run-memops-gcov-test.gcda libc/test/run-stdlib-gcov-test.gcda 
libc/test/run-ctype-gcov-test.gcda \
        libc/test/run-snprintf-gcov-test.gcno 
libc/test/run-memops-gcov-test.gcno libc/test/run-stdlib-gcov-test.gcno 
libc/test/run-ctype-gcov-test.gcno \
        libc/test/run-snprintf-test.o libc/test/run-memops-test.o 
libc/test/run-stdlib-test.o libc/test/run-ctype-test.o
rm -f x86_64-linux-gnu/libflash/test/test-ipmi-hiomap.o 
x86_64-linux-gnu/libflash/test/stubs.o x86_64-linux-gnu/libflash/ipmi-hiomap.o 
x86_64-linux-gnu/libflash/test/test-blocklevel.o 
x86_64-linux-gnu/libflash/test/stubs.o 
x86_64-linux-gnu/libflash/test/test-flash.o 
x86_64-linux-gnu/libflash/test/stubs.o 
x86_64-linux-gnu/libflash/test/mbox-server.o 
x86_64-linux-gnu/libflash/test/test-ecc.o 
x86_64-linux-gnu/libflash/test/stubs.o 
x86_64-linux-gnu/libflash/test/mbox-server.o 
x86_64-linux-gnu/libflash/test/test-mbox.o 
x86_64-linux-gnu/libflash/test/stubs.o 
x86_64-linux-gnu/libflash/test/mbox-server.o
rm -f test/hello_world/hello_kernel/hello_kernel
rm -f test/sreset_world/sreset_kernel/sreset_kernel
rm -f -f libstb/test/*.gcda libstb/test/*.gcno
rm -f x86_64-linux-gnu/libflash/test/test-ipmi-hiomap.d 
x86_64-linux-gnu/libflash/test/stubs.d x86_64-linux-gnu/libflash/ipmi-hiomap.d 
x86_64-linux-gnu/libflash/test/test-blocklevel.d 
x86_64-linux-gnu/libflash/test/stubs.d 
x86_64-linux-gnu/libflash/test/test-flash.d 
x86_64-linux-gnu/libflash/test/stubs.d 
x86_64-linux-gnu/libflash/test/mbox-server.d 
x86_64-linux-gnu/libflash/test/test-ecc.d 
x86_64-linux-gnu/libflash/test/stubs.d 
x86_64-linux-gnu/libflash/test/mbox-server.d 
x86_64-linux-gnu/libflash/test/test-mbox.d 
x86_64-linux-gnu/libflash/test/stubs.d 
x86_64-linux-gnu/libflash/test/mbox-server.d
rm -f test/hello_world/hello_kernel/hello_kernel.o
rm -f test/sreset_world/sreset_kernel/sreset_kernel.o
rm -f *.[odsa] asm/*.[odsa] core/*.[odsa] hw/*.[odsa] hw/fsp/*.[odsa] 
hw/ec/*.[odsa] hw/ast-bmc/*.[odsa] hw/ipmi/*.[odsa] platforms/*.[odsa] 
platforms/ibm-fsp/*.[odsa] platforms/rhesus/*.[odsa] platforms/astbmc/*.[odsa] 
platforms/mambo/*.[odsa] platforms/qemu/*.[odsa] libfdt/*.[odsa] 
libflash/*.[odsa] libxz/*.[odsa] libpore/*.[odsa] libc/*.[odsa] 
libc/string/*.[odsa] libc/ctype/*.[odsa] libc/stdlib/*.[odsa] 
libc/stdio/*.[odsa] ccan/*.[odsa] ccan/list/*.[odsa] ccan/str/*.[odsa] 
hdata/*.[odsa] libstb/*.[odsa] libstb/mbedtls/*.[odsa] libstb/drivers/*.[odsa] 
libstb/tss/*.[odsa]
rm -f *.elf skiboot.lid *.map skiboot.lds skiboot.lid.xz
rm -f include/asm-offsets.h version.c .version
rm -f skiboot.info external/gard/gard.info external/pflash/pflash.info
rm -f extract-gcov skiboot.lid.stb skiboot.lid.xz.stb
rm -f *~ asm/*~ core/*~ hw/*~ hw/fsp/*~ hw/ec/*~ hw/ast-bmc/*~ hw/ipmi/*~ 
platforms/*~ platforms/ibm-fsp/*~ platforms/rhesus/*~ platforms/astbmc/*~ 
platforms/mambo/*~ platforms/qemu/*~ libfdt/*~ libflash/*~ libxz/*~ libpore/*~ 
libc/*~ libc/string/*~ libc/ctype/*~ libc/stdlib/*~ libc/stdio/*~ ccan/*~ 
ccan/list/*~ ccan/str/*~ hdata/*~ libstb/*~ libstb/mbedtls/*~ libstb/drivers/*~ 
libstb/tss/*~ include/*~
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_clean
        rm -f debian/debhelper-build-stamp
        rm -rf debian/.debhelper/
        rm -f -- debian/qemu-skiboot.substvars debian/opal-utils.substvars 
debian/files
        rm -fr -- debian/qemu-skiboot/ debian/tmp/ debian/opal-utils/
        find .  \( \( \
                \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
-type f -a \
                \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
                 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
                 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
                 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
                \) -exec rm -f {} + \) -o \
                \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   debian/rules override_dh_auto_build-arch
make[1]: Entering directory '/<<PKGBUILDDIR>>'
GARD_VERSION=gard-6.2 make V=1 -C external/gard/
make[2]: Entering directory '/<<PKGBUILDDIR>>/external/gard'
ln -sf ../../libflash ./libflash
ln -sf ../../ccan ./ccan
ln -sf ../common ./common
ln -sf ../../hw/ast-bmc/ast-sf-ctrl.c common/ast-sf-ctrl.c
ln -sf ../../include/ast.h common/ast.h
ln -sf arch_flash_x86_io.h common/io.h
ln -sf ../../include/lpc.h common/lpc.h
cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -Wall -Werror -Wno-stringop-truncation -I. -c 
version.c -o version.o
cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -Wall -Werror -Wno-stringop-truncation -I. -c 
gard.c -o gard.o
cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -Wall -Werror -Wno-stringop-truncation -I. -c 
units.c -o units.o
cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -Wall -Werror -Wno-stringop-truncation -I. -c 
libflash/libflash.c -o libflash-libflash.o
cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -Wall -Werror -Wno-stringop-truncation -I. -c 
libflash/libffs.c -o libflash-libffs.o
cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -Wall -Werror -Wno-stringop-truncation -I. -c 
libflash/ecc.c -o libflash-ecc.o
libflash/ecc.c: In function 'memcpy_to_ecc_unaligned':
libflash/ecc.c:419:24: error: taking address of packed member of 'struct ecc64' 
may result in an unaligned pointer value [-Werror=address-of-packed-member]
  419 |   memcpy(inc_uint64_by(&ecc_word.data, alignment), src, bytes_wanted);
      |                        ^~~~~~~~~~~~~~
libflash/ecc.c:448:24: error: taking address of packed member of 'struct ecc64' 
may result in an unaligned pointer value [-Werror=address-of-packed-member]
  448 |   memcpy(inc_uint64_by(&ecc_word.data, len), inc_ecc64_by(dst, len),
      |                        ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [rules.mk:38: libflash-ecc.o] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/external/gard'
make[1]: *** [debian/rules:25: override_dh_auto_build-arch] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:16: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

--- End Message ---
--- Begin Message ---
Version: 6.5-1

On 21.08.19 16:51, Frédéric Bonnard wrote:
> Hi Matthias,
> new upstream skiboot 6.5 fixed that bug and I released a package of it :
> https://buildd.debian.org/status/fetch.php?pkg=skiboot&arch=amd64&ver=6.5-1&stamp=1566396860&raw=0
> 
>> Please keep the issue open until the package can be built in
>> a follow-up test rebuild.
> 
> Is the previous buildd build enough or do you plan your own test rebuild ?
> I don't see any new rebuild in https://people.debian.org/~doko/logs/?C=M;O=D
> I am asking because I'd like to know when we can close that bug : now
> already or later after some other rebuild.
> 
> Thanks
> 
> F.
> 

--- End Message ---

Reply via email to