All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions
Date: Fri, 2 May 2008 19:11:23 +0200	[thread overview]
Message-ID: <56cafb8cfeb954984d6e400c3de789b8@kernel.crashing.org> (raw)
In-Reply-To: <8CB3566C-F433-4457-906D-247BBB8D5505@kernel.crashing.org>

>> Why can't we link with libgcc, instead?
>
> Do you have or can you generate a ppc64 toolchain with this patch in 
> it?

I'm not sure what you mean.

I build GCC TOT toolchains sort-of daily, and build the kernel
with it (all architectures).  I don't build any 4xx config though,
maybe I should.


Segher

  reply	other threads:[~2008-05-02 17:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  8:11 [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions Kumar Gala
2008-05-02 11:54 ` Segher Boessenkool
2008-05-02 13:28   ` Kumar Gala
2008-05-02 13:37     ` Segher Boessenkool
2008-05-02 13:41       ` Kumar Gala
2008-05-02 15:20         ` Scott Wood
2008-05-02 17:15         ` Segher Boessenkool
2008-05-02 14:09   ` Kumar Gala
2008-05-02 17:11     ` Segher Boessenkool [this message]
2008-05-02 21:28       ` Kumar Gala
2008-05-02 21:40         ` David Miller
2008-05-02 21:58           ` Kumar Gala
2008-05-02 23:27           ` Benjamin Herrenschmidt
2008-05-02 23:38             ` David Miller
2008-05-03  0:06               ` Segher Boessenkool
2008-05-03  7:50               ` Benjamin Herrenschmidt
2008-05-03  7:55                 ` David Miller
2008-05-03 11:01                   ` Benjamin Herrenschmidt
2008-05-05 11:55                   ` Gabriel Paubert
2008-05-02 12:13 ` Josh Boyer
2008-05-02 13:32   ` Kumar Gala
2008-05-02 13:53     ` Josh Boyer
2008-05-02 13:59       ` Kumar Gala

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=56cafb8cfeb954984d6e400c3de789b8@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.