[Bug build/34312] New: [2.44 Regression] glibc failed to build for i686

https://sourceware.org/bugzilla/show_bug.cgi?id=34312

            Bug ID: 34312
           Summary: [2.44 Regression] glibc failed to build for i686
           Product: glibc
           Version: 2.44
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
                CC: carlos at redhat dot com
  Target Milestone: ---
            Target: i686

On Linux/x86-64, when configured with

BUILD_CC="gcc" TEST_CC="gcc -m32" TEST_CXX="g++ -m32" CC="gcc -m32" CXX="g++
-m32" CFLAGS="-O2 -g -march=i686"
/export/gnu/import/git/sources/glibc/configure --prefix=/usr --without-selinux
--target=i686-linux --build=i686-linux --host=i686-linux
--enable-hardcoded-path-in-tests --enable-large-benchtests
--enable-stack-protector=all --with-timeoutfactor=3

I got

/tmp/cckNiV9Q.s: Assembler messages:
/tmp/cckNiV9Q.s: Warning: local symbol `_dl_sysinfo_int80' has non-default
visibility

using binutils with

commit c4150acbda1b3ce0602f79cbb7700b39e577be7e
Author: Jan Beulich <[email protected]>
Date:   Fri May 8 11:45:04 2026 +0200

    gas/ELF: warn upon non-default visibility of local symbols

    The spec explicitly precludes STB_LOCAL together with STV_PROTECTED (and,
    implicity, STV_HIDDEN or STV_INTERNAL), so we better wouldn't entirely
    silently write out symbols violating this.

    LoongArch's tc_symbol_new_hook() simply needs dropping. If FAKE_LABEL_NAME
    symbols can end up global, marking them hidden would need doing elsewhere.
    There not being a need to make any testsuite adjustments suggests though
    that this won't normally (ever?) happen.

    A couple of testcases then also need adjustment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.