[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37f96102-34bf-db52-720a-d8c83965f8dc@metux.net>
Date: Tue, 9 Jul 2019 12:20:43 +0200
From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To: Cedric Hombourger <Cedric_Hombourger@...tor.com>,
yamada.masahiro@...ionext.com
Cc: ben@...adent.org.uk, isar-users@...glegroups.com,
michal.lkml@...kovi.net, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, riku.voipio@...aro.org
Subject: Re: [PATCH v4] builddeb: generate multi-arch friendly linux-libc-dev
package
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@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists