-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> sorry, I just checked in the patches I got from Jeff. Please sort out > the cross issues without me. Generally, the cross support in the GCC > packaging is there to avoid a second, third, ... source package, but > it's not the only way to build cross compilers. > > Matthias OK, I'll try not to bother you with any technical issues related to cross-compiler build. However, I hope we'll continue to use gcc source packages as the "official" way to build cross-compilers in Debian because this way seems to be the most consistent and less error-prone compared to others. A large amount of work has been done in last months to make it stable (and today it really is for most targets); and the work continues: - - right now I'm trying to make multilib targets (sparc and s390) to work correctly as cross targets; I've already committed lib64 support to dpkg-cross, and now I'm trying to find out what's wrong there at gcc side; - - there are plans to move the same cross target support to the rest two gcc source packages - gcc-2.95 and gcc-snapshot - - there are plans to enable alternative libc support for cross targets (and probably also builds of cross-compiler without target libc available - upstream supports that) - - there are plans for better intergation of cross target build procedure into gcc source packages, to avoid code duplication between native and cross targets that's currently there. Don't you object we'll try to do that? If you agree, it's probably a good idea to confirm cross-target-related patches at debian-embedded@lists.debian.org - that will help to keep the work consistent. Nikita -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA8OfisTbPknTfAB4RAnNhAJ9kzTvCd9WjCIETWcRaePsE08rj+gCfeSMu oZprbnkevHdSLUlNHbsNd+E= =SGCS -----END PGP SIGNATURE-----
