Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <A01E735D4940D311A3850090275559330BA938@NTSRV02>
From: Erik Hensema <erik DOT hensema AT group2000 DOT nl>
To: "'Cygwin mailing list'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Q: pthreads, crosscompiling
Date: Tue, 7 Sep 1999 13:21:15 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

I'm fairly new to the Cygwin project, and I've got some questions. 

I know the pthreads implementation isn't quite stable right now. Does
anybody know how this is going to be in the future? I'm a C programmer, so
optionally I can help develop the pthreads implementation, but I haven't got
a lot of time to do so.

Related to this: I can't compile the latest snapshot of the Cygwin source.
I've downloaded cygwin-src-19990905_tar.gz, unpacked it, and ran configure ;
make. It stops with the message:

gcc -c -fno-rtti -fno-exceptions  -g -O2 -Wall -Wwrite-strings
-I./include
 -I. -I./../newlib/libc/sys/cygwin -I./../newlib/libc/include
-I./config/i386 -n
ostdinc++ -o wait.o wait.cc
gcc -c -fno-rtti -fno-exceptions  -g -O2 -Wall -Wwrite-strings
-I./include
 -I. -I./../newlib/libc/sys/cygwin -I./../newlib/libc/include
-I./config/i386 -n
ostdinc++ -o window.o window.cc
dlltool --as=as -k --dllname kernel32.dll --output-lib libkernel32.a --def
sysde
f/kernel32.def
dlltool --as=as -k --dllname advapi32.dll --output-lib libadvapi32.a --def
sysde
f/advapi32.def
make[1]: *** No rule to make target `../newlib/libc.a', needed by
`new-cygwin1.d
ll'.  Stop.
make: *** [all-target-winsup] Error 2

I think it's cause by the absence of a Makefile in i686-pc-cygwin32/newlib,
and configure doesn't run from that directory:
gorgo:~/src/i686-pc-cygwin32/newlib$ ./configure
loading cache ./config.cache
configure: error: can not find install-sh or install.sh in .. ./..


A completely different question: right now we're developing Unix software on
Solaris, and our complete version-control system is running on the Sun. Is
it still practical to setup a crosscompiler on Solaris to generate NT
binaries?

The project I'm working on involves extensive use of threads, tcp/ip and
Unix domain sockets. All source is beleived to be quite Posix complient.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com