On 28.11.2016 20:00, Mark Brown wrote: > On Sun, Nov 27, 2016 at 06:39:22PM +0200, Sami Liedes wrote: > >> It seems to me that Mark is saying that this is not even supposed to >> work with lib32z1-dev installed, but rather you should have >> zlib1g-dev:i386 installed (and not doing so is user error). > > Right, that's now the expected way for users to get an i386 version on > amd64.
... which doesn't help building packages on the buildds. >> I found this surprising (and wonder what lib32z1-dev is actually for >> then), but as I don't know how these packages are supposed to work, I >> won't take a position. I am happy enough that I got things working by >> installing zlib1g-dev:i386. > > In the past before Debian supported coinstallation of packages from > multiple architectures on one system (multiarch) some packages like zlib > were built specially to provide binaries for one architecture in > packages for another architecture (so lib32z1 is a 32 bit version of > zlib built as a package for a 64 bit architecture for example). This > was called multilib and the goal has been to phase it out in favour of > using multiarch. sure, but that goal isn't yet reached. > It appears that there have been changes in the toolchain that mean that > broke the multilib packages (I'm guessing that it was some of the > multiarch implementation) but given the availability of multiarch which > supports all libraries rather than just ones that have been specially > built people should be using that instead. There are some cases where > the infrastructure isn't able to cope yet which may be what's going on > here but they definitely don't apply to end users. the only thing that happened is that libgphobos is now built as a shared runtime library, depending on libz. Matthias
