On Sat, Mar 22, 2008 at 6:14 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > Actually, the problem was tracked down to be inside uic. When built on
> > (and Leslie's) 7.0 "upgraded" from 6.x system, uic does not link to
> > libthr.so, while in a newly-installed 7.0 it does.
> It should not be linking (directly) to libthr at all, it should be
> linking to libpthread (which is a symlink to it).
Yes, it does link to -lpthread, but ldd tells different things on newly
installed 7.0 and 7.0 upgraded from 6.2... I don't know if it's the reason,
that was Mel's guess (
> > So one of people here (Mel) asked to provide the actual commandline used
> > link uic (see this for reference:
> > http://docs.freebsd.org/cgi/mid.cgi?200803161912.18248.fbsd.questions),
> > which is what I did.
> It links to libqt-mt and presumably gets its thread library from there,
> so the question extends there.
Well, the commandline used to build libqt-mt is included in the log and it
also links to -pthread...
> > Log of the actual "mutex unlock failure" error was already posted in
> > list, it's here: http://docs.freebsd.org/cgi/mid.cgi?47D8DBC0.3010106
> OK, I suppose I was confused because you posted this under a new subject
> instead of as a followup to the earlier messages, so context was lost
> from your mails.
Ok, my fault - should have taken the same subject :-)
If you are willing to further investigate the issue, I can provide more
details about my system or even give you the shell access.
Dmitry RCL Rekman
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"