From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Christoph Lameter <cl@linux.com>, Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [bisected] broken make-kpkg kernel build in 3.15-rc1
Date: Tue, 15 Apr 2014 20:43:19 +0100 [thread overview]
Message-ID: <20140415194319.GV24070@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.10.1404151539110.15528@vincent-weaver-1.um.maine.edu>
On Tue, Apr 15, 2014 at 03:39:47PM -0400, Vince Weaver wrote:
> On Tue, 15 Apr 2014, Russell King - ARM Linux wrote:
> >
> > Hmm, any ideas what HAVE_INST_PATH is set to? It would be good to have
> > the complete picture on this bug. :)
>
> In debian/ruleset/misc/version_vars.mk
>
> HAVE_INST_PATH =$(call doit,grep -E '\(INSTALL_PATH\)' Makefile 2>/dev/null )
Ah, so that would match on:
export INSTALL_DTBS_PATH ?= $(INSTALL_PATH)/dtbs/$(KERNELRELEASE)
^^^^^^^^^^^^^^
So it's matching on use of INSTALL_PATH not whether INSTALL_PATH has been
defined. Interesting concept. :p
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-15 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:43 Vince Weaver
2014-04-15 15:03 ` Michal Marek
2014-04-15 16:49 ` Christoph Lameter
2014-04-15 16:57 ` Michal Marek
2014-04-15 17:22 ` Christoph Lameter
2014-04-15 18:26 ` Russell King - ARM Linux
2014-04-15 19:10 ` Vince Weaver
2014-04-15 19:28 ` Vince Weaver
2014-04-15 19:30 ` Vince Weaver
2014-04-15 19:31 ` Russell King - ARM Linux
2014-04-15 19:39 ` Vince Weaver
2014-04-15 19:43 ` Russell King - ARM Linux [this message]
2014-04-15 19:56 ` Christoph Lameter
2014-04-15 19:37 ` Vince Weaver
2014-04-15 19:47 ` Christoph Lameter
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=20140415194319.GV24070@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=cl@linux.com \
--cc=grant.likely@linaro.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=robh+dt@kernel.org \
--cc=vincent.weaver@maine.edu \
/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®