FX Coudert writes:
>> Ah yes indeed it is systematic. Many thanks for spotting this - git
>> pushed GNU flex required
>> https://gcc.gnu.org/pipermail/gcc-cvs/2024-July/406305.html
>
> Couldn’t the generated files be committed to the tree, so that flex is not
> needed (unless one modifies the s
> Ah yes indeed it is systematic. Many thanks for spotting this - git
> pushed GNU flex required
> https://gcc.gnu.org/pipermail/gcc-cvs/2024-July/406305.html
Couldn’t the generated files be committed to the tree, so that flex is not
needed (unless one modifies the source). This is what is done
FX Coudert writes:
> Another quick m2-related question: I am seeing, in a build of GCC
> 14.1.0 on Linux, that flex is called when building with the modula-2
> front-end. It was not the case in previous builds, and the only
> difference is that I added m2 to the languages. Is that systematic? If
Another quick m2-related question: I am seeing, in a build of GCC 14.1.0 on
Linux, that flex is called when building with the modula-2 front-end. It was
not the case in previous builds, and the only difference is that I added m2 to
the languages. Is that systematic? If so, the prerequisites page
FX Coudert writes:
> Hi,
>
> I am unable to perform a nonbootstrap build when gm2 is included, with
> Apple clang 15 as compiler. The error is due to incorrect inclusion of
> headers ( and ) which are included after GCC’s
> system.h has been included, and macros like abort() are redefined or
> po
Hi,
I am unable to perform a nonbootstrap build when gm2 is included, with Apple
clang 15 as compiler. The error is due to incorrect inclusion of headers
( and ) which are included after GCC’s system.h has been
included, and macros like abort() are redefined or poisoned.
I think the correct id
