[From nobody Thu Mar 26 05:51:04 2026
Received: (at submit) by bugs.debian.org; 1 Oct 2024 11:30:09 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
 (2021-04-09) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_NONE
 autolearn=ham autolearn_force=no
 version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 149; neutral, 43; spammy,
 0. spammytokens: hammytokens:0.000-+--armhf, 0.000-+--H*F:U*helmut,
 0.000-+--H*F:D*subdivi.de, 0.000-+--H*RU:sk:helmut@,
 0.000-+--H*rp:U*helmut
Return-path: <helmut@subdivi.de>
Received: from isilmar-4.linta.de ([136.243.71.142]:36586)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from <helmut@subdivi.de>) id 1svb4v-00Fqwu-GY
 for submit@bugs.debian.org; Tue, 01 Oct 2024 11:30:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=subdivi.de;
 s=k10.isilmar-4; t=1727782201;
 bh=fZAXEYlwZMoLJYWAzRLnx8aI9yrBHFKGeJXunz8U/6Q=;
 h=Date:From:To:Subject:From;
 b=0b/fHPwhNz/nqk4kY/j1ZeetWHF5HEzJ2osknhaqmd21V819l5AMavg76r9/jnZ3g
 0ti5IQETghm+UN4Aj87IjpZ4ZjbkzKFBf+I2gCcq7MahibXtzmlCtuhN/ULhVzk2dQ
 nmo221B9KzmrTZa+KGqXJd+GVR7W1ryx3VfJCR8v0VhQva2A4XUI5xBW/CaPDhFSsZ
 28DrpnntLvjTq2eb5zsmFfwduLnBLaQObv3G/K9jFLxfvmyJAfI9EjImpFozQV9eX0
 DQfT0H87pwcj4YnVgyYeUKmWl1Gtdl4sMru/pysom57dPZ7q3cw7wRcaPYFcdnVDvG
 rFQjcXfr9Ijpg==
Received: from isilmar-4.linta.de (isilmar.linta [10.0.0.1])
 by isilmar-4.linta.de (Postfix) with ESMTP id CCA4C2004F8
 for <submit@bugs.debian.org>; Tue,  1 Oct 2024 11:30:01 +0000 (UTC)
Date: Tue, 1 Oct 2024 13:29:45 +0200
From: Helmut Grohne <helmut@subdivi.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: nss FTBFS on 32bit arm userland and 64bit kernel
Message-ID: <20241001112945.GA3796004@subdivi.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="a8jucGfmltxR0qi9"
Content-Disposition: inline
X-Reportbug-Version: 13.0.1
Delivered-To: submit@bugs.debian.org


--a8jucGfmltxR0qi9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Source: nss
Version: 2:3.103-1
Severity: important
Tags: ftbfs patch
Control: clone -1 -2
Control: reassign -2 src:nss-pem
Control: clone 948523 -3
Control: reassign -3 src:nss-pem
Control: clone -1 -4
Control: retitle -4 nss-pem: unregistered vendor copy of nss
Control: tags -4 =
Control: reassign -4 src:nss-pem

Hi,

nss and nss-pem FTBFS on the reproducible builds infrastructure for
armhf. For nss-pem, it was the second build that FTBFS. That got me
looking and allowed me identifying the cause. It looks at the uname and
when you build on an arm32 userland with a 64bit kernel, some features
are detected differently (as it looks at uname -m) and then the build
fails.

We already pass OS_TEST for cross building where uname -m is a problem,
so I suggest extending this to cover the arm case and overriding OS_TEST
even for native builds. I'm attaching a patch for your convenience.

As this bug also affects nss-pem, I am cloning the bug (as -2) for
nss-pem and also cloning another bug (as -3) where nss-pem FTCBFS for
ppc64el.

I also observe that the vendoring of nss-pem is not registered in the
security tracker
https://salsa.debian.org/security-tracker-team/security-tracker/-/blob/master/data/embedded-code-copies.
Please unvendor nss from nss-pem or register your copy. This matter is
tracked as bug -4.

Helmut

--a8jucGfmltxR0qi9
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="ftbfs.patch"

--- nss-b/debian/rules
+++ nss-a/debian/rules
@@ -47,6 +47,11 @@
 endif
 TOOLCHAIN += OS_TEST=$(DEB_HOST_GNU_CPU)
 TOOLCHAIN += KERNEL=$(DEB_HOST_ARCH_OS)
+else
+# Avoid misdetecting armhf as arm64 when built on a 64bit kernel.
+ifeq ($(DEB_HOST_GNU_CPU),arm)
+TOOLCHAIN += OS_TEST=arm
+endif
 endif
 
 # $(foreach foo,$(list),$(call cmd,some command $(foo))) expands to

--a8jucGfmltxR0qi9--
]