Your message dated Thu, 8 Sep 2022 15:40:53 +0200
with message-id <d2968ac8-0ede-d48a-cdca-c74d224af...@debian.org>
and subject line buildable again
has caused the Debian Bug report #1005473,
regarding gcc-11-cross-ports: FTBFS: s-tsmona.adb:160: undefined reference to 
`dladdr'
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.)


-- 
1005473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-11-cross-ports
Version: 8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile 
> /<<PKGBUILDDIR>>/gcc/build/./gcc/xgcc -B/<<PKGBUILDDIR>>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnux32/bin/ -B/usr/x86_64-linux-gnux32/lib/ -isystem 
> /usr/x86_64-linux-gnux32/include -isystem 
> /usr/x86_64-linux-gnux32/sys-include -isystem 
> /<<PKGBUILDDIR>>/gcc/build/sys-include    -DHAVE_CONFIG_H -I. 
> -I../../../src/libgfortran  -iquote../../../src/libgfortran/io 
> -I../../../src/libgfortran/../gcc -I../../../src/libgfortran/../gcc/config 
> -I../../../src/libgfortran/../libquadmath -I../.././gcc 
> -I../../../src/libgfortran/../libgcc -I../libgcc 
> -I../../../src/libgfortran/../libbacktrace -I../libbacktrace 
> -I../libbacktrace  -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes 
> -Wold-style-definition -Wextra -Wwrite-strings 
> -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk 
> -fcx-fortran-rules -ffunction-sections -fdata-sections   -g -O2 -MT 
> iany_i4.lo -MD -MP -MF .deps/iany_i4.Tpo -c -o iany_i4.lo `test -f 
> '../../../src/libgfortran/generated/iany_i4.c' || echo 
> '../../../src/libgfortran/'`../../../src/libgfortran/generated/iany_i4.c
> libtool: compile:  /<<PKGBUILDDIR>>/gcc/build/./gcc/xgcc 
> -B/<<PKGBUILDDIR>>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnux32/bin/ 
> -B/usr/x86_64-linux-gnux32/lib/ -isystem /usr/x86_64-linux-gnux32/include 
> -isystem /usr/x86_64-linux-gnux32/sys-include -isystem 
> /<<PKGBUILDDIR>>/gcc/build/sys-include -DHAVE_CONFIG_H -I. 
> -I../../../src/libgfortran -iquote../../../src/libgfortran/io 
> -I../../../src/libgfortran/../gcc -I../../../src/libgfortran/../gcc/config 
> -I../../../src/libgfortran/../libquadmath -I../.././gcc 
> -I../../../src/libgfortran/../libgcc -I../libgcc 
> -I../../../src/libgfortran/../libbacktrace -I../libbacktrace 
> -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes 
> -Wold-style-definition -Wextra -Wwrite-strings 
> -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk 
> -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -MT iany_i4.lo 
> -MD -MP -MF .deps/iany_i4.Tpo -c ../../../src/libgfortran/generated/iany_i4.c 
>  -fPIC -DPIC -o .libs/iany_i4.o
> /usr/x86_64-linux-gnux32/bin/ld: s-trasym.o: in function 
> `system__traceback__symbolic__module_name__getXnn':
> /<<PKGBUILDDIR>>/gcc/build/gcc/ada/rts/s-tsmona.adb:160: undefined reference 
> to `dladdr'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/gcc-11-cross-ports_8_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
these are buildable again with recent c-t-b updates.

--- End Message ---

Reply via email to