On Sun, 2019 Nov 17 22:34-05:00, Bruno Haible wrote:
>
> > (There are other environment variables documented at the link above
> > that may be of interest, but I have not found any additional ones to
> > be necessary to fix issues in gnulib's test suite.)
>
> So, the gnulib tests for the math functions and *printf work fine
> without _EDC_SUSV3? And the ones for *printf work fine without
> _EDC_C99_NAN?
I have not seen any test failures related to the functionality affected
by those two variables. But are the behaviors at issue covered by the
tests, thorough as they otherwise are?
For example, if I look at the log10*() family of functions, I see this
in the IBM doc:
If x is 0, the function returns -HUGE_VAL and errno remains
unchanged.
Note: When environment variable _EDC_SUSV3 is set to 2, and if x is
0, the function returns -HUGE_VAL and sets errno to ERANGE.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxbd00/log10.htm
So it sets ERANGE where it otherwise wouldn't have before. But there is
no mention of ERANGE in tests/test-log* ... should there be?
> I think many programs that are built with gnulib invoke other programs;
> therefore it is risky to add setenv calls for such environment variables
> to gnulib itself. But we can do so
> - in the documentation,
> - in particular tests. You mentioned test-sigpipe.sh; do you have a
> list of tests which fail by default and succeed with one of these
> environment variables.
That is the only one I've found, of all the tests. It fails because the
output file t-sigpipeA.tmp is not empty; it contains the text
CEE5213S The signal SIGPIPE was received.
z/OS often takes the opportunity to do things slightly differently from
other systems, if the letter of the standard allows it :/
--Daniel
--
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.
