public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105719] RFE: fixincludes should handle Frameworks
Date: Thu, 18 May 2023 10:24:20 +0000 [thread overview]
Message-ID: <bug-105719-4-YwA2GElbEl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105719-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #4)
> Created attachment 55084 [details]
> Implement the use of fixed framework headers
>
> this was a proof-of-principle exercise while looking into issues caused by
> implementing __has_feature () [PR60512].
>
> This does not have any of the mechanism to *create* or *install* the fixed
> headers (for my testing I just built a
> CoreFoundation.framework/Headers/CFBase.h and edited bye hand to fix the
> problems found).
>
> So, still plenty to do ;)
Remind me to test this patch later; I've kind of forgotten where I was with
this... distracted with other stuff... (maybe I should unassign it from
myself?)
next prev parent reply other threads:[~2023-05-18 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 14:41 [Bug target/105719] New: " egallager at gcc dot gnu.org
2022-05-24 14:42 ` [Bug target/105719] " egallager at gcc dot gnu.org
2022-05-24 14:49 ` egallager at gcc dot gnu.org
2022-05-24 19:21 ` iains at gcc dot gnu.org
2023-05-14 19:43 ` iains at gcc dot gnu.org
2023-05-15 18:10 ` bkorb at gnu dot org
2023-05-18 10:24 ` egallager at gcc dot gnu.org [this message]
2024-06-07 19:58 ` egallager 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-105719-4-YwA2GElbEl@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).