Re: Shrinking install/specific.html

[Dara Hazeghi <dhazeghi at yahoo dot com>]

--- "Joseph S. Myers" <jsm@polyomino.org.uk> wrote:
> There is a table of contents so that people can
> ignore everything not
> related to their platform.  So where's the problem
> in length?  (I actually
> think this is the right place to list all target
> triples and identify what
> they mean, even absent any special information about
> them.)

Right. I agree on that account (would be even nice if
all the targets referenced would build). However,
individual notes tend to be somewhat lengthy, enough
so that I am hesitant to respond to typical questions
with "read install/specific.html section for xxx
platform" for fear that they'll miss the information
they need. Perhaps I am overly concerned on that
account.

Also, I wonder if it's necessary to mention much about
requirements for building older versions of gcc, since
we generally don't encourage that, and it adds caveats
to build procedures and so forth.

> 
> 
> As far as I know, systems for which support has been
> removed have been
> removed from this file.  You could reduce the length
> a bit by establishing
> a general minimum binutils version when GNU binutils
> is used, adding a
> corresponding configure check for it, putting this
> in the list of
> prerequisites, and removing mention of older
> binutils versions from
> specific targets.

That sounds like a good proposal. Umm... Given that
some platforms require binutils, some support it, and
some don't, I'm wondering how cleanly one can setup
such a check.

Dara

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree