[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160921120226.5466c5b2@canb.auug.org.au>
Date: Wed, 21 Sep 2016 12:02:26 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
<bauerman@...ux.vnet.ibm.com>
Subject: Re: linux-next: build failure after merge of the akpm-current tree
Hi Michael,
On Wed, 21 Sep 2016 10:27:46 +1000 Michael Ellerman <mpe@...erman.id.au> wrote:
>
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
>
> > On Tue, 20 Sep 2016 22:00:32 +1000 Michael Ellerman <mpe@...erman.id.au> wrote:
> >>
> >> Ah yep looks like that's the problem, patch below should fix it?
> >
> > Yeah, I am just going to (logically) run "sed 's/CONFIG_WORD_SIZE/BITS/'"
> > over the tree during the merge of the apm-current tree today.
> >
> >> I think I'd actually prefer it if purgatory didn't redefine the CFLAGS
> >> from scratch, so I'll see if Thiago can do that and send a new version.
> >
> > That could be better, but there are still some additions of
> > CONFIG_WORD_SIZE elsewhere :-(
>
> I don't see any others in yesterday's next?
I fixed the other one I found as it caused a build failure as well but
was more obvious (and I had had time to think about what was happening).
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists