Pete French wrote:
>>The real bug does indeed lie in the internal initialization process of the
>>FreeBSD libpthread library. In this case when libobjc is not excplitly linked
>
>
> ... this is probably the root cause of the issue I am seeing as well.
>
>
>>I'll leave it up to the -make maintainers to decide what to do. My current
>>tendency is to close this bug as invalid at least until someone verifies that
>>the issue exists with released versions of FreeBSD. And even then a
>>workaround should probably be done in libobjc (which seems to be installed by
>>FreeBSD but if libobjc needs updating you might as well update libpthread
>>instead and fix the bug properly).
>
>
> What would the actual fix to libpthread be in this case ? I can submit
> a PR for this and try and get it fixed in FreeBSD.
>
IMHO, to guard all public API functions of libpthread internally with:
if (_thr_initial == NULL)
_libpthread_init(NULL);
as the have already done for some of them.
Cheers,
David
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
