Latest gcc throws errors when using tmpnam. Generate temporary file name within the test to work around. It has the same shortcomings as using tmpnam, but they are no risk as it is used only in the tests.
Details
Motivation and Context
Test didn't compile anymore on my Linux machine.
How Has This Been Tested?
It is within a test. The test passes.
Types of changes
[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
Checklist:
[x] It is my own work, its copyright is implicitly assigned to the project and no substantial part of it has been copied from other sources (including Stack Overflow). In rare occasions this is acceptable, like in CMake modules where the original copyright information should be kept.
[x] I'm using the same code standards as the existing code (indentation, spacing, variable naming, ...).
[ ] I've added tests for my code.
[x] I have verified whether my change requires changes to the documentation
[x] My change either requires no documentation change or I've updated the documentation accordingly.
[x] My branch has been rebased to main, keeping only relevant commits.
Summary
Latest gcc throws errors when using tmpnam. Generate temporary file name within the test to work around. It has the same shortcomings as using tmpnam, but they are no risk as it is used only in the tests.
Details
Motivation and Context
Test didn't compile anymore on my Linux machine.
How Has This Been Tested?
It is within a test. The test passes.
Types of changes
Checklist: