Your message dated Fri, 09 Aug 2024 12:32:41 +0000
with message-id <[email protected]>
and subject line Bug#1069498: fixed in libx86emu 3.5-1.1
has caused the Debian Bug report #1069498,
regarding libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration
of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]
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.)
--
1069498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069498
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libx86emu
Version: 3.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi,
During a rebuild of all packages in sid, your package failed to build
on armhf.
Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 -fPIC
> -fvisibility=hidden -fomit-frame-pointer -Wall -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
> -Wl,-z,relro -Wl,-z,now -c ops.c
> mem.c: In function ‘vm_i_byte’:
> mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean
> ‘ins’? [-Werror=implicit-function-declaration]
> 581 | return inb(addr);
> | ^~~
> | ins
> mem.c: In function ‘vm_i_word’:
> mem.c:619:10: error: implicit declaration of function ‘inw’; did you mean
> ‘ins’? [-Werror=implicit-function-declaration]
> 619 | return inw(addr);
> | ^~~
> | ins
> mem.c: In function ‘vm_i_dword’:
> mem.c:657:10: error: implicit declaration of function ‘inl’; did you mean
> ‘ins’? [-Werror=implicit-function-declaration]
> 657 | return inl(addr);
> | ^~~
> | ins
> mem.c: In function ‘vm_o_byte’:
> mem.c:676:5: error: implicit declaration of function ‘outb’; did you mean
> ‘outs’? [-Werror=implicit-function-declaration]
> 676 | outb(val, addr);
> | ^~~~
> | outs
> mem.c: In function ‘vm_o_word’:
> mem.c:711:3: error: implicit declaration of function ‘outw’; did you mean
> ‘outs’? [-Werror=implicit-function-declaration]
> 711 | outw(val, addr);
> | ^~~~
> | outs
> mem.c: In function ‘vm_o_dword’:
> mem.c:748:3: error: implicit declaration of function ‘outl’; did you mean
> ‘outs’? [-Werror=implicit-function-declaration]
> 748 | outl(val, addr);
> | ^~~~
> | outs
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:22: mem.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libx86emu_3.5-1_unstable-armhf.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&[email protected]&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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 mark 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 ---
Source: libx86emu
Source-Version: 3.5-1.1
Done: Michael Prokop <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libx86emu, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Prokop <[email protected]> (supplier of updated libx86emu 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 02 Aug 2024 16:29:04 +0200
Source: libx86emu
Architecture: source
Version: 3.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia <[email protected]>
Changed-By: Michael Prokop <[email protected]>
Closes: 1069498
Changes:
libx86emu (3.5-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Guillem Jover ]
* Do not build on ARM architectures where there is no port I/O
(Closes: #1069498)
Checksums-Sha1:
a5eb44107cc74e386f1f46ad3d653e07f519a210 2016 libx86emu_3.5-1.1.dsc
4b016c59706a6f82ff372e9aa5814c80d310f870 6024 libx86emu_3.5-1.1.debian.tar.xz
eb2e3a914ca99a0a5c3ea2148e05b54b71856050 5860
libx86emu_3.5-1.1_source.buildinfo
Checksums-Sha256:
1d77c4e36a3fb895b658f522a89b393991c2d57673d16667ac535ba6f09f6f04 2016
libx86emu_3.5-1.1.dsc
29908d9f7ead99d0dad3d47dc67b23b7407906944bcb257e518c4630fb2815b4 6024
libx86emu_3.5-1.1.debian.tar.xz
35caa4909679740aa5d84741dc0818471cadcf1fefe1ecd27903a2432caa6049 5860
libx86emu_3.5-1.1_source.buildinfo
Files:
7a7d7f43cb5a620c86a2c87269694265 2016 libs optional libx86emu_3.5-1.1.dsc
8454b8583926ba9f9e3571da51bdeb7e 6024 libs optional
libx86emu_3.5-1.1.debian.tar.xz
2ffbd69ce94c20c9abeaa0d4e1570756 5860 libs optional
libx86emu_3.5-1.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEM8yxNkAa/shDo4djlqh4crfqNzcFAma15uUACgkQlqh4crfq
NzdZYBAAmkIuhcuoSpstb4FFE2vk8a2KktBzC0i+/+4AJtFXvOt8rwIuN9o8kXeX
wD7DhzhltkzpGeTgzK87TwNh2HnuuXyBiAOu82lWgdkBXRHD40K/ShwBQed7zW8b
5mxyjXvUnI5ub8jxllFD6QJ2os2NmaS4ihL14uR5tOo+n6L4Yfxz/38YLYy7rF5G
X+EgtuylCSdYK573O6V7bAKlqVLu93Qx9kkwKhuDzZF0YQC7hEsHw2RQPj5GcnZu
EswT59eZWEDiGeZLNASfKqapQPoEZH8xsUXWFYTBnf5ZXPwsNdDSQIHQmeWENFY7
G7wqTe82zRCb5fqTrfDBgUyHxo86NDzegUpJD/x0v7LI3DNOeYd2Lq4C8M/RRpg3
sRESR1HvgQslhBrpT3S3ocfGj9VTBFSUcdilUXyrElRLWRZ2l4Pj7jCh92OYDvBK
rEbvHfHxFG8yO+yjk120PP5ZkAJh+MEyj4fKkkLARaYSZydXkPt65+UwCMJwP/p+
dzTMPxKOyvmkiHzKerwwfIkoFXXPxCr7SIIW7hixRYJEdNWj93XbSMpHDsLXHkgi
vsKMuhyxZI9nAQBXSAsKJqxw3i7bmqSqZJObSL21WjwLPGOI5AIta9GHAiGNWBol
mwNcyCZEDQgcpY2pT0NPv5pm1XbxeOAj0Vj29hOiI//MllTDWT0=
=RtXb
-----END PGP SIGNATURE-----
pgp2eYU_4Avah.pgp
Description: PGP signature
--- End Message ---
