public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Cc: "Frank W. Miller" <fwmiller@cornfed.com>
Subject: Re: Building cross compiler for x86_64
Date: Sun, 17 Feb 2008 02:55:00 -0000	[thread overview]
Message-ID: <b609cb3b0802161855p4168db79n323fd7b9fac4ab97@mail.gmail.com> (raw)
In-Reply-To: <47B7A14F.690D0B0@dessent.net>

On Feb 16, 2008 9:51 PM, Brian Dessent <brian@dessent.net> wrote:
> ... like I said, you can't build libgcc without target libc headers.  I
> don't know why the all-gcc rule still tries to build parts of libgcc.

What parts does it try to build?

  reply	other threads:[~2008-02-17  2:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 17:14 Forward declaration of classes needed when using GCJ? Andrew W
2008-02-11 17:50 ` David Daney
     [not found]   ` <47B098D1.1050200@iee.org>
2008-02-11 18:58     ` David Daney
2008-02-11 21:56   ` Andrew W
2008-02-11 22:37     ` David Daney
2008-02-12 16:02       ` Andrew W
2008-02-12 17:48         ` Andrew Haley
2008-02-15 18:24         ` Andrew W
2008-02-15 18:31           ` Building cross compiler for x86_64 Frank W. Miller
2008-02-16  0:00             ` Brian Dessent
2008-02-16  0:14               ` Frank W. Miller
2008-02-16  0:33                 ` Brian Dessent
2008-02-16 20:06             ` Frank W. Miller
2008-02-17  2:52               ` Brian Dessent
2008-02-17  2:55                 ` NightStrike [this message]
2008-02-18  4:39                   ` Frank W. Miller
2008-02-15 19:51           ` Forward declaration of classes needed when using GCJ? Andrew Haley

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=b609cb3b0802161855p4168db79n323fd7b9fac4ab97@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=fwmiller@cornfed.com \
    --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).