Helmut Grohne <hel...@subdivi.de> writes:
> Note that python3 is used > as a code generator, so rather than a host architecture python3 a build > architecture python3 is needed. To achieve that, it should be annotated > :native or :any. Sounds reasonable. > Once that has changed, one can actually attempt a cross build. That > attempt quickly ends due to not finding ncurses, because it didn't do > a cross build. The relevant --build and --host flags are missing from > configure. Is there a reason for not using dh_auto_configure? No idea now, sorry. I think this stuff was contributed by others. Probably legacy reasons now. > It would automatically pass them as needed. Once > added, the build progresses quite far until it fails finding > asn1_compile. The build system is clever enough to recognize that it > cannot run the built asn1_compile and tries running the system copy > instead, which isn't there. Unfortunately, asn1_compile does not reside > in a Multi-Arch: foreign package and thus is not readily available. I > propose splitting it out of heimdal-multidev into a heimdal-multidev-bin > package that contains architecture-independent tools. Once done, we can > depend on it (for cross compilation only to avoid a recursive > depdendency in native builds). Are you ok with such a split? We have > quite some prior art for this if you look for other packages matching > the pattern "*-bin", especially in the qt/kde ecosystem. I'm attaching a > patch for your convenience. When I tried to build this with my build system I get: $ apt-get-build-depends --yes Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package heimdal-multidev-bin E: Unable to locate package <cross> Is "heimdal-multidev-bin <cross>," correct syntax? If so, maybe apt-get-build-depends doesn't support it. -- Brian May <b...@debian.org>
