Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.1.0.14.2.20021118083517.00fd5d58@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Mon, 18 Nov 2002 08:48:43 -0800
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	Re: Thread.start called but threads not available
In-Reply-To:	<5.0.2.1.2.20021118165822.01975f08@brest.ifremer.fr>
Mime-Version:	1.0

Jacques,

I don't know how much of the Gnu Compiler for Java shares with the Gnu C 
and C++ compilers, but why do you assume that availability of threading in 
"gcc" implies that Java threads will be available via "gcj?"


Moreover, why are you using "gcj" at all? Is there a reason the Sun J2SDK 
is unacceptable? It is far more mature and is eminently usable under 
Cygwin. I do a lot of Java work these days, so I'd be interested in hearing 
what is the appeal of gcj.


The following paragraph was included in Chris Faylor's the release 
announcement for gcc 3.2.1 (Subject: "[ANNOUNCEMENT] Updated/new: gcc 
3.2-1, gcc2-2.95.3-10, gcc-mingw-3.2-20020817-1"; Date: "Tue, 15 Oct 2002 
17:06:20 -0400 (EDT)"):

>gcc 3.2-1 contains gcj which various people have reported as being either 
>functional or broken.  I'll probably strip it out of future releases and 
>offer it separately.


It seems that under Cygwin at least, "gcj" might not be ready for 
production use.


Randall Schulz
Mountain View, CA USA


At 08:04 2002-11-18, Jacques Grelet wrote:
>Hi,
>
>I have compiled a java source with gcj under cygwin on win2000:
>gcj -o serveur --main=serveur serveur.java
>The programme gave the following message about threads not available, but 
>gcc seems to be compiled with threads enable.
>Why ?
>
>Thanks for help,
>
>[jgrelet]:/s/outils/sources/serveur> ./serveur 10183
>
>Serveur version java 1.1 port UDP : 10183
>
>
>Exception in thread "main" java.lang.InternalError: Thread.start called 
>but threads not available
>
>[jgrelet]:/s/outils/sources/serveur> gcc -v
>Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs
>Configured with: /netrel/src/gcc-3.2-3/configure 
>--enable-languages=c,c++,f77,java --enable-libgcj --enable-threads=posix 
>--with-system-zlib --enable-nls --without-included-gettext 
>--enable-interpreter --disable-sjlj-exceptions 
>--disable-version-specific-runtime-libs --enable-shared 
>--build=i686-pc-linux --host=i686-pc-cygwin --target=i686-pc-cygwin 
>--enable-haifa --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc 
>--libdir=/usr/lib --includedir=/nonexistent/include --libexecdir=/usr/sbin
>Thread model: posix
>gcc version 3.2 20020927 (prerelease)
>
>Source code is :
>...
>
>
>Jacques Grelet
>
>Email: Jacques DOT Grelet AT ird DOT fr


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -