From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B4F2E3850AE3; Fri, 7 Jul 2023 15:08:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B4F2E3850AE3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1688742510; bh=wqsK8mA8liIRatXg/0Sl8ND2sL5dSfuwEG+g37OmuSc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NUOdxnwhRIuxIokhZSryK8FDZpgDyAQKMN/QNENE4ZggeQFj5zK1Dg2Pw5GALbwtH J1m54zDEJdSkWNOtl6oJOCLn2RKBDplZ2FEpwsjc+DOneyMAgTcGvc+/PSwv+E881O a9U2oyPEzcwldXh78jfXipJAs5/gWnt3wZrHLyyo= From: "siddhesh at sourceware dot org" To: glibc-bugs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBzdHJpbmcvMjk0NTJdIC9ob21lL2RhdmUvZ251L2dsaWJj?= =?UTF-8?B?L2dsaWJjL2RlYnVnLy4uL3N0cmluZy9iaXRzL3N0cmluZ19mb3J0aWZpZWQu?= =?UTF-8?B?aDozMDogdW5kZWZpbmVkICByZWZlcmVuY2UgdG8gYF9fYnVpbHRpbl9keW5h?= =?UTF-8?B?bWljX29iamVjdF9zaXplJw==?= Date: Fri, 07 Jul 2023 15:08:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: string X-Bugzilla-Version: 2.38 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: siddhesh at sourceware dot org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: 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 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=3D29452 Siddhesh Poyarekar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael.hudson at canonica= l dot co | |m --- Comment #6 from Siddhesh Poyarekar --- (In reply to ferdymercury from comment #5) > I have found (kind of) a similar problem. I was using nvcc-8 on Ubuntu22, > and after some glibc package upgrades, it stopped working. (see > https://stackoverflow.com/questions/76531467/nvcc-cuda8-gcc-5-3-no-longer- > compiles-with-o1-on-ubuntu-22-04). >=20 > Now getting: /usr/include/x86_64-linux-gnu/bits/string_fortified.h(104): > error: identifier "__builtin___stpncpy_chk" is undefined >=20 > I was wondering if there is a way to hack 'by hand' the string_fortified.h > with an #ifdef guard that checks for the CUDA_version... to restore the > original behavior before the package upgrade. >=20 > Thanks! This looks like something we fixed in 2.36 and backported to the 2.35 relea= se branch: https://sourceware.org/git/?p=3Dglibc.git;a=3Dcommit;h=3D478cd506eaa5bbc81e= 3de6593a5064fa5f36fea9 Ubuntu needs to rebase its release or at least cherry-pick that fix. --=20 You are receiving this mail because: You are on the CC list for the bug.=