I've just realised (making some new cross-chroots) that installing build-essential requires you to have a native toolchain installed (gcc, g++).
e.g. in etch: Depends: libc6-dev | libc-dev, gcc (>= 4:4.1.1), g++ (>= 4:4.1.1), make, dpkg-dev (>= 1.13.5) Now for cross-building that's not really what you want. I'm wondering if the right thing to do is create a crossbuild-essential package which depends on gcc-cross and g++-cross, then have our cross-packges provide gcc-cross and g++-cross? Or what happens if our cross packages provide gcc and g++ directly? It's true and it satisfies build-essential as-is, but I have a feeling that might produce some unexpected effects. Can anyone think of a reason why this wouldn't work? Opinions? Wookey -- Principal hats: Balloonz - Toby Churchill - Aleph One - Debian http://wookware.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
