public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "judge.packham at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/111057] [11/12/13 only] build error: libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:180:10: fatal error: crypt.h: No such file or directory Date: Fri, 18 Aug 2023 01:47:54 +0000 [thread overview] Message-ID: <bug-111057-4-YNozBs61SA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111057 --- Comment #5 from Chris Packham <judge.packham at gmail dot com> --- Created attachment 55751 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55751&action=edit Remove crypt and crypt_r interceptors Attached is the patch derived from https://github.com/llvm/llvm-project/commit/d7bead833631486e337e541e692d9b4a1ca14edd which we'll be carrying in crosstool-ng. I've kept the upstream authors and commit message. It should apply cleanly to the releases/gcc-13 branch but is not necessary for 14.x.
next prev parent reply other threads:[~2023-08-18 1:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-18 0:59 [Bug sanitizer/111057] New: " judge.packham at gmail dot com 2023-08-18 1:02 ` [Bug sanitizer/111057] " pinskia at gcc dot gnu.org 2023-08-18 1:04 ` pinskia at gcc dot gnu.org 2023-08-18 1:05 ` [Bug sanitizer/111057] [11/12/13 only] " pinskia at gcc dot gnu.org 2023-08-18 1:05 ` pinskia at gcc dot gnu.org 2023-08-18 1:21 ` judge.packham at gmail dot com 2023-08-18 1:47 ` judge.packham at gmail dot com [this message] 2024-03-11 21:47 ` romain.geissler at amadeus dot com
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-111057-4-YNozBs61SA@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).