https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119694
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm not sure there is enough time before the branching for new options etc.
So, I just wondered about something that can be done quickly, whether it is
renaming
most of the getenv uses (except for those which are already in supportable
state, dunno, is that
getenv("PATH")/getenv("GCOBOL_DATA")/getenv("GCOBOL_TEMPDIR") ?
Anything else?) say to gcbl_getenv and either
#if 0
#define gcbl_getenv(x) getenv(x)
#else
#define gcbl_getenv(x) ((char *)nullptr)
#endif
or make it dependent on #ifdef GCOB_MAINTAINER_DEBUGGING or something like
that.
And after branching (hopefully next week) we'd change it on the trunk back and
eventually resolve cleanly.
After all, most of the COBOL debugging will be done on the GCC trunk (to be GCC
16) and on rare occassions there will be some backports from trunk to 15 branch
after a while.
