public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: eager@eagercon.com
Cc: pkoning@equallogic.com, drow@mvista.com, gcc@gcc.gnu.org,
	rock-linux@rocklinux.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Tue, 13 May 2003 19:44:00 -0000	[thread overview]
Message-ID: <20030513.214707.412778972.rene.rebe@gmx.net> (raw)
In-Reply-To: <3EC13D95.6080108@eagercon.com>

Hi,

On: Tue, 13 May 2003 11:46:45 -0700,
    Michael Eager <eager@eagercon.com> wrote:

> Thanks, but you miss my point.

Nope - it was only intended as intermediate help or starting-point for
a real FAQ.

> First off, "-C gcc" is not some important missing glue.  It isn't necessary
> and I don't specify this when building a cross compiler.

For the way we setup the cross-build this is needed for gcc-2.95.x and
gcc-3.3.x but not for gcc-3.2.x ... :-(

> Second, it looks like you build glibc using a previously created GCC.  Which

Yes.

> raises two issues:
>  (1) how do you create that version of gcc, and (2) is
> this the same version of gcc that you build later?
>  This is the classic bootstrap
> problem which appears overlooked.

Could you elaborate on the problem that appears to be overlooked?

> There are a number of scripts which describe how someone has built
> cross tools.  They don't tell how to do something different from
> what the script does, nor do the distinguish between what is necessary,
> what is ideosyncratic about an environment, and what "just happens to work".
> Like your scripts, they are terse, with few comments and no explaination.
> 
> Your scripts are interesting and I'll take a look.  But shell scripts are not a FAQ.

Sure a real up-to-date FAQ is needed.

Sincerely,
  René Rebe
    - ROCK Linux stable release maintainer

--  
René Rebe - Europe/Germany/Berlin
  rene@rocklinux.org rene.rebe@gmx.net
http://www.rocklinux.org http://www.rocklinux.org/people/rene       
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene

  reply	other threads:[~2003-05-13 19:44 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 [this message]
2003-05-13 20:34               ` Michael Eager
2003-05-13 22:14                 ` Rene Rebe
2003-05-12 17:04     ` Joseph S. Myers
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=20030513.214707.412778972.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=drow@mvista.com \
    --cc=eager@eagercon.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pkoning@equallogic.com \
    --cc=rock-linux@rocklinux.org \
    /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).