[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

qemu version used on sh4 buildds (was: Bug#914323: file: non-zero exit code for shared objects on sh4)

Andrius Merkys wrote...

> on sh4 many package builds are terminated in dh_shlibdeps stage due to:
> dh_shlibdeps: file -e apptype -e ascii -e encoding -e cdf -e compress -e tar <<shared_object>> returned exit code 1
> Observed at least in build logs of libssh [1], apt [2] and cod-tools [3].

> [1] https://buildd.debian.org/status/fetch.php?pkg=libssh&arch=sh4&ver=0.8.5-1&stamp=1542810549&raw=0
> [2] https://buildd.debian.org/status/fetch.php?pkg=apt&arch=sh4&ver=1.8.0%7Ealpha2%2Bb1&stamp=1542808944&raw=0

Built on sh4-gandi-01.buildd.org

> [3] https://buildd.debian.org/status/fetch.php?pkg=cod-tools&arch=sh4&ver=2.2%2Bdfsg-4&stamp=1542808526&raw=0

Built on sh4-do-01.buildd.org

Long story short: The file(1) program caused the build errors on sh4 for
several packages. After *many* hours of digging I found the pread64
system call used by libmagic isn't properly translated when using the
stretch version of qemu-user-static (1:2.8+dfsg-6+deb9u5). The
buster/sid version has upstream's fix¹, and I can confirm file(1) will
work as exepected then. So, not a bug in the file package, closing.

The thing that puzzles me: James Clarke (jrtc27, cc:'ed) stated the
buildds use a manually built and fairly recent qemu version. These two
bits of information don't match.

As I neither have access to the buildds nor am interested in getting
one: Can you please check the problem is really fixed there? Should
be as simple as running "file /bin/ls" in a qemulated sh4 chroot.

Expected result: /bin/ls: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=bc61964767543a3ac5b756454ac96634c24a9f1b, for GNU/Linux 3.2.0, stripped

Broken: /bin/ls: ERROR: error reading (Invalid argument)
(also, non-zero exit)



¹ https://git.qemu.org/?p=qemu.git;a=blobdiff;f=linux-user/syscall.c;h=9268c3ef691514a654fd058f4d3c341600197a22;hp=8047bf3aacad4338960772c83c26d68743efccd7;hb=8bf8e9df4a7d82c7a47cc961c9cdee1615595de0;hpb=541e1690420d293c1b09eeb128fac74e98cbef7a

Attachment: signature.asc
Description: PGP signature

Reply to: