All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: unlisted-recipients:; (no To-header on input)
Cc: <isar-users@googlegroups.com>,
	Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	<yamada.masahiro@socionext.com>, <michal.lkml@markovi.net>,
	<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] builddeb: generate multi-arch friendly linux-libc-dev package
Date: Mon, 17 Jun 2019 08:14:56 +0200	[thread overview]
Message-ID: <1560752096-1323-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)

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.

Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Reviewed-by: Henning Schild <henning.schild@siemens.com>
---
 scripts/package/builddeb | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index b03dd56a4782..8f7afb3a84e9 100755
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -132,6 +132,11 @@ fi
 if [ "$ARCH" != "um" ]; then
 	$MAKE -f $srctree/Makefile headers_check
 	$MAKE -f $srctree/Makefile headers_install INSTALL_HDR_PATH="$libc_headers_dir/usr"
+	# move asm headers to /usr/include/<libc-machine>/asm to match the structure
+	# used by Debian-based distros (to support multi-arch)
+	libc_mach=$($CC -dumpmachine)
+	mkdir $libc_headers_dir/usr/include/$libc_mach
+	mv $libc_headers_dir/usr/include/asm $libc_headers_dir/usr/include/$libc_mach/
 fi
 
 # Install the maintainer scripts
-- 
2.11.0


WARNING: multiple messages have this Message-ID (diff)
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Cc: isar-users@googlegroups.com,
	Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	yamada.masahiro@socionext.com, michal.lkml@markovi.net,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] builddeb: generate multi-arch friendly linux-libc-dev package
Date: Mon, 17 Jun 2019 08:14:56 +0200	[thread overview]
Message-ID: <1560752096-1323-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)

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.

Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Reviewed-by: Henning Schild <henning.schild@siemens.com>
---
 scripts/package/builddeb | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index b03dd56a4782..8f7afb3a84e9 100755
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -132,6 +132,11 @@ fi
 if [ "$ARCH" != "um" ]; then
 	$MAKE -f $srctree/Makefile headers_check
 	$MAKE -f $srctree/Makefile headers_install INSTALL_HDR_PATH="$libc_headers_dir/usr"
+	# move asm headers to /usr/include/<libc-machine>/asm to match the structure
+	# used by Debian-based distros (to support multi-arch)
+	libc_mach=$($CC -dumpmachine)
+	mkdir $libc_headers_dir/usr/include/$libc_mach
+	mv $libc_headers_dir/usr/include/asm $libc_headers_dir/usr/include/$libc_mach/
 fi
 
 # Install the maintainer scripts
-- 
2.11.0

             reply	other threads:[~2019-06-17  6:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  6:14 Cedric Hombourger [this message]
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 12:39     ` Cedric Hombourger
2019-07-04 13:10   ` Ben Hutchings
2019-07-04 19:42     ` [PATCH v2] " Cedric Hombourger
2019-07-04 19:42       ` Cedric Hombourger
2019-07-04 19:49       ` Ben Hutchings
2019-07-04 20:28         ` Cedric Hombourger
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           ` Cedric Hombourger
2019-07-04 20:50           ` [PATCH v3 1/1] builddeb: generate multi-arch friendly linux-libc-dev package Cedric Hombourger
2019-07-04 20:50             ` 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                 ` Cedric Hombourger
2019-07-09  7:43                 ` [PATCH v4] builddeb: generate multi-arch friendly linux-libc-dev package Cedric Hombourger
2019-07-09  7:43                   ` 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-14  7:49                       ` Cedric Hombourger

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=1560752096-1323-1-git-send-email-Cedric_Hombourger@mentor.com \
    --to=cedric_hombourger@mentor.com \
    --cc=isar-users@googlegroups.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.