mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build failure in -next due to 'sh: thin archives fix linking'
Date: Wed, 28 Jun 2017 07:02:02 -0700	[thread overview]
Message-ID: <4a610d3a-76de-7fec-40dc-61ec5ef175ee@roeck-us.net> (raw)
In-Reply-To: <20170628225837.25abba1e@roar.ozlabs.ibm.com>

On 06/28/2017 05:58 AM, Nicholas Piggin wrote:
> On Wed, 28 Jun 2017 05:38:50 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
> 
>> Hi,
>>
>> I see the following build error in -next when building sh:rts7751r2dplus_defconfig.
>>
>> sh4-linux-ld: arch/sh/kernel/vsyscall/vsyscall-dummy.o: compiled for a big endian system and target is little endian
>> sh4-linux-ld: arch/sh/kernel/vsyscall/vsyscall-dummy.o: uses instructions which are incompatible with instructions used in previous modules
>> sh4-linux-ld: failed to merge target specific data of file arch/sh/kernel/vsyscall/vsyscall-dummy.o
>> make[2]: *** [arch/sh/kernel/vsyscall/vsyscall-syms.o] Error 1
>>
>> Bisect points to 'sh: thin archives fix linking' as the culprit. Bisect log is attached.
>> I tried with gcc 4.8.3 and 6.3.0, both built with buildroot for sh4eb.
> 
> Thanks for the report. In arch/sh/kernel/vsyscall/Makefile, the line:
> 
>   cmd_syscall_syms = $(LD) -r -o $@ -R $<
> 
> Can you try adding $(LDFLAGS), e.g. change it to:
> 
>   cmd_syscall_syms = $(LD) $(LDFLAGS) -r -o $@ -R $<
> 

That fixes the problem (including the missing symbols seen after reverting the offending patch).

Thanks,
Guenter

  reply	other threads:[~2017-06-28 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 12:38 Guenter Roeck
2017-06-28 12:58 ` Nicholas Piggin
2017-06-28 14:02   ` Guenter Roeck [this message]
2017-06-29 15:36     ` Masahiro Yamada
2017-06-29 16:58       ` Nicholas Piggin

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=4a610d3a-76de-7fec-40dc-61ec5ef175ee@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®