busybox-w32/testsuite/env.tests, branch mount_pointA mirror of https://github.com/rmyorston/busybox-w32.git
https://git.lua4.win/busybox-w32/atom?h=mount_point2023-08-19T08:32:30+00:00testsuite: skip some tests in native build2023-08-19T08:32:30+00:00Ron Yorstonrmy@pobox.com2023-08-19T08:32:30+00:00urn:sha1:77aa74d151643ff2ec96156942e004fba19464a5
The testsuite includes some Windows-specific tests. Exclude these
when running a test on a native build to avoid upsetting the results.
win32: better fix for empty environment variables2022-05-05T14:14:10+00:00Ron Yorstonrmy@pobox.com2022-05-05T14:14:10+00:00urn:sha1:3b5042430fc4b82d44e0430f9ecc21a9228d1651
It appears the CRT and OS each have a copy of the environment.
mingw_putenv() fools the CRT into accepting an empty environment
variable by calling _putenv("V=0") then truncating the new value
by hand. But _putenv() also updates the OS environment with the
fake 'V=0' value. Commit 5b48ca53b (win32: pass NULL to spawnve,
not environ) resulted in this fake value being used and hence empty
variables getting the value '0'.
- Add a call to SetEnvironmentVariable() in mingw_putenv() to update
the OS environment.
- Restore the use of NULL environment pointers in mingw_spawnvp().
- Add a test.
(GitHub issue #250)