mingw using wrong errno definition

Chris Faylor cgf@cygnus.com
Wed Apr 5 22:21:00 GMT 2000

On Wed, Apr 05, 2000 at 08:46:03PM -0700, Ron Parker wrote:
>First a little more information.  Yesterday I did _not_ make from the root 
>directory. When I try to do a make from the root I get an error when 
>cinstall tries to compile zlib.
>-I. -I../../../../../src/winsup/cinstall/zlib  
>-I../../../../../src/winsup/cinstall/zlib/..    -g -O2 -W -Wall -mno-c
>ygwin -I../../../../src/winsup/mingw/include 
>-I../../../../src/winsup/w32api/include -c 
>Syntax error: word unexpected

Are you building this in the same directory as the sources by any chance?
That's not really supported.  It's hard to decipher all of the ../.. stuff
but it sounds like you're somewhere below your source tree somehow.

I'd suggest building this in a separate build area.  My build looks like

i686-pc-cygwin-gcc -DPACKAGE=\"zlib\" -DVERSION=\"1.1.3\" -DHAVE_UNISTD_H=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MEMCPY=1 -DHAVE_STRERROR=1 -DHAVE_UNISTD_H=1  -I. -I/cygnus/src/sourceware/winsup/cinstall/zlib  -I/cygnus/src/sourceware/winsup/cinstall/zlib/..    -g -O2 -mno-cygwin -I/cygnus/src/sourceware/winsup/mingw/include -I/cygnus/src/sourceware/winsup/w32api/include -c /cygnus/src/sourceware/winsup/cinstall/zlib/adler32.c

When you configured this did you do it from the winsup directory or from the
level above winsup?  I think it might work better if you just do it from winsup.

I have a directory called "/build" that I use to build things.
So, you'd do something like:

cd /build

>End of search list.

This means that it is not finding the winsup/mingw directory.  Do you have it checked

>And a separate question, when commit'ing a change to configure.in, do I also 
>update the configure file itself?

Yes.  Take a look at the ChangeLog and you'll see an example of this.

>I would assume so, but thought I should what ask the approved version
>of autoconf was before I overwrite a version 31.415 file with a version
>0.1a file.  ;^) I know as-yet-unreleased tools are frequently used on
>this project.

Hmm.  I'm not sure that we do use unreleased tools very often except very
recently with Mumit's gcc, but that's hardly unreleased.

I used 2.13 to regenerate configure, which I believe is the current version.
If you don't have it you should be able to pick it up at:


But the configure.in script won't allow itself to be built with anything
prior to 2.12 so you won't be able to overwrite anything.


More information about the Cygwin-developers mailing list