https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #8 from Dev Dude ---
Hmmm it seems adding an attachment lost my comment. I'll try to remember most
of it.
First, thanks Nathaniel for your polite comments. Much appreciated.
I'm not sure why Sam is mentioning multiple bugs because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #7 from Dev Dude ---
Created attachment 58661
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58661&action=edit
A script to try to build gcc module headers
A script to try to build gcc module headers, used in absence of knowing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
Nathaniel Shead changed:
What|Removed |Added
CC||nshead at gcc dot gnu.org
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #5 from Dev Dude ---
I'm not sure what's difficult about me posing a question about what the correct
way is to build module headers so they all build properly, and also providing
my own script to show what I'm doing in absence of kno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #4 from Sam James ---
I'd really suggest filing one bug per issue in future. Making it very clear
what a specific bug is about and how to reproduce with a standalone attachment
is good too (your last issue at least seems to need your
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #3 from Dev Dude ---
Hello, any update on this bug? Has anyone run the script I provided in the
prior post for building the module headers? Or can anyone comment on the
correct way to build module headers? I can't progress on modules
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #2 from Dev Dude ---
Just to clarify the initial comment if it is unclear:
It's unclear how to compile C++ standard headers. If I use the script below to
try to build all the standard c++ headers, I see the "random" header errors an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115706
--- Comment #1 from Jonathan Wakely ---
(In reply to Dev Dude from comment #0)
> Unrelated, is this problem going to be fixed?
> import std;
> #include // or any other standard library header
I think that's PR 114990