Re: cross-compiling Debian packages

Eric Cooper wrote: Also, would you welcome patches that add the ability to handle packages built with alternative libc implementations, namely uClibc, Dietlibc and Newlib? Shall I file a "bug" report? In the meantime, can you make these available somewhere? (I'm interested in using dpkg-c

question on hurd-i386 Debian architecture

Dear DDs, Can anyone please explain why this architecture is named hurd-i386 rather that i386-hurd? Is there any rule that says that the OS name should come before CPU name? Pjotr Kourzanov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAI

Re: cross-compiling Debian packages

Nikita V. Youshchenko wrote: I have devoted some time cross-compiling a number of essential packages, with glibc-based, uclibc-based and dietlibc-based ARM and MIPS toolchains and found all of that not a huge problem at all, given that "debian/rules" is provisioned with proper calls to --host (a

Re: "but ./configure makes it look so easy", or why cross compiling isn't always trivial

Peter Samuelson wrote: [Peter Kourzanov] For most of the packages, what is so different in cross-compilation in comparison to native? Whether or not 'configure' believes it can use tests of the form "try compiling and running this little program to see what it does&qu

Re: ./configure in debian/rules

Henrique de Moraes Holschuh wrote: On Thu, 09 Mar 2006, Hendrik Sattler wrote: `--host=HOST-TYPE' the type of system on which the package will run. By default it is the same as the build machine. Specifying it enables the cross-compilation mode. That's insane. However, i

Re: ./configure in debian/rules

Hendrik Sattler wrote: Am Donnerstag, 9. März 2006 03:12 schrieb Russ Allbery: Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: I'm one of the people who actually helped design the GNU Makefile and configure standards, and --host does not "signal that you're cross-compiling." What sign

cross-compiling Debian packages

Hi everyone! To continue the "./configure in debian/rules" thread... Can anyone tell me what is the factual difference between a cross- and a native-build? I am aware only of an obvious limitation that a cross package build system can not rely on the cross-compiled binaries generated in the pr

Re: ./configure in debian/rules

Russ Allbery wrote: Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: I'm one of the people who actually helped design the GNU Makefile and configure standards, and --host does not "signal that you're cross-compiling." What signals that you are cross-compiling is a disagreement between --hos