-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> On Fri, 2004-07-09 at 12:39, Erik Andersen wrote: > > gcc uses glibc internals when compiling libstdc++, and must be > > taught to use uClibc instead. gcc patches are available from > > uclibc.org, > > I applied those patches to gcc 3.3.4 stock and libstdc++ builds and > works fine. Applying those patches to gcc 3.3.4-debian, doesn't build, > but as I said, I haven't looked into it thoroughly yet, and I won't get > a chance to until next week (hopefully). Shouldn't we have some sort of coordination on debian cross-toolchain related works? I've just discovered that in gcc-3.3 3.3.4-3 package, some more cross-compiler-related patches have been accepted from Jeff Bailey <[EMAIL PROTECTED]>. It's great that different people contribute and bugs are getting fixed, I really appreciate bug fixes. However, I'm a bit worried that README.cross was patched to recommend a new tool (crosshurd) to create the build environment. AFAIK until this moment we preferred dpkg-cross ... IMHO we should define a common policy, which tools we are going to use and why, and which debs we wish to provide and why (which host-target combinations, which gcc versions, which libc variants, etc), and how this corresponds to other build systems such as OpenEmbedded. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA7v8XsTbPknTfAB4RAvqrAKCJwjrD6J6b+rCI18YDyvOOEhliHQCfUaWX vCjTLPpUZU957aeSDaz2qbM= =ghoF -----END PGP SIGNATURE-----
