linuxppc-dev.lists.ozlabs.org archive mirror
 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 15:37:54 +0200	[thread overview]
Message-ID: <20862df61b024849f55dbd54de7cfb8f@kernel.crashing.org> (raw)
In-Reply-To: <BC3385F6-8403-446C-BC04-4DA811CFE96A@kernel.crashing.org>

>> Why can't we link with libgcc, instead?
>
> we possibly could, the problem is knowing the path of libgcc to link 
> with.

gcc -print-libgcc-file-name

>   This seemed easier to me than the makefile headaches to ensure that 
> we get that right.

Ah come on, make syntax is fun!


Segher

  reply	other threads:[~2008-05-02 13:38 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 [this message]
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
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=20862df61b024849f55dbd54de7cfb8f@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 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 NNTP newsgroup(s).