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:15:26 +0200 [thread overview]
Message-ID: <fc168238292deeec4612f9fe5ad3e03f@kernel.crashing.org> (raw)
In-Reply-To: <68FE3962-84B3-4A5A-A64A-3FD1B7F6B4E3@kernel.crashing.org>
>> gcc -print-libgcc-file-name
>
> It wasn't clear if we used a multilib toolchain if we always get the
> proper libgcc since we are building bootwrappers for all kinda of
> variants. (e500, 40x, 6xx, etc.).
gcc -mthe-options-to-select-some-target -print-libgcc-file-name
> My patch seemed the least painful solution to me.
In the short term, perhaps ;-)
> I assume there is a reason we don't link libgcc w/the kernel.
It's historical, even _if_ there was a valid reason once (and I'm
not so sure about that), who knows if there still is.
Besides, this is not the kernel, this is the bootwrapper, I strongly
doubt libgcc would cause any conflicts here.
Segher
next prev parent reply other threads:[~2008-05-02 17:15 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 [this message]
2008-05-02 14:09 ` Kumar Gala
2008-05-02 17:11 ` Segher Boessenkool
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=fc168238292deeec4612f9fe5ad3e03f@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.