public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/99476] 'PATH_MAX' was not declared in this scope Date: Mon, 08 Jan 2024 09:50:42 +0000 [thread overview] Message-ID: <bug-99476-4-vHp7CBy3Ry@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99476 Ilya Leoshkevich <iii at linux dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iii at linux dot ibm.com --- Comment #3 from Ilya Leoshkevich <iii at linux dot ibm.com> --- I had a similar issue when compiling GCC targeting i686-linux on x86_64 debian, and --includedir= helped, thanks! I had to do the following: ../configure --target=i686-linux-gnu --disable-bootstrap --prefix=/usr --includedir=/usr/i686-linux-gnu/include
next prev parent reply other threads:[~2024-01-08 9:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-08 22:35 [Bug sanitizer/99476] New: " unlvsur at live dot com 2022-01-16 23:31 ` [Bug sanitizer/99476] " unlvsur at live dot com 2023-05-18 3:46 ` syq at debian dot org 2024-01-08 9:50 ` iii at linux dot ibm.com [this message] 2024-02-21 5:12 ` 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-99476-4-vHp7CBy3Ry@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).