On 05/20/2017 08:53 AM, Finn Thain wrote:
Btw, if you build firebird3.0 in this chroot without updating the glibc,
the problem will actually go away.
OK, I will try that too. But first I will try to reproduce the bug.
What's the quickest way to reproduce the build failure for the firebird3.0
deb?
1. Make sure you have the necessary "deb-src" entries in your sources.list:
# binary default
deb http://ftp.ports.debian.org/debian-ports/ unstable main
deb http://incoming.ports.debian.org/buildd/ unstable main
deb http://ftp.ports.debian.org/debian-ports/ unreleased main
# source
deb-src http://ftp.debian.org/debian/ unstable main
deb-src http://incoming.debian.org/debian-buildd/ buildd-unstable main
2. Run "apt update"
3. apt install devscripts && apt build-dep firebird3.0
4. dget -u http://deb.debian.org/debian/pool/main/f/firebird3.0/firebird3.0_3.0.2.32703.ds4-1.dsc
5. cd firebird3.0-3.0.2.32703.ds4/
6. ./debian/rules binary-arch
It should hang at some point when running the compiled binary on Aranym
or qemu-system. On qemu-user, it will just crash but for other reasons.
Although I didn't test it with qemu-system, I am very confident it should
hang the same way as on Aranym. The qemu-user crash is related to the
broken atomics in qemu-user.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@xxxxxxxxxx
`. `' Freie Universitaet Berlin - glaubitz@xxxxxxxxxxxxxxxxxxx
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
