Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Apr 2006 07:47:05 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        Andrew Belashov <bel@orel.ru>
Cc:        freebsd-sparc64@freebsd.org, freebsd-threads@freebsd.org
Subject:   Re: pthread_mutex_timedlock on sparc64
Message-ID:  <Pine.GSO.4.64.0604170744350.18659@sea.ntplx.net>
In-Reply-To: <44436C5B.50703@orel.ru>
References:  <20060416220250.K52948@hades.admin.frm2> <44436C5B.50703@orel.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Apr 2006, Andrew Belashov wrote:

> Hello, Joerg!
>
> Joerg Pulz wrote:
>> sorry for the cross posting but i think it is related to both lists.
>> 
>> Today i got two mails from pointyhat for ports that i maintain which seem 
>> to have problems on sparc64.
>> The relevant ports are net/gatekeeper, net/openmcu and the exact error 
>> message is:
>> /usr/local/lib/libpt_r.so: undefined reference to `pthread_mutex_timedlock'

Note that /usr/local/lib/foo is not part of FreeBSD base, so
it looks like the sparc build machine is using a non-standard
thread library.

>> There is another port net/openam which has the same problem.
>> 
>> As far as i can see, the '-pthread' argument is used and therefore this 
>> should not occur, unless there is something missing or wrong in the sparc64 
>> thread library.
>> I can't investigate this further because i have no access to a sparc64 
>> machine running any version FreeBSD.
>> 
>> Any information regarding this problem is much appreciated.
>> 
>> Kind regards
>> Joerg
>> 
>
> What about libthr library? For switching to libthr:
> # echo "libc_r.so libthr.so" >>/etc/libmap.conf

Also, some sparc64-knowledgeable person(s) need to make
libpthread work on sparc64 ;-)

-- 
DE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0604170744350.18659>