• Bug#1060732: abinit: FTBFS with stack-clash-protection on armhf

    From Emanuele Rocca@21:1/5 to All on Sat Jan 13 15:00:01 2024
    Source: abinit
    Version: 9.10.4-2
    Severity: serious
    Tags: patch
    User: debian-arm@lists.debian.org
    Usertags: 32bit-stackclash

    Dear Maintainer,

    abinit currently fails to build from source on armhf. To address the immediate issue, please disable stack-clash-protection with the following snippet in debian/rules:

    ifeq ($(DEB_TARGET_ARCH),armhf)
    export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash
    else
    export DEB_BUILD_MAINT_OPTIONS = hardening=+all
    endif

    You can find the full build logs of a failed build at: http://qa-logs.debian.net/2024/01/11/armhf/abinit_9.10.4-2_unstable-armhf.log

    The failure is:

    Command /<<PKGBUILDDIR>>/src/98_main/abinit /<<PKGBUILDDIR>>/tests/Test_suite/fast_t26/t26.abi > /<<PKGBUILDDIR>>/tests/Test_suite/fast_t26/t26.stdout 2> /<<PKGBUILDDIR>>/tests/Test_suite/fast_t26/t26.stderr
    returned exit_code: 139

    [fast][t26][np=1][run_etime: 0.63 s]: fldiff fatal error:
    file 1 has more significant lines than file 2 (288 > 121).
    [file=t26.abo]
    [fast][t26][np=1] Test was not expected to fail but subprocesses returned retcode: 139

    Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

    Backtrace for this error:
    Segmentation fault

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Feb 4 22:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Sun, 04 Feb 2024 21:01:51 +0000
    with message-id <E1rWjcd-006ebz-Pb@fasolo.debian.org>
    and subject line Bug#1060732: fixed in abinit 9.10.4-3
    has caused the Debian Bug report #1060732,
    regarding abinit: FTBFS with stack-clash-protection on armhf
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    1060732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060732
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 13 Jan 2024 13:50:32 +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=-5.6 required=4.0 tests=BAYES_00,DKIM_SIGNED,
    DKIM_VALID,DKIM_VALID_EF,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,
    FROMDEVELOPER,FVGT_m_MULTI_ODD,HEADER_FROM_DIFFERENT_DOMAINS,
    RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 35; hammy, 150; neutral, 59; spammy,
    0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--armhf, 0.000-+--qalogsdebiannet,
    0.000-+--qa-logs.debian.net
    Return-path: <emarocca@gmail.com>
    Received: from mail-ej1-x62b.google.com ([2a00:1450:4864:20::62b]:38153