On Sun, 21 Aug 2022, Bruno Haible wrote:
>
> This is the situation on the various platforms:
[snip]
> * In C mode: does
>
> AIX: #include , defines only macros
> FreeBSD: self-contained
> Haiku: self-contained
> HP-UX: #include , defines only macros
> macOS: self-contained
On Monday I wrote:
> > to exclude other problems, we need to check it on a platform-by-platform
> > basis.
This is the situation on the various platforms:
* In C++ mode,
- either the C is used,
- or a C++ exists that
#include
- or a C++ exists that #include <__config>,
Paul Eggert asked:
> > Could you investigate further why mingw 64-bit fails?
Some words on the "why". You seem to have expectations regarding the
distribution quality of the resulting file names, but these expectations
are not warranted.
Donald E. Knuth wrote in TAOCP vol 2 "Seminumerical algorit
> From: Bruno Haible
> Cc: bug-gnulib@gnu.org, la...@gnus.org, 57...@debbugs.gnu.org,
> jporterb...@gmail.com
> Date: Sun, 21 Aug 2022 18:20:52 +0200
>
> I changed test-tempname.c to skip the case 1 and execute only case 2, and
> added printf statements per the attached tempname.c.diff. Then ran
Paul Eggert wrote:
> > Since this contradicts what you debugged on mingw, I ran the test 1
> > times on native Windows. Result:
> >- on 32-bit mingw, no failure.
> >- on 64-bit mingw, around 30 failures (or around 10 failures with Paul's
> > newest patch). That is, a probability of
