This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PROPOSAL: Policy for obsoleting targets
>Finally, since it appears that no one has time or energy to document
>how crossbuilding works, would it be possible to ask cross-build
>status reporters to make available, if possible, the scripts they use?
>A pointer would be enough; copying it into the report is probably
>excessive. I'm thinking that perhaps I might be able to intuit what
>the crossbuild process is from looking at a sufficiently large sample
>of "scripts that just happen to work". What the heck, I might as well
>try, nothing else has worked...
I'd say that us cross-builders have generated *lots* of information on
what we have to go through to get a toolchain built. Read though the
crossgcc list at http://sources.redhat.com/ml/crossgcc/ to get a
taste.
You'll find that everytime a release of binutils, gcc, newlib, glibc
comes out, we have to go back and sharpen our pencils again and try to
figure out a workaround for what's changed(such as the broken
--without-headers in gcc-3.x).
--
Peter Barada
peter@baradas.org