I need examples of packages which, when cross-built, depend on a native (i.e build architecture) library package at build-time. That would be because they build a tool which is used during the build, but is not shipped in the package, and that tool needs a library that is not in build-essential to build.
(It's not a problem if the tool ends up in the final package, because then that package can be build-depended on to get the tool.) This is the case which the build-depends: package:native syntax is intended to cover. I suspect such things exist but I've been told that we should find at least one example of this actually occuring in the archive before putting functionality to cater for this in the multiarch spec. The background to this is in https://wiki.ubuntu.com/MultiarchCross which describes additions to the https://wiki.ubuntu.com/MultiarchSpec (the spec as currently being implemented), in order to cater for cross-building. This bug is also very relevant and puts things succinctly: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558095 So, examples welcome. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
