[From nobody Sat Mar 28 17:35:06 2026
Received: (at maintonly) by bugs.debian.org; 24 Feb 2026 16:09:23 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-106.1 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
 DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,
 FROMDEVELOPER,MD5_SHA1_SUM,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
 USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 16; hammy, 150; neutral, 45; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <ema@debian.org>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:60268)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <ema@debian.org>) id 1vuuyR-001D3l-1o
 for maintonly@bugs.debian.org; Tue, 24 Feb 2026 16:09:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=NN96Z2/SgnBY5uGHFB4ABUcHqQ3WaqVZdEQ+t4+QhSA=; b=HDG5Okr+TGZV+OnWe9remv5au5
 5nbAc3PsPHyElUNhBepoo9A2GDpomm/fjSPnxq0mf7ijQ0+SZqCN2eWZXyjdualpTXowjxcv18f+m
 0mU9YaP36VOQRukB/+KJxuHiZT9Xst1YweFB6ONCyg+NKeG/xc4MGAJ3K6dvn7CGsTI2laYlwzZ0n
 M33FCMEIh8KFvzqp8eDs5xdX8DIoEqQh4uxIedeuDgzb5/UL0iYWrA9ANzgrQdQZrUjXvLTWJvp8O
 sjt48LA+YB/+M+qHQs6uc1+EF5GqxfmFgT0MC5YW9HC4sdunef9YQZMCvCwKXlH8QUL/6yhufprHY
 mk2vF28Q==;
Received: from authenticated user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from <ema@debian.org>) id 1vuuyP-009sti-DW
 for maintonly@bugs.debian.org; Tue, 24 Feb 2026 16:09:22 +0000
Date: Tue, 24 Feb 2026 17:09:19 +0100
From: Emanuele Rocca <ema@debian.org>
To: maintonly@bugs.debian.org
Subject: yorick-yeti: FTBFS with glibc 2.43 on arm64, issue with 2MB THP
Message-ID: <aZ3NL1oF0PpKdFtu@ariel.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: ema
Delivered-To: maintonly@bugs.debian.org

Source: yorick-yeti
Version: 6.4.0-2
Severity: important
Tags: ftbfs upstream
Justification: fails to build from source
User: debian-glibc@lists.debian.org
Usertags: glibc-2.43

Hi,

yorick-yeti fails to build from source on arm64 when using glibc 2.43,
currently in experimental.

The issue is triggered by glibc 2.43 on arm64 enabling 2MB THP by
default:
https://sourceware.org/git/?p=glibc.git;a=commit;h=321e1fc73f53081d92ba357cdd48c56b79292020

Successful build with glibc 2.42, currently in sid:
https://people.debian.org/~ema/glibc-2.43-rebuilds/output-2/yorick-yeti_arm64.build

Logs of a failed build with glibc 2.43 are here:
https://people.debian.org/~ema/glibc-2.43-rebuilds/output-1/yorick-yeti_arm64.build

The following test is failing:

ERROR (__dft_op) mathlib function signals error
  LINE: 67  FILE: /build/reproducible-path/yorick-yeti-6.4.0/fftw/yeti_fftw_test.i

Notably, the problem cannot be reproduced when building the package with
dpkg-buildpackage, while it can be reproduced with sbuild. An important
difference between the two environments is that sbuild has an empty
/sys/kernel/, and glibc 2.43 checks if THP are enabled by looking under
/sys/kernel/mm/transparent_hugepage/enabled.

See https://bugs.debian.org/1128916 for a somehow related issue.
]