From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <ben@decadent.org.uk>
Cc: <yamada.masahiro@socionext.com>, <isar-users@googlegroups.com>,
<michal.lkml@markovi.net>, <linux-kbuild@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <riku.voipio@linaro.org>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH v3 0/1] builddeb: generate multi-arch friendly linux-libc-dev
Date: Thu, 4 Jul 2019 22:50:26 +0200 [thread overview]
Message-ID: <1562273427-204-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <432e997617a0669886cd9ea5ceac7c1a2173044b.camel@decadent.org.uk>
Changes in v3:
- add Multi-Arch: same to debian/control for linux-libc-dev
Changes in v2:
- forward $debarch from mkdebian to builddeb
- use dpkg-architecture -qDEB_HOST_MULTIARCH instead of $CC -dumpmachine
Cedric Hombourger (1):
builddeb: generate multi-arch friendly linux-libc-dev package
scripts/package/builddeb | 8 ++++++++
scripts/package/mkdebian | 5 +++--
2 files changed, 11 insertions(+), 2 deletions(-)
--
2.11.0
next prev parent reply other threads:[~2019-07-04 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 6:14 [PATCH] builddeb: generate multi-arch friendly linux-libc-dev package Cedric Hombourger
2019-07-04 0:43 ` Masahiro Yamada
2019-07-04 12:39 ` Cedric Hombourger
2019-07-04 13:10 ` Ben Hutchings
2019-07-04 19:42 ` [PATCH v2] " Cedric Hombourger
2019-07-04 19:49 ` Ben Hutchings
2019-07-04 20:28 ` Cedric Hombourger
2019-07-04 20:50 ` Cedric Hombourger [this message]
2019-07-04 20:50 ` [PATCH v3 1/1] " Cedric Hombourger
2019-07-07 8:58 ` Masahiro Yamada
2019-07-09 7:43 ` [PATCH v4 0/1] builddeb: generate multi-arch friendly linux-libc-dev Cedric Hombourger
2019-07-09 7:43 ` [PATCH v4] builddeb: generate multi-arch friendly linux-libc-dev package Cedric Hombourger
2019-07-09 10:20 ` Enrico Weigelt, metux IT consult
2019-07-11 14:46 ` Masahiro Yamada
2019-07-14 7:49 ` Cedric Hombourger
2019-07-17 5:47 ` Henning Schild
2019-07-20 20:16 ` chombourger
2019-09-02 17:40 ` Jan Kiszka
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=1562273427-204-1-git-send-email-Cedric_Hombourger@mentor.com \
--to=cedric_hombourger@mentor.com \
--cc=ben@decadent.org.uk \
--cc=isar-users@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=riku.voipio@linaro.org \
--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