public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: kbuild test robot <fengguang.wu@intel.com>,
	Anton Blanchard <anton@samba.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: collect2: error: ld returned 1 exit status
Date: Mon, 23 Nov 2015 20:54:53 +1100	[thread overview]
Message-ID: <1448272493.3452.4.camel@ellerman.id.au> (raw)
In-Reply-To: <201511220951.EHLYd8lw%fengguang.wu@intel.com>

On Sun, 2015-11-22 at 09:05 +0800, kbuild test robot wrote:

> Hi Anton,
> 
> FYI, the error/warning still remains.

...

>    /usr/lib/gcc-cross/powerpc64le-linux-gnu/5/../../../../powerpc64le-linux-gnu/bin/ld: arch/powerpc/kernel/vdso64/sigtramp.o: file class ELFCLASS64 incompatible with ELFCLASS32
>    /usr/lib/gcc-cross/powerpc64le-linux-gnu/5/../../../../powerpc64le-linux-gnu/bin/ld: final link failed: File in wrong format
> > > collect2: error: ld returned 1 exit status

Hi Fengguang,

How new is your GCC? This looks like a bug that was fixed recently (September) in GCC:

  https://github.com/gcc-mirror/gcc/commit/0012c439035bc1d5843e5c8e72c6c5fad357d389

cheers


  reply	other threads:[~2015-11-23  9:55 UTC|newest]

Thread overview: 30+ 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 [this message]
2015-11-23 12:45   ` Fengguang Wu
2015-11-24 20:05     ` Breno Leitao
  -- strict thread matches above, loose matches on Subject: below --
2022-01-29 21:57 kernel test robot
2022-01-25 19:17 kernel test robot
2021-09-11 19:31 kernel test robot
2021-07-20 19:27 kernel test robot
2021-07-05  2:19 kernel test robot
2021-05-31 12:45 kernel test robot
2021-05-29 19:48 kernel test robot
2021-05-16 23:06 kernel test robot
2021-04-10 19:46 kernel test robot
2021-03-07 17:24 kernel test robot
2021-03-03 21:22 kernel test robot
2019-05-31  6:18 kbuild test robot
2017-02-12  4:37 kbuild test robot
2017-01-01 19:08 kbuild test robot
2016-12-11 10:05 kbuild test robot
2016-11-20 20:39 kbuild test robot
2016-11-21 10:16 ` Linus Walleij
2016-09-11  2:06 kbuild test robot
2016-04-16 23:50 kbuild test robot
2016-04-03  0:46 kbuild test robot
2016-03-12 23:33 kbuild test robot
2016-03-05 23:34 kbuild test robot
2016-02-27 23:12 kbuild test robot
2016-01-16 23:31 kbuild test robot
2015-12-05 23:55 kbuild test robot
2015-10-10 23:32 kbuild test robot

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=1448272493.3452.4.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.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