From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 03C033858D35; Mon, 28 Aug 2023 05:29:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 03C033858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1693200555; bh=K0mPoxCfQii0yX9EQ5j9xk1vmE7NMa4sGXdNX+/V0B0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=D+kF9aicBEWkNizfMeydUWFP4J9mIXqju0+yrOdJ+prNbRhuLdoOxJBZ4W1KLBdPB 7DqZr/nIrZlwtHAOc5TKIRM33f51M1NXZb89hhhkaOr5v/1/Yeo0mG18kW+y8F+xlF BiSJFjznFsAOwgyYFLCe0WlulYUE+HqrIYL3gEnY= From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/30798] sysdeps/nptl/lowlevellock.h and lowlevellock-futex.h Date: Mon, 28 Aug 2023 05:29:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc flagtypes.name bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30798 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com Flags| |security- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Florian Weimer --- (In reply to Alexei Sholomitskiy from comment #0) > my question: I'd like to try build glibc-2.31 manually, but with new kern= el > headers 5.15.79, can I do it? Why do you want to do that? These days, we try to make sure that the built glibc (and its included features) does not depend on the kernel header vers= ion. > I understand, different Linux systems have different patches, in order to > have less problems I downloded sources by: > $ apt-get source glibc >=20 > $ cd glibc-2.31 > $ mkdir mybuild; cd mybuild > $ ../configure --prefix=3D/tools/glibc-2.31 --disable-werror > --enable-kernel=3D5.15.0 --with-selinux --enable-stack-protector=3Dstrong > --with-headers=3D/usr/local/lib/modules/5.15.79/source/include --with-tls > --enable-add-ons --enable-multi-arch --enable-nss-crypt --enable-pt_chown > --enable-tunables=3Dyes --enable-shared You need to configure with --prefix=3D/usr. For compatibility with Debian multi-arch, you need additional flags and maybe patches. Debian hasn't upstreamed their multi-arch implementation. Your problems maybe caused by --with-headers=3D/usr/local/lib/modules/5.15.79/source/include because as f= ar as I understand it, this is a path that is used for the kernel module headers,= but you need the UAPI headers for building glibc. This topic is more suited to the libc-help mailing list. --=20 You are receiving this mail because: You are on the CC list for the bug.=