Sent by Daniel Eischen:
No, I simply meant that you saw it was returning bad system
call from sem_init/ksem_init.
Instead, I suspected, that it is the OpenMP, that's at fault. I'm sorry
for failing to live up to your expectations of a true FreeBSD user.
A little investigation would have turned up the reason. If you want
to debate whether or
not P1003_1B_SEMAPHORES should be standard, that is another
issue, which I might actually agree with.
Well, I'm sure, the debate on including P1003_1B_SEMAPHORES by default
has already raged before...
No, what I was suggesting, was that sem_init -- not the system call, but
the C-function -- should be more intelligent in detecting such
situations and reporting them instead of crashing...
Either the C-function, or, maybe, the no-op implementation of
(k)sem_init in the kernel ought to have told me (even if only in the
kernel log), that I need to kldload sem and refer to the man-page.
That's what well-integrated Operating Systems do, anyway...
-mi
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
