From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: drow@mvista.com, gcc@gcc.gnu.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Mon, 12 May 2003 17:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305121802280.28692@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20030512.185423.115908471.rene.rebe@gmx.net>
On Mon, 12 May 2003, Rene Rebe wrote:
> Well nice that the cross-build instructions change between every major
> release (and sometimes between minors ...). What are the current
> instructions?
>
> (Is it intentional that the GCC install instructions point to the
> rather old "Version: 1.01, Last Updated December 3, 1999" CrossGCC/FAQ
> ? Maybe some more recent info should be included in the install
> document ...)
About fifteen requests for a volunteer with relevant expertise to overhaul
the documentation on building cross compilers produced just one volunteer
who didn't follow up, and no improvements to the documentation. The
relevant PR for the lack of this documentation is other/5301.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2003-05-12 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 12:00 Rene Rebe
2003-05-12 14:22 ` Daniel Jacobowitz
2003-05-12 16:51 ` Rene Rebe
2003-05-12 16:59 ` Paul Koning
2003-05-12 19:24 ` Rene Rebe
2003-11-05 14:12 ` Rene Rebe
2003-05-13 15:46 ` Michael Eager
2003-05-13 16:07 ` Rene Rebe
2003-05-13 18:56 ` Michael Eager
2003-05-13 19:44 ` Rene Rebe
2003-05-13 20:34 ` Michael Eager
2003-05-13 22:14 ` Rene Rebe
2003-05-12 17:04 ` Joseph S. Myers [this message]
2003-05-12 17:13 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0305121802280.28692@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=rene.rebe@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).