Hi Andre
> On 23 Jul 2025, at 08:41, Andre Vehreschild <ve...@gmx.de> wrote:
> thank you for testing. I know already about the missing <signal.h> include. It
> is also needed on FreeBSD. What's new is the <sys/types.h>. Is that really
> needed or is it transitively included by <signal.h>? Could you check by, for
> example, just grepping signal.h for it?
It is what the Linux man page says for kill()
```
KILL(2)
Linux Programmer's Manual
KILL(2)
NAME
kill - send signal to a process
SYNOPSIS
#include <sys/types.h>
#include <signal.h>
```
Actually Darwin/macOS (and presumably FreeBSD) only needs signal.h
> As "hello world" so to say test every test under
> gcc/testsuite/gfortran.dg/coarray can be used, for example get_array.f90. Most
> tests do not output anything, well, because they are tests, but they run
> within
> milliseconds usually.
>
> What did you do in the hello.f90 program?
Just a standard “hello world” but compiled and linked with the coarray shmem lib
(i.e. the code does no coarray work at all)
FWIW I tried one of Thomas’ coarray examples and it behaves the same - hangs in
the startup.
> I have never seen a hang in the init
> phase.
Unfortunately, as soon as I try to run it under a debugger - the hang
disappears .. as a hunch I’d look for a potential race condition in the startup
code ..
> I also have no system available that runs Mac OS. This will get
Maybe FX will be able to help - but I think he’s very busy too.
Iain
