From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
yamada.masahiro@socionext.com
Cc: ben@decadent.org.uk, isar-users@googlegroups.com,
michal.lkml@markovi.net, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, riku.voipio@linaro.org
Subject: Re: [PATCH v4] builddeb: generate multi-arch friendly linux-libc-dev package
Date: Tue, 9 Jul 2019 12:20:43 +0200 [thread overview]
Message-ID: <37f96102-34bf-db52-720a-d8c83965f8dc@metux.net> (raw)
In-Reply-To: <1562658215-186-2-git-send-email-Cedric_Hombourger@mentor.com>
On 09.07.19 09:43, Cedric Hombourger wrote:
> Debian-based distributions place libc header files in a machine
> specific directory (/usr/include/<libc-machine>) instead of
> /usr/include/asm to support installation of the linux-libc-dev
> package from multiple architectures. Move headers installed by
> "make headers_install" accordingly using Debian's tuple from
> dpkg-architecture (stored in debian/arch).
Is it correct the packages currently are not multiarch-compatible ?
If so, your patch would be another step towards completely replacing
the downstream's utterly complex build process :)
I'll give it some test cycles.
thx.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-07-09 10:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 6:14 [PATCH] " 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 ` [PATCH v3 0/1] builddeb: generate multi-arch friendly linux-libc-dev Cedric Hombourger
2019-07-04 20:50 ` [PATCH v3 1/1] builddeb: generate multi-arch friendly linux-libc-dev package 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 [this message]
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=37f96102-34bf-db52-720a-d8c83965f8dc@metux.net \
--to=lkml@metux.net \
--cc=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