public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fernando.hueso at uv dot es" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/29452] /home/dave/gnu/glibc/glibc/debug/../string/bits/string_fortified.h:30: undefined reference to `__builtin_dynamic_object_size' Date: Fri, 07 Jul 2023 15:03:28 +0000 [thread overview] Message-ID: <bug-29452-131-ud0PxvWu6h@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29452-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29452 ferdymercury <fernando.hueso at uv dot es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fernando.hueso at uv dot es --- Comment #5 from ferdymercury <fernando.hueso at uv dot es> --- 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). 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! -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-07 15:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-06 14:41 [Bug string/29452] New: " danglin at gcc dot gnu.org 2022-08-07 8:43 ` [Bug string/29452] " fweimer at redhat dot com 2022-08-07 15:07 ` dave.anglin at bell dot net 2022-08-08 16:11 ` dave.anglin at bell dot net 2022-08-08 16:19 ` siddhesh at sourceware dot org 2023-07-07 15:03 ` fernando.hueso at uv dot es [this message] 2023-07-07 15:08 ` siddhesh at sourceware dot org 2023-07-07 15:41 ` fernando.hueso at uv dot es
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29452-131-ud0PxvWu6h@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).