b20.1 (egcs-1.1.1): making winsup problem

Stipe Tolj tolj@uni-duesseldorf.de
Mon Feb 15 08:00:00 GMT 1999

Hi Mumit,

> > gcc -c -fno-rtti -fno-exceptions -g -O2 -Wall -Wwrite-strings       -I./inc
> lude -I. -I./newlib/libc/sys/cygwin -I./newlib/libc/include -I./config/i386 -
> nostdinc++ -o assert.o assert.cc
> This doesn't look correct. Look at the -I./newlib/libc/sys/cygwin etc
> include paths! Either configure is screwing up, or something else smells
> here. There is at the very least a missing leading "." in the newlib
> include paths.

Your absolutly right. It seems that configure screws up something. After

    updir:= $(dir $(srcdir))


    updir:= ../

within winsup/Makefile manualy the whole packages builds cleanly.

Now I'm ready to go ahead in trying to get pthreads running. Geoffrey mentioned
that the latest winsup snapshot supports a configure options caleld
--enablethreadsafe to support at least experimental thread support.

Will this include and build the pthread package or will I have to compile it from
the pthread-win32 package available at sourceware.cygnus.com?

The latest pthreads-snap-1999-01-23 claims within README to be unable to compile
under Cygwin or Mingw. I have compiled successfully the older
pthreads-snap-10-20, but when linking the example programs I get undefined
references to _beginthreadex and _endthreadex, which obviously are not supported
on Win9x systems.

May you have a clue how to get basic pthread support for Cygwin, if possible?

Thanks for assistance.

> I also recommend that you build all of this in an object directory, and
> not in the source directory. Just to keep things clean if nothing else.

What do you mean with an object directory? In other words: Where is the
difference in a source and object directory within this scope?


Stipe Tolj <tolj@uni-duesseldorf.de>

Cygwin Porting Project -- "We build UNIX on top of Windows"

Department of Economical Computer Science
University of Cologne, Germany

More information about the Cygwin-developers mailing list