GCC-build errors

Dan Nicholson dbn.lists at gmail.com
Wed Sep 20 13:35:49 PDT 2006

On 9/20/06, Luca <liliana.perossa at fastwebnet.it> wrote:
> I'm recompiling gcc-4.1.1 in order to user NVIDIA-SDK, but I'm having an
> error I'm trying to solve.
> Gcc-4.1.1 configure so:
> "../gcc-4.1.1/configure --prefix=/usr --libexecdir=/usr/lib
> --enable-shared --enable-threads=posix --enable-__cxa_atexit
> --enable-clocale=gnu
> --enable-languages=c,ada,c++,fortran,java,objc,obj-c++,treelang
> --with-mpfr=usr --with-gmp=/usr --with-system-zlib --with-x
> --enable-java-awt=gtk,xlib --enable-gtk-cairo --enable-java-gc=boehm
> --with-libart-prefix=/usr --without-system-unwind
> --enable-libstdcxx-allocator=mt --enable-libstdcxx-debug".
> While making in java I receive this error:
> "./gcj-dbtool -n classmap.db || touch classmap.db
> Unexpected error from pthread_mutex_trylock
> /bin/sh: line 1: 15360 Aborted                ./gcj-dbtool -n classmap.db
> make[3]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libjava'
> make[2]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libjava'
> make[1]: Leaving directory `/sources/gcc-build'"

Two things I noticed. First, I think that the the error is hrom the
boehm garbage collector. From boehm-gc/pthread_support.c:

        switch(pthread_mutex_trylock(lock)) {
            case 0:
#               ifdef LOCK_STATS
#               endif
            case EBUSY:
                ABORT("Unexpected error from pthread_mutex_trylock");

So, you could try removing --enable-java-gc=boehm. However, I think
you can ignore the error. Here's from libjava/Makefile.am:

## The .db file.  This rule is only used for native builds, so it is
## safe to invoke gcj-dbtool.
$(db_name): gcj-dbtool$(EXEEXT)
## In case it exists already.
        @rm -f $(db_name)
## We don't actually care if it fails -- if it does, just make an
## empty file.  This is simpler than trying to discover when mmap is
## not available.
        ./gcj-dbtool -n $(db_name) || touch $(db_name)

Does make return unsuccessfully?


More information about the blfs-support mailing list