From: Breno Leitao <brenohl@br.ibm.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Anton Blanchard <anton@samba.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: Re: collect2: error: ld returned 1 exit status
Date: Tue, 24 Nov 2015 18:05:10 -0200 [thread overview]
Message-ID: <5654C2F6.10401@br.ibm.com> (raw)
In-Reply-To: <20151123124518.GA22401@wfg-t540p.sh.intel.com>
Hi Fengguang,
On 11/23/2015 10:45 AM, Fengguang Wu wrote:
> I'm using Debian's cross gcc 5.2.1:
>
> gcc-powerpc64le-linux-gnu 5.2.1-14+really5.2.1-13
>
> It may take some time for debian to catchup up with the newer version.
I already opened a Debian bug to track the backport of this fix into
Debian's GCC 5.2.1.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806160
prev parent reply other threads:[~2015-11-24 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 1:05 collect2: error: ld returned 1 exit status kbuild test robot
2015-11-23 9:54 ` Michael Ellerman
2015-11-23 12:45 ` Fengguang Wu
2015-11-24 20:05 ` Breno Leitao [this message]
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=5654C2F6.10401@br.ibm.com \
--to=brenohl@br.ibm.com \
--cc=anton@samba.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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).