From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6703379430489718784 X-Received: by 2002:ac2:414d:: with SMTP id c13mr9822332lfi.47.1562245811669; Thu, 04 Jul 2019 06:10:11 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:ac2:5213:: with SMTP id a19ls336806lfl.8.gmail; Thu, 04 Jul 2019 06:10:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqzM5ReHlGVuEJOEZCYndQLv43kQttU4lS8aXJzSlXTC6QWEWH+hs6IAXFvnU2V0f4eXHWEx X-Received: by 2002:ac2:5231:: with SMTP id i17mr21037973lfl.39.1562245811158; Thu, 04 Jul 2019 06:10:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562245811; cv=none; d=google.com; s=arc-20160816; b=hK7Kf2y2OJ9IDVBbKmIymOXIXpSj9eJILYK13vFGYQtXvTz+G5zR4j7dSmo5x8DAng d/PMejIuL4Gk5tu7TgHYu7VDsox7LrdPqBcVijM6hmPo0afN1LwN011JSFJ07EFzaIlT frpwgf3BICsYNBDOg3MdYboUA+qcKWzXMf2KFWYKSN9kaX2UfDOj3zrNCksZQq2+LiRo vIpxq6/E44DkSYK/Rz6BVLUb+1Z0PyYXFLpPKz0nMuDUMox/DuJKRuBB4Uz9xjkXle67 nW/w8rE9BBld31T2EzrvaTt9z5gxSsCz7DzgkekglbyXC8jKSJxY0qwBImAU7kTbah/7 DYEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:user-agent:references:in-reply-to:date:cc:to:from :subject:message-id; bh=nVYogWte++m/uS4CvExii1G4XGrrMdd3FOR+oZfs2Lo=; b=T00Bpbq61Agm4lS9NaexjsJj3k52UK3TA+XB9EJcd9MSQEOnLDmm3VZAtFt7SKTLGA mpopuFcWDGu52NyMFhsjJlEYGHtphBCnoLTGU/qUSVvVsm655hDF2QXjTHMB10Ni141Z 1JYZ+UZvglT4eD6ZFgqj3WIKUlMITHzsDX/ARkjAzmxfFCbnehvvzC4GV+8Ri+aALBu1 DYbf78UVhIXTGhrbjjrrPD1O0drbaNpHpZa9EcNRtdss0gth/ekXhWd8HQsTd/K6zFJN 5MiP7y9JCaHTZFW88j110R86QLsjluJnQ5aG70T819gUdgbGqQOyO74CB75ZM3Vbhi4a WTFg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ben@decadent.org.uk designates 88.96.1.126 as permitted sender) smtp.mailfrom=ben@decadent.org.uk Return-Path: Received: from shadbolt.e.decadent.org.uk (shadbolt.e.decadent.org.uk. [88.96.1.126]) by gmr-mx.google.com with ESMTPS id r27si280139ljn.3.2019.07.04.06.10.10 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 04 Jul 2019 06:10:11 -0700 (PDT) Received-SPF: pass (google.com: domain of ben@decadent.org.uk designates 88.96.1.126 as permitted sender) client-ip=88.96.1.126; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ben@decadent.org.uk designates 88.96.1.126 as permitted sender) smtp.mailfrom=ben@decadent.org.uk Received: from [192.168.4.242] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hj1V1-0006UL-4P; Thu, 04 Jul 2019 14:10:07 +0100 Received: from ben by deadeye with local (Exim 4.92) (envelope-from ) id 1hj1V0-000833-U3; Thu, 04 Jul 2019 14:10:06 +0100 Message-ID: <0ff3202ced2b501d6045157f1c7b50810c0571e5.camel@decadent.org.uk> Subject: Re: [PATCH] builddeb: generate multi-arch friendly linux-libc-dev package From: Ben Hutchings To: Masahiro Yamada , Cedric Hombourger Cc: isar-users@googlegroups.com, Michal Marek , Linux Kbuild mailing list , Linux Kernel Mailing List , Riku Voipio Date: Thu, 04 Jul 2019 14:10:02 +0100 In-Reply-To: References: <1560752096-1323-1-git-send-email-Cedric_Hombourger@mentor.com> Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-BZKpguClIp8ilfm1QdtD" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.4.242 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false X-TUID: tZW9qYzWPrvh --=-BZKpguClIp8ilfm1QdtD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2019-07-04 at 09:43 +0900, Masahiro Yamada wrote: > CCed a couple of people. >=20 > On Mon, Jun 17, 2019 at 3:15 PM Cedric Hombourger > wrote: > > Debian-based distributions place libc header files in a machine > > specific directory (/usr/include/) 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. > >=20 > > Signed-off-by: Cedric Hombourger > > Reviewed-by: Henning Schild > > --- > > scripts/package/builddeb | 5 +++++ > > 1 file changed, 5 insertions(+) > >=20 > > 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" !=3D "um" ]; then > > $MAKE -f $srctree/Makefile headers_check > > $MAKE -f $srctree/Makefile headers_install INSTALL_HDR_PATH=3D"= $libc_headers_dir/usr" > > + # move asm headers to /usr/include//asm to match = the structure > > + # used by Debian-based distros (to support multi-arch) > > + libc_mach=3D$($CC -dumpmachine) > > + mkdir $libc_headers_dir/usr/include/$libc_mach > > + mv $libc_headers_dir/usr/include/asm $libc_headers_dir/usr/incl= ude/$libc_mach/ This is wrong; the multiarch architecture tuple used in directory names does not necessarily match the compiler's architecture tuple. Firstly, if you use a biarch compiler the compiler is only going to tell you the default architecture. Secondly, on i386 the minimum processor is i586 or i686 but the multiarch architecture tuple is still "i386-linux-gnu" (and there might be other cases like this). So, the correct command is: dpkg-architecture -a$debarch -qDEB_HOST_MULTIARCH > > fi > >=20 > > # Install the maintainer scripts >=20 > I am not sure but, > I just worried about the backward compatibility... > Was this previously broken? Debian has had multiarch support since Debian 7 "wheezy", and older versions are no longer supported. So I think this change is fine to make unconditionally. The current linux-libc-dev packages build by "make deb-pkg" are "broken" in that multiple architectures can't be co-installed with each other, whereas this genrally can be done with the linux-libc-dev packages provided by Debian-based distributions. However, co- installation is only allowed if the version strings and contents of common files in the packages are identical, and I don't know whether that's going to be true for those generated by "make deb-pkg". > I guess debian is using own control file > instead of the one in upstream kernel. We maintain multiple configurations, a meaningful changelog, tools packages, etc. So "make deb-pkg" is not used for official kernel packages but we recommend it for custom kernels. > So, this is almost a matter for developers, I think. >=20 > How did debian-base distros managed this before, > and will this introduce no breakage? On the Debian side a similar change was made in Debian 7 "wheezy". In Ubuntu I believe it was done earlier as they modified dpkg to support multiarch before us. > Ben, > Could you comment on this? Ben. --=20 Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. --=-BZKpguClIp8ilfm1QdtD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl0d+qoACgkQ57/I7JWG EQlj5w/6A7Dpm2f0EbQF+Zdnfmf9gTCl8GGkRIuZ5I6YNr4t4SwUAptrZs8R34Zj RHemXnL7F/H1Baw3nAtbO9GE+76vatgwtdkhRC6B7fwNxPhUOgkGnbN8sZ+67qmu yuJ4Ap2IGagPh6D21APIF4s4XzEA7rD0B1kJUO0H7VKeztM58zuUnPiDmmXg4/YZ whgnLfJyUDDyny6HUdFJ2lvTeVOFYN0MWSKwqyR8mEDoAoCzcKX+OyFbs+Fu3Lys CgGjip3wpIshqibwUxVUzqq+qLTmfCuTsT7Vd/s/aBf3bD/8qNphL8zO2AsLrHdP RlwXzRZ9Sq+GajvHGcJqwdz+azF/oJfOCse138+HrK5lmt2RSxr9f1Zgqf9P/Pve eJy51IWmIKvEBiIx3bAATfwu8g61LlOepHZZooOT0zSQ5RZmoyj/WOPQRAyO6kyq tu/CVG0sbrOl0kEUEdfTFnCJKPGyK9KlTYdF6oXVXsaojIBsqM8IT6KrYQ7s08M2 di8T9P/2+a1Q/d7it0ngt5itBJ3ZBos3yG7oYl+HKxPXP1ITj0h71jUyIC8nCFjb gDzEPHr+0Pp6GNsVG6lfBO9aLJ9QHHj8v28QNSWjuhq2GtF1rEfwefADbtJuZnag bA/So3i8ExEK4yxZ/PJqwKiMJoP0M/3Qs0jyd4uA7rLGuBv8HDM= =xBtL -----END PGP SIGNATURE----- --=-BZKpguClIp8ilfm1QdtD--