On Wed, Aug 26, 2015 at 01:52:25PM -0700, Ryan Tandy wrote: > We can drop libperl-dev if we disable slapd, but perl (the interpreter) is > still used in a couple of places in debian/rules. But that should be OK for > your cross build because you can use the host's perl, right?
I see you are getting the details right from the start. Awesome. The Build-Depends of openldap are currently cross-unsatisfiable regardless of whether you are in a bootstrap setting or not. The technical reason is that you depend on the host architecture perl, but essential depends on the build architecture perl and perl is not coinstallable with itself. The non-technical explanation is that you want to execute perl and thus should be depending on the build architecture perl, which is generally available during a cross build. To do that you mark it as "perl:native". The archive support for ":native" is still not known to work in all places, so I skipped that part in my patch. Since perl is "M-A:allowed" you can achieve the same effect by saying "perl:any" and have it work today. I note that you seem to be using "host's perl" with a (Mozilla'ish) terminology that differs from the GNU terminology. I generally use the terminology from "man dpkg-architecture" section "TERMS". All other Build-Depends should be ready for crossing unless I am getting things wrong again. TL;DR: perl (not libperl-dev) is always available for cross builds even in a bootstrap setting. It just needs to be written as "perl:any" (or "perl:native" in a not so distant future). Helmut
