> If it said "No shlibs information", then *that* would be a known bug in > ia32-libs, and known to be the current reason for Wine to FTBFS on the > amd64 build daemons. (I'm not sure I understand what you say.) There isn't any amd64 build daemon for Wine at this time: "Dep-Wait: ia32-libs (>> 2.2)" because of libxml2 (#458013 & #456914). On my PC, I edited /var/lib/dpkg/info/ia32-libs.shlibs manually in order to build wine myself.
> But your error looks more like a problem that dpkg-shlibdeps used to > only treat as a warning, not an error. Does the build actually stop > there, and not because of some other error? Yes it stops there. Since I don't need libwine-ldap : 1. I added a 'bash -i' line before and after: dh_shlibdeps -s -Llibwine -ldebian/libwine/usr/lib' 2. before dh_shlibdeps, I did: $ mv debian/libwine-ldap/usr/lib/wine/wldap32.dll.so .. 3. after: $ mv ../wldap32.dll.so debian/libwine-ldap/usr/lib/wine/ (Finally, I got a libwine-ldap_0.9.54-1_amd64.deb package without any dependency.) > If so, what if you delete debian/amd64.tar.lzma.uu from the unpacked > sources before building? That would build a Wine that only uses the > 32-bit libraries that are actually available in ia32-libs (but might > still fail due to "No shlibs information"...) Oops. Not tried, and I should redownload the source package to test. I've already upgraded Wine to 0.9.54-1. Tell me if this test would be useful to you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
