This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Current build failure when libgcj is enabled on i386-unknown-freebsd4.2
- To: rittle at rsch dot comm dot mot dot com
- Subject: Re: Current build failure when libgcj is enabled on i386-unknown-freebsd4.2
- From: Jeff Sturm <jsturm at one-point dot com>
- Date: Wed, 25 Apr 2001 00:31:40 -0700 (PDT)
- cc: java at gcc dot gnu dot org
On Tue, 24 Apr 2001, Loren James Rittle wrote:
> During the configuration of boehm-gc, it doesn't detect the mismatch
> between the configuration requested and the fact that there is no code
> path for generic POSIX threads. It appears that this version of
> boehm-gc only supports POSIX threads on some platforms even though
> additional platforms support the required POSIX pthread_* API.
Yep. The GC needs to know how to find all threads, plus suspend/restart
individual threads. Unfortunately that can't be done with generic
pthreads, so there is a port for each supported OS.
For the rest you can configure threads without GC, or GC without
threads. I consider it a bug that boehm-gc/configure doesn't abort if you
attempt to build with posix threads on an unsupported target. Here's a
suggestion:
diff -u -p -r1.21 configure.in
--- configure.in 2000/12/30 12:18:38 1.21
+++ configure.in 2001/04/25 07:24:35
@@ -60,7 +60,7 @@ if test "$THREADS" = yes; then
;;
*)
# For now.
- THREADS=none
+ THREADS=posix
;;
esac
fi
@@ -84,6 +84,9 @@ case "$THREADS" in
;;
*-*-irix*)
AC_DEFINE(IRIX_THREADS)
+ ;;
+ *)
+ AC_MSG_ERROR(posix threads not yet supported on $host)
;;
esac
THREADLIBS=-lpthread