[lkml]   [2014]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [bisected] broken make-kpkg kernel build in 3.15-rc1
On Tue, 15 Apr 2014, Vince Weaver wrote:

> On Tue, 15 Apr 2014, Russell King - ARM Linux wrote:
> > Right, so the thing to do is to run a build with the commit applied,
> > without any -j arguments and V=1, logging the output (so that predictable
> > output can be generated).
> >
> > Then run the same thing with the commit reverted, again logging it. Then
> > diff the two and see what's different.
> OK, I captured the output. No diffs, as of course reverting things
> means one kernel was called 3.15-rc1 and one 3.15-rc1+ which meant more or
> less every line changed.
> It seems that on stock 3.15-rc1 (which fails to build) after running
> depmod it kicks into
> restore_upstream_debianization
> which goes down a path which causes the file permission failures
> Wheras 3.15-rc1 with the problem commit reverted this doesn't happen.
> This is a really weird bug, I've tried reverting individual hunks of the
> problem commit manually and it is not clear at all to me what is
> triggering this.

OK, in debian/ we have this:

ifeq ($(strip $(HAVE_INST_PATH)),)
test ! -f || cp \
test ! -f || chmod 644 \
cp $(kimagesrc) $(kimagedest)

So in the good case it goes down the if, in the bad case down the else.

I'm assuming that the ($(strip $(HAVE_INST_PATH)),) is being confused by
the INSTALL_DTBS_PATH introduced by the changeset.

So I guess that makes this a debian bug?


 \ /
  Last update: 2014-04-15 22:01    [W:0.060 / U:3.576 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site