public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/106998] New: libsanitizer PATH_MAX not defined for linux new targets Date: Wed, 21 Sep 2022 16:39:44 +0000 [thread overview] Message-ID: <bug-106998-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106998 Bug ID: 106998 Summary: libsanitizer PATH_MAX not defined for linux new targets Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- ../../../../../../../gcc/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:438:23: error: 'PATH_MAX' was not declared in this scope; did you mean 'PTY_MAX'? 438 | unsigned path_max = PATH_MAX; | ^~~~~~~~ | PTY_MAX should include <linux/limits.h>
next reply other threads:[~2022-09-21 16:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-21 16:39 unlvsur at live dot com [this message] 2022-09-22 17:37 ` [Bug sanitizer/106998] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-12-22 14:37 ` rguenth at gcc dot gnu.org 2023-02-21 13:55 ` rguenth at gcc dot gnu.org 2023-02-22 1:46 ` unlvsur at live dot com 2023-03-27 13:56 ` rguenth at gcc dot gnu.org 2023-07-07 10:44 ` [Bug sanitizer/106998] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-21 5:05 ` pinskia at gcc dot gnu.org
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-106998-4@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).