From: Robert Yang <liezhi.yang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] libunwind: don't use gold for mips
Date: Wed, 22 Apr 2015 10:27:14 +0800 [thread overview]
Message-ID: <55370702.8030101@windriver.com> (raw)
In-Reply-To: <0B9D4FD8-56E6-44B4-96E8-E283B6F12E98@gmail.com>
On 04/22/2015 10:24 AM, Khem Raj wrote:
>
>> On Apr 21, 2015, at 7:22 PM, Robert Yang <liezhi.yang@windriver.com> wrote:
>>
>> +# gold doesn't work for mips
>> +LDFLAGS_mips_append = ""
>> +LDFLAGS_mips64_append = ""
>> +LDFLAGS_mips64n32_append = ""
>>
>
> how about little-endian variants ?
Maybe we'd better set _86 _ppc and _arm one by one, please ?
// Robert
>
>
next prev parent reply other threads:[~2015-04-22 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 2:22 [PATCH 0/1] libunwind: don't use gold for mips Robert Yang
2015-04-22 2:22 ` [PATCH 1/1] " Robert Yang
2015-04-22 2:24 ` Khem Raj
2015-04-22 2:27 ` Robert Yang [this message]
2015-04-22 2:38 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2015-04-22 6:59 [PATCH 0/1 V2] " Robert Yang
2015-04-22 6:59 ` [PATCH 1/1] " Robert Yang
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=55370702.8030101@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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