https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732
Antonio Muci <a.mux at inwind dot it> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |a.mux at inwind dot it
--- Comment #9 from Antonio Muci <a.mux at inwind dot it> ---
Hi,
I have been hit by this con gcc 14.2 [0].
A google search helped me find the (proper) solution suggested by
pins...@gcc.gnu.org (thanks), but from a user point of view it is still very
difficult to figure out without external help.
Moreover, since the "-include" parameter does not accept globs, an invocation
like this:
gcc -c include/*.h -o /dev/null
would become:
gcc -xc -include something1.h -include something2.h [...] /dev/null -o
/dev/null -c
While I now understand why this is the correct way of calling gcc, I concour
with m...@immute.net that:
> Those make sense as internal details.
> I don't think a typical user should be expected to guess or learn these
> differences in order to use the GCC from the command line.
[0]
https://github.com/bancaditalia/secp256k1-frost/blob/5b2ae33158cf929ecc89ca339f88eb2606414fd1/scripts/ensure-frost-header-is-precompilable.sh#L5-L13
