From: Peter Zijlstra <peterz@infradead.org>
To: youling 257 <youling257@gmail.com>
Cc: viro@zeniv.linux.org.uk, jpoimboe@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: Merge branch 'core-objtool-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Date: Thu, 9 Apr 2020 09:38:07 +0200 [thread overview]
Message-ID: <20200409073807.GA2483@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAOzgRdYkJMiQM9M-UHv5Z-6CLzaV0P8YTK5Ft-CmT5-JqCnYSA@mail.gmail.com>
On Thu, Apr 09, 2020 at 10:00:53AM +0800, youling 257 wrote:
> d937a6dfc9428f470c3ce4d459c390944ddef538 caused 64bit kernel build
> failed on 32bit userspace.
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d937a6dfc9428f470c3ce4d459c390944ddef538
>
> 2020-04-08 16:13 GMT+08:00, youling 257 <youling257@gmail.com>:
> > after this merge branch, build 64bit kernel failed on 32bit userspace.
> >
> >
> > CC tools/objtool/builtin-check.o
> > CC tools/objtool/builtin-orc.o
> > In file included from check.h:10,
> > from builtin-check.c:18:
> > elf.h: In function ‘sec_offset_hash’:
> > elf.h:102:14: error: right shift count >= width of type
> > [-Werror=shift-count-overflow]
> > 102 | oh = offset >> 32;
> > | ^~
Oh right; I figured it wouldn't matter since we don't do objtool for
32bit kernels, but I suppose you're cross building a 64bit kernel on a
32bit host or something daft like that?
I'll go fix it.
next prev parent reply other threads:[~2020-04-09 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOzgRdbWsKY7mXgiTx3um_gdJvgPN1O2p1vxmWv9eApQAy9UzQ@mail.gmail.com>
2020-04-09 2:00 ` Merge branch 'core-objtool-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip youling 257
2020-04-09 7:38 ` Peter Zijlstra [this message]
2020-04-11 17:30 ` youling 257
2020-04-20 5:37 ` youling 257
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=20200409073807.GA2483@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=youling257@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.