On Tue, Aug 30, 2016 at 07:53:05PM +0200, Helmut Grohne wrote: > Package: libtool-bin > Version: 2.4.2-1.11 > User: helm...@debian.org > Usertags: rebootstrap > > libtool-bin requires a compiler for proper operation. In earlier times, > there was only the libtool binary package, which still depends on gcc | > c-compiler. Then we split out /usr/bin/libtool to libtool-bin and had it > depend on libtool thus inheriting all dependencies, at least we thought. > What we forgot is that libtool became Multi-Arch: foreign. Thus > installing libtool-bin:arch1 with gcc:arch2 is considered ok. > Unfortunately that doesn't work well as /usr/bin/libtool expects > gcc/g++/ld to match its own architecture. > > The trivial solution to this problem is adding an explicit dependency on > gcc | c-compiler to libtool-bin. > > I note though that after adding that dependency, libtool-bin will > effectively become unusable to cross building, because its gcc:hostarch > dependency will not be satisfiable. In a distant future, we want it to > depend on gcc-for-host instead and thus allow cross compilers to be > used. Until that becomes reality, the dependency on gcc will remind us > that cross building anything that Build-Depends on libtool-bin will be a > fruitless exercise.
We actually have 67 packages that build-depend on libtool-bin? Really nothing should be build-depending on that. I consider it a bug that anything uses it. That should generate libtool by running configure. And that libtool is configured for the arch of the package, it's not usable for any other arch. Kurt
