public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/115368] Wrong order of gcc include paths on musl systems
Date: Thu, 06 Jun 2024 18:42:37 +0000 [thread overview]
Message-ID: <bug-115368-4-q4Hp9M9Wvg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115368-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115368
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2024-06-06
Ever confirmed|0 |1
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Also how come glibc targets get it correct:
[apinski@xeond2 gcc]$ ~/upstream-gcc-match/bin/gcc -E -Wp,-v -
ignoring nonexistent directory
"/home/apinski/upstream-gcc-match/lib/gcc/x86_64-pc-linux-gnu/15.0.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/home/apinski/upstream-gcc-match/lib/gcc/x86_64-pc-linux-gnu/15.0.0/include
/usr/local/include
/home/apinski/upstream-gcc-match/include
/home/apinski/upstream-gcc-match/lib/gcc/x86_64-pc-linux-gnu/15.0.0/include-fixed
/usr/include
next prev parent reply other threads:[~2024-06-06 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 7:00 [Bug driver/115368] New: " raj.khem at gmail dot com
2024-06-06 7:03 ` [Bug driver/115368] " raj.khem at gmail dot com
2024-06-06 16:56 ` raj.khem at gmail dot com
2024-06-06 18:33 ` redi at gcc dot gnu.org
2024-06-06 18:40 ` pinskia at gcc dot gnu.org
2024-06-06 18:42 ` pinskia at gcc dot gnu.org [this message]
2024-06-06 18:47 ` 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-115368-4-q4Hp9M9Wvg@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: link
Be 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).