From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2E36438555B3; Fri, 7 Jul 2023 15:03:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E36438555B3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1688742209; bh=sNi27vSqHcqgC4kL6ZYAg+q8MNg62CSm+PN7AG9w/jk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Fnhc6A8oGOBBYa51RrdUrZAOKGxkPJ0wVq1qUbegDpZ9Ru05aOERvgk6WnZ4rsF/6 DLEs1XP1R1wfS7UAjlLdbFeKtTMzESa/2t7Epw2pAJceaIIB33zmLKSDt4HsfxikOi mVfl4YwFoCdu+dQsYzkCkOgneMkhys67DvJ+e2nI= From: "fernando.hueso at uv dot es" 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:03:28 +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: fernando.hueso at uv dot es 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 ferdymercury changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fernando.hueso at uv dot es --- Comment #5 from ferdymercury --- I have found (kind of) a similar problem. I was using nvcc-8 on Ubuntu22, a= nd after some glibc package upgrades, it stopped working. (see https://stackoverflow.com/questions/76531467/nvcc-cuda8-gcc-5-3-no-longer-c= ompiles-with-o1-on-ubuntu-22-04). Now getting: /usr/include/x86_64-linux-gnu/bits/string_fortified.h(104): error: identifier "__builtin___stpncpy_chk" is undefined 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. Thanks! --=20 You are receiving this mail because: You are on the CC list for the bug.=