Re: New CrossGCC FAQ maintainer needed?

[Scott Howard <scott at sthoward dot com>]

When I inherited the FAQ, I did update much of the information, but I
did not perform the overhaul to the basic structure that I felt it
needed to make it more useful. Maybe that time has come.

I haven't touched the FAQ in almost two years - got busy with other
things and lost interest I guess. If there are folks out there who have
an interest in maintaining it, I'd be more than happy to turn it over to
them.

The original document was done in Lyx, and translated to text, HTML,
Postscript etc. using the Linux SGML tools. If you want the source, I'll
dig it out and post it to the list.

Regards,

Scott

Steve deRosier wrote:
> 
> Hey,  I wrote some stuff dealing with making an CrossGCC for my specific
> project.  I think there may be some valuable notes in here for a rewrite of
> the FAQ.  Basically this stuff is wisdom that I had to learn on my own or
> glean from various sources (BTW - a thank you to all on this list, the
> binutils list and the coldfire list that helped with questions). I've
> excerpted the more general parts from my document and am attaching the html.
> If it helps any, then great.
> 
> - Steve
> 
> ----------
> >From: David Korn <dkorn@pixelpower.com>
> >To: crossgcc@sources.redhat.com
> >Subject: RE: New CrossGCC FAQ maintainer needed?
> >Date: Wed, Mar 21, 2001, 10:30 AM
> >
> 
> >>bgat@open-widgets.com wrote:
> >>
> >>> Guys:
> >>>
> >>> I'm not one to stick my head in and volunteer where I'm not wanted,
> >>> but...  Does the CrossGCC FAQ need a maintainer?  I'd be happy to
> >>> volunteer if so.
> >
> >>From: Stephen Smith [mailto:ischis2@home.com]
> >>
> >>If you do, be sure to get the newest howto from Mumit.  He
> >>helped me out recently and then posted a howto on his site.
> >>
> >>I know that the official Cross GCC FAQ was a disaster for me.
> >
> >   I second this.  The cross gcc FAQ is now so out-of-date it's a
> > liability; an awful lot of the questions on this list are from people
> > who have followed the procedures in the FAQ and run up against problems
> > that it makes no mention of.  For example, a section on target headers is
> > much needed; and perhaps a bit about the dangers of line ends when
> > building under cygwin.
> >
> >   If you're serious about this, I've got some bits of documentation on
> > my website that could make the basis for some new answers in the FAQ;
> > I'll post them to the list sometime in the next few days (my time is
> > quite busy at the moment) and we can collectively start bashing an
> > updated FAQ into shape.
> >
> >   Stephen, can you post the URL of Mumit's HOWTO, please?
> >
> >        DaveK
> > --
> >  All your base are belong to us!
> >
> >
> > **********************************************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please notify
> > the system manager.
> >
> > This footnote also confirms that this email message has been swept by
> > MIMEsweeper for the presence of computer viruses.
> >
> > www.mimesweeper.com
> > **********************************************************************
> >
> > ------
> > Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> > Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
> 
>   ------------------------------------------------------------------------
>                         Name: XGCC_excerpt.html
>    XGCC_excerpt.html    Type: Plain Text (text/plain)
>                     Encoding: base64
> 
>   ------------------------------------------------------------------------
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com