This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PROPOSAL: Policy for obsoleting targets
- From: Michael S. Zick <mszick at goquest dot com>
- To: Joe Buck <jbuck at synopsys dot com>,Alexandre Oliva <aoliva at redhat dot com>
- Cc: Joel Sherrill <joel dot sherrill at OARcorp dot com>,Paul Koning <pkoning at equallogic dot com>,janis187 at us dot ibm dot com,pbarada at mail dot wm dot sps dot mot dot com,zack at codesourcery dot com,gcc at gcc dot gnu dot org
- Date: Mon, 19 May 2003 17:37:47 -0500
- Subject: Re: PROPOSAL: Policy for obsoleting targets
- References: <874r3u27sm.fsf@egil.codesourcery.com> <oru1buld3w.fsf@free.redhat.lsd.ic.unicamp.br> <20030516165454.B12185@synopsys.com>
On Friday 16 May 2003 06:54 pm, Joe Buck wrote:
> On Fri, May 16, 2003 at 07:51:15PM -0300, Alexandre Oliva wrote:
> > On May 16, 2003, Joel Sherrill <joel.sherrill@OARcorp.com> wrote:
> > > The problem with cross build is that there is really no generic
> > > "build a cross compiler" procedure.
> >
> > Excellent point.
> >
> > > No one person is skilled in all those types of cross builds. I have
> > > done about 4 of them in the past year. If GCC is to have good cross
> > > building instructions, then my proposal would be to divide the
> > > instructions into categories based upon the above patterns and any
> > > others that people can identify.
> >
> > Agreed on all counts. You seem to have a great starting point.
>
> So, suppose we start a web page with Joel's categories as headings, and
> then let people fill in sections for instructions in places where they
> know the answer? We'll wind up with missing sections, but at least we'll
> have something to point people to.
>
Perhaps establishing a Wiki would be the answer here.
It is such a diverse subject (cross-building) with many people having just
the bits and pieces that work for them; it sounds like an ideal subject for
a Wiki.