public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Ruottu <karuottu@mbnet.fi>
To: Duft Markus <Markus.Duft@salomon.at>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Cross GCC and Sysroot
Date: Fri, 16 Mar 2007 15:20:00 -0000	[thread overview]
Message-ID: <45FAA186.4070207@mbnet.fi> (raw)
In-Reply-To: <18597F2B47F1394A9B309945EC724112D0B361@servex01.wamas.com>

Duft Markus kirjoitti:
> Hi!
>
> I'm working on getting a compiler-farm up, that can cross compile to
> multiple platforms. It's allready almost done, but there are some small
> problems left over.
>
> Since the Compiler-Farm will only compile (no preprocessing, no linking,
> etc.) because of usage of DISTCC, i wanted to ask if there is a way to
> build binutils/gcc in a way that there are only the really necessary
> parts (as, gcc, g++) without support for linking and other unwanted
> stuff.
>   
 Just leave the build when it stops!  It stops when trying libgcc, so if 
you don't link,
where you will need libgcc?
> The second problem is, how to find out what to put in the sysroot
> packages used to bootstrap the crossc ompilers for each platform. At the
> moment this is a really annoying manual process of sorting out and
> tar'ing together /usr/include and /usr/lib with some additional
> softlinks. Is there a somewhat short list of files i need for this
> purpose?
>   
 You  don't need anything for the $target system...
> The sysroot package is used only for bootstrapping gcc, since everything
> that the cross-gcc will see is preprocessed allready.
>   
 No 'bootstrap' required either...

 In a nutshell: Building GCC binaries requires ONLY the $host GCC !  
Nothing for
the $target !  Producing anything for the $target WITH the new GCC then 
can require
quite a lot $target stuff !

  reply	other threads:[~2007-03-16 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 13:49 Duft Markus
2007-03-16 15:20 ` Kai Ruottu [this message]
2007-03-16 17:24 Duft Markus
2007-03-19 10:17 Duft Markus

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=45FAA186.4070207@mbnet.fi \
    --to=karuottu@mbnet.fi \
    --cc=Markus.Duft@salomon.at \
    --cc=gcc-help@gcc.gnu.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).