public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: pkoning@equallogic.com
Cc: drow@mvista.com, gcc@gcc.gnu.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Mon, 12 May 2003 19:24:00 -0000	[thread overview]
Message-ID: <20030512.212240.893778964.rene.rebe@gmx.net> (raw)
In-Reply-To: <16063.53985.772832.598267@pkoning.dev.equallogic.com>

Hi,

On: Mon, 12 May 2003 12:59:13 -0400,
    Paul Koning <pkoning@equallogic.com> wrote:

>  Rene> (Is it intentional that the GCC install instructions point to
>  Rene> the rather old "Version: 1.01, Last Updated December 3, 1999"
>  Rene> CrossGCC/FAQ ? Maybe some more recent info should be included
>  Rene> in the install document ...)
> 
> Indeed.  It would be even better if they actually worked.  I have
> never seen ones that work.  The closest I have come is procedures that
> result in a build process that aborts at some point, but gets far
> enough to produce a compiler that appears to function.

In ROCK Linux we always had working cross-compile functionality since
we support cross build (of selected packages). We even do build a
"pseudo" cross compile for native builds (e.g. to have a clean
compiler for the real gcc build - and for system that have an old gcc
and the new glibc-2.3 is selected to build).

We had this code:

        if [ "$pkg" = "gcc2" ] ; then
                make -C gcc all LANGUAGES="c"
                make -C gcc install LANGUAGES="c"
        else
                make all
                make install
        fi

Which I now changed to:

        if [ "$pkg" = "gcc2" ] ; then
                make -C gcc all LANGUAGES="c"
                make -C gcc install LANGUAGES="c"
        else
                make -C gcc all
                make -C gcc install
        fi

And this seems to work for the 3.3-prerelease. I still need to test if
this still works for the current stable 3.2.x branch ...

You can browse it online at:

http://schillernet.dyndns.org/svn/rock-linux/rock-trunk/package/base/gcc3/gcc3.conf

>        paul

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-12 19:24 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 [this message]
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
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=20030512.212240.893778964.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pkoning@equallogic.com \
    /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).