https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124554

--- Comment #17 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #15)
> (In reply to Jonathan Wakely from comment #13)
> > Cannot compile std module
> > Module initialization function will be missing
> 
> > But bootstrap should complete successfully. Could you please check this and
> > let me know ASAP if it's not working as expected?
> 
> This confused me today, when I saw an 'error:' fly by during building but
> not failing to build. It actually not only shows:
> 
>   Cannot compile std module
>   Module initialization function will be missing
> 
> but later additionally
> 
>   In module imported at std.compat.cc:30:8:
>   std: error: failed to read compiled module: No such file or directory
>   std: note: compiled module file is ‘gcm.cache/std.gcm’
>   std: note: imports must be built before being imported
>   std: fatal error: returning to the gate for a mechanical issue
>   compilation terminated.
>   Cannot compile std.compat module
>   Module initialization function will be missing

Yes, that's expected. The first error happens when compiling std.cc fails. The
second one is because std.compat.cc depends on the std module, which can't be
imported if std.cc failed to compile. So compiling std.compat.cc fails too.

If the first one fails, then both fail. If the first one compiles, it's likely
that the second one would compile because it's a subset of the first one. But
the makefile recipes allow either to fail independently.

> I think I saw some message pointer to an URL before citing some PR, but that
> message seems to be gone now.

That wouldn't have come from libstdc++.

> In any case NVPTX and GCN builds don't fail - as supposed and confirmed by
> Thomas.

Thanks!

Reply via email to