From: Ben Hutchings <ben@decadent.org.uk>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org
Cc: Liz Zhang <lizzha@microsoft.com>,
Lili Deng <v-lide@microsoft.com>,
Riku Voipio <riku.voipio@linaro.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-kernel@vger.kernel.org,
Manoj Srivastava <srivasta@debian.org>
Subject: Re: [PATCH] kbuild: add workaround for Debian make-kpkg
Date: Wed, 06 Mar 2019 20:59:28 +0000 [thread overview]
Message-ID: <bc3f60f43fc7973dfffcf63aa037439462a6ce38.camel@decadent.org.uk> (raw)
In-Reply-To: <1551888035-13329-1-git-send-email-yamada.masahiro@socionext.com>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
kernel-package is maintained by Manoj Srivastava (cc'd), not by the
Debian kernel team.
On Thu, 2019-03-07 at 01:00 +0900, Masahiro Yamada wrote:
> Since commit 3812b8c5c5d5 ("kbuild: make -r/-R effective in top
> Makefile for old Make versions"), make-kpkg is not working.
>
> make-kpkg directly includes the top Makefile of Linux kernel, and
> appends some debian_* targets.
>
> /usr/share/kernel-package/ruleset/kernel_version.mk:
>
> # Include the kernel makefile
> override dot-config := 1
> include Makefile
> dot-config := 1
>
> I did not know the kernel Makefile was used in that way, and it is
> hard to guarantee the behavior when the kernel Makefile is included
> by another Makefile from a different project.
>
> Looks like Debian Stretch stopped providing make-kpkg (except PowerPC).
kernel-package is not included in stretch at all. I'm not sure where
you're seeing it as being present on powerpc - that architecture wasn't
included in the stretch release.
> Maybe it is obsolete and being replaced with 'make deb-pkg' etc.
> but still widely used.
[...]
kernel-package is currently planned to be included in the next release,
though I'm not sure whether it should be.
There is another bug report about kernel-package with current kernel
versions <https://bugs.debian.org/890817> but I don't know whether it
has been worked around already.
Ben.
--
Ben Hutchings
friends: People who know you well, but like you anyway.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-06 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 16:00 Masahiro Yamada
2019-03-06 20:59 ` Ben Hutchings [this message]
2019-03-06 21:01 ` Ben Hutchings
2019-03-07 4:03 ` Masahiro Yamada
2019-03-07 6:36 ` Ben Hutchings
[not found] ` <CABkpOEUqJWn62VZoTA5UEnbDieiYR9y3diRQhZuOVe6hOoBNhA@mail.gmail.com>
2019-03-07 21:56 ` Ben Hutchings
2019-03-08 6:42 ` Masahiro Yamada
2019-03-09 20:32 ` Ben Hutchings
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=bc3f60f43fc7973dfffcf63aa037439462a6ce38.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizzha@microsoft.com \
--cc=michal.lkml@markovi.net \
--cc=riku.voipio@linaro.org \
--cc=srivasta@debian.org \
--cc=v-lide@microsoft.com \
--cc=yamada.masahiro@socionext.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 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®