On Fri, Aug 13, 1999 at 10:42:35AM +0200, Roman Hodek wrote: > > > No. The dpkg-architecture terminology may confuse you. Here's from > > Packaging Manual 3.0.1.0 section 3.2.1 (debian/rules - the main > > building script): "... BUILD for specification of the build machine > > or HOST for specification of the machine we build for. " > > Hmm... it guess I was confused by the GNU parlance: > > build : arch of the machine we build *on* > host : arch we build the program for (i.e., on which it runs later) > target: arch for which the program runs (different from host in case > of cross-compilers or the like) > > But we don't want to cross-compile cross-compilers, I guess, so we > always have host == target.
Exactly. This simplifies things a lot. > But I see what you mean: If we consider cross-compiling of Debian > packages, some src-deps are needed for the build arch and some (libs > and -dev packages) for the host arch. > > But this obviously leads too far... But we may dream... ;) With dpkg-cross and dpkg-architecture, we are ready for proper cross-compilation setups. This will probably never happen completely, but at least where it is desireable the functionality is there. To make source-dependencies for host architecture work, we would need a cross-dpkg, which can install packages on another architecture. Currently "--root" doesn't cut it because dpkg will try to run the pre or post install/rm scripts (even with --unpack it runs at least the pre* stuff). This is less likely to become implemented, so the functionality is not yet needed. The decision to leave this out of the proposal was a wise one. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org finger brinkmd@ Marcus Brinkmann GNU http://www.gnu.org master.debian.org [EMAIL PROTECTED] for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09
