[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWqdi=7hsXTx=WKf-=He-9GP-WNLXppijeZgcoZDCq=bg@mail.gmail.com>
Date: Mon, 18 Jul 2016 13:04:34 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: [PATCH/RFC] Re: linux-next: build failure after merge of the
luto-misc tree
On Sun, Jul 17, 2016 at 10:18 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Arnaldo,
>
> On Fri, 15 Jul 2016 12:43:26 -0300 Arnaldo Carvalho de Melo <acme@...hat.com> wrote:
>>
>> Ok, same results, it works, queuing this one, ack? Stephen, does it work
>> for you?
>
> Sorry, no. See my other email.
>
> I am cross building (if that makes a difference).
I wonder if something's wrong with the way that hostprogs-y works if
the program includes kernel headers.
It's plausible that something like this:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/commit/?h=x86/vdso&id=424eb7848324efbfcffaf58b142db1a455a9628b
coupled with a change to make vdso2c or, more generally, hostprogs-y
use USERINCLUDE would help.
--Andy
Powered by blists - more mailing lists