FTBFS on armhf

[Graham Inggs]

As posted on the debian-arm mailing list:
https://lists.debian.org/debian-arm/2016/07/msg00090.html

Dpkg in Ubuntu carries a patch introduced in dpkg 1.16.1.2ubuntu2 from
December 2011.
The changelog entry reads:

* Apply patch from Steve McIntyre to special-case armhf/armel ELF
  objects in Shlibs/Objdump.pm, so we don't get incorrect deps.

Wine-development since 1.9.9-1 has a script (sonames2elf) [1] and some
magic in debian/rules [2] that generates a list of shared libraries
that libwine should recommend and depend on.
This change in wine-development and the patch to dpkg above, together
cause wine-development to FTBFS on Ubuntu armhf, see the second part
of my report in #827770 [3], where the following error and similar are
mentioned.

dpkg-shlibdeps: error: couldn't find library libfontconfig.so.1 needed by debian/tmp/elf.depends (ELF format: 'elf32-littlearm-sfabi'; RPATH:'')

Reverting Ubuntu's dpkg patch causes dpkg-shlibdeps to find the libraries.
Alternatively, using readelf -h I found the ELF header flags of
elf.depends and elf.recommends to be 0x5000600. After using hte to
change these flags to 0x5000402, dpkg-shlibdeps was also able to find
the lbraries.

How can I set these flags correctly? I have tried passing
-mfloat-abi=hard and -mhard-float to gcc from sonames2elf, but neither
had an effect.

[1] https://anonscm.debian.org/git/pkg-wine/wine.git/tree/debian/scripts/sonames2elf
[2] https://anonscm.debian.org/git/pkg-wine/wine.git/tree/debian/rules#n162
[3] https://bugs.debian.org/827770

[Bryan Quigley (bryanquigley)]

Added dpkg as maybe that patch is no longer required?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Graham Inggs (ginggs)]

I've attached a debdiff of the dpkg patch being discussed.

A couple of weeks ago I asked Adam Conrad by email, "Is this patch still needed in Ubuntu? Should it go into Debian?", and received the following reply.

"Yes, it's needed in Ubuntu. It would be needed in Debian if Debian
users ever built on machines with both armel and armhf binaries
installed (which happens on Ubuntu with gcc-multilib, because we
build a libc-armel and Debian doesn't).

If this is causing a build failure in Wine, Wine is buggy, not dpkg."

[Graham Inggs (ginggs)]

See also LP: #1187722
dpkg-shlibdeps fails on armhf ELF binaries that do not define architecture specific information

[Graham Inggs (ginggs)]

See also https://bugs.debian.org/853793

[Jeremy Bícha (jbicha)]

Fixed in zesty. The fix is minimal if anyone cared to backport to yakkety:

https://anonscm.debian.org/git/pkg-wine/wine.git/commit/?id=51f48d3e

https://bugs.launchpad.net/ubuntu/+source/wine/1.8.7-1ubuntu1
https://launchpad.net/ubuntu/+source/wine-development/2.0-3ubuntu1

I'm closing the dpkg task based on comment #4 (and because this was fixed in the wine packaging).