PROPOSAL: Policy for obsoleting targets

[Paul Koning]

>>>>> "Peter" == Peter Barada <peter@baradas.org> writes:

 >> 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...

 Peter> I'd say that us cross-builders have generated *lots* of
 Peter> information on what we have to go through to get a toolchain
 Peter> built.  Read though the crossgcc list at
 Peter> http://sources.redhat.com/ml/crossgcc/ to get a taste.

I have... that's why I'm complaining.

This is the point -- there is no documentation, only a collection of
anecdotes, many of them years out of date.

 Peter> You'll find that everytime a release of binutils, gcc, newlib,
 Peter> glibc comes out, we have to go back and sharpen our pencils
 Peter> again and try to figure out a workaround for what's
 Peter> changed(such as the broken --without-headers in gcc-3.x).

Perhaps that's what happened -- I must have been trying to build
something that no one else tries, and since nothing follows any
pattern, none of the patterns were helpful.

	 paul