Bug 72353

Comment 1 Daniel Eischen 2004-10-05 18:07:28 UTC

On Tue, 5 Oct 2004, Ivan Voras wrote:
> Compiling monodoc (Mono documentation browsers) fails with error:
> Assertion failed: (lu->lu_myreq->lr_owner == lu), function _lock_acquire, file /usr/src/lib/libpthread/sys/lock.c, line 171.
> Abort trap (core dumped)
> *** Error code 134
>
> >How-To-Repeat:
> $ wget http://www.go-mono.com/archive/1.0.2/monodoc-1.0.2.tar.gz
> $ tar xzf monodoc-1.0.2.tar.gz
> $ cd monodoc-1.0.2
> $ ./configure
> $ make
>
> >Fix:
> none, but http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/70430 works (old version).
> More info here: http://lists.freebsd.org/pipermail/freebsd-gnome/2004-August/007781.html

This suggests you are using /etc/libmap.conf to map everything to libc_r.
Is this still true?  If you have any binaries or libraries that link to
libc_r and are trying to build something to work with libpthread, you
need to use libmap.conf to map libc_r to libpthread (the opposite of
what you had done before).  Please try to repeat the problem with
an /etc/libmap.conf containing the following entries:

        libc_r.so.5             libpthread.so.1
        libc_r.so               libpthread.so

-- 
Dan Eischen

Daniel Eischen wrote:
> 
> This suggests you are using /etc/libmap.conf to map everything to libc_r.
> Is this still true?  If you have any binaries or libraries that link to

No, my libmap.conf maps everything to libpthread (has been since 
RELENG_5, and not a single problem there).

As I said in the pr, the thing that the port skeleton (the first URL) 
does works to build version 1.0 without errors, only the newer version, 
1.0.2, for which I don't have the port skeleton, dies.

Comment 3 Daniel Eischen 2004-10-05 21:44:14 UTC

On Tue, 5 Oct 2004, Ivan Voras wrote:

> Daniel Eischen wrote:
> >
> > This suggests you are using /etc/libmap.conf to map everything to libc_r.
> > Is this still true?  If you have any binaries or libraries that link to
>
> No, my libmap.conf maps everything to libpthread (has been since
> RELENG_5, and not a single problem there).
>
> As I said in the pr, the thing that the port skeleton (the first URL)
> does works to build version 1.0 without errors, only the newer version,
> 1.0.2, for which I don't have the port skeleton, dies.

-bash-2.05b$ ./configure
checking build system type... i386-unknown-freebsd6.0
checking host system type... i386-unknown-freebsd6.0
checking target system type... i386-unknown-freebsd6.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gacutil... no
configure: error: No gacutil tool found

What is gacutil?

-- 
Dan Eischen

Daniel Eischen wrote:

> -bash-2.05b$ ./configure
> checking build system type... i386-unknown-freebsd6.0
> checking host system type... i386-unknown-freebsd6.0
> checking target system type... i386-unknown-freebsd6.0
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for gacutil... no
> configure: error: No gacutil tool found
> 
> What is gacutil?

Oh, sorry, I should have mantioned you need lang/mono port installed to 
build monodoc, and probably x11-toolkits/gtk-sharp also.

Comment 5 Daniel Eischen 2004-10-06 14:46:16 UTC

On Wed, 6 Oct 2004, Ivan Voras wrote:

> Daniel Eischen wrote:
>
> > -bash-2.05b$ ./configure
> > checking build system type... i386-unknown-freebsd6.0
> > checking host system type... i386-unknown-freebsd6.0
> > checking target system type... i386-unknown-freebsd6.0
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for gawk... no
> > checking for mawk... no
> > checking for nawk... nawk
> > checking whether make sets $(MAKE)... yes
> > checking whether to enable maintainer-specific portions of Makefiles... no
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking for gacutil... no
> > configure: error: No gacutil tool found
> >
> > What is gacutil?
>
> Oh, sorry, I should have mantioned you need lang/mono port installed to
> build monodoc, and probably x11-toolkits/gtk-sharp also.

I installed monodoc, not gtk-sharp.  What does 'pkg_which gacutil'
show?

-- 
Dan Eischen

Daniel Eischen wrote:

>>>What is gacutil?
>>
>>Oh, sorry, I should have mantioned you need lang/mono port installed to
>>build monodoc, and probably x11-toolkits/gtk-sharp also.
> 
> 
> I installed monodoc, not gtk-sharp.  What does 'pkg_which gacutil'
> show?
> 

~> pkg_which gacutil
mono-1.0_1

Comment 7 Tom McLaughlin 2007-02-05 01:37:53 UTC

State Changed
From-To: open->closed

The majority of Mono's threading issues have been ironed out in the past 
two years and I don't recall the last time I saw an error like this.