net release/installer status?

Chris Faylor
Mon Mar 27 20:41:00 GMT 2000

On Mon, Mar 27, 2000 at 10:34:41PM -0600, Mumit Khan wrote:
>Corinna Vinschen <> writes:
>>FYI: I finally could cross compile cygwin1.dll on my linux box.  Ah,
>>yes, it's not only compiled but it also runs under W2K.
>>Nevertheless I have some trouble.  I have patched two Makefiles and I
>>had to configure twice in winsup.  Eventually I couldn't compile the
>>utils subdir because w32api/include isn't in the configured incude path
>The problem may actually be quite simple -- we may be lacking -nostdinc
>-I<path_to_w32ap_include> in the Makefiles.  The -B<path_to_newlib>
>only handles the newlib includes, but the w32api headers are still
>coming from your installed tree.

There *is* a -I<path_to_w32ap_include> in winsup/Makefile.common:

INCLUDES:=-I. -I$(cygwin_source)/include -I$(cygwin_source) -I$(newlib_source)/libc/sys/cygwin -I$(newlib_source)/libc/include -I$(w

AFAICT, it is being set correctly.  I see a
-I/whatever/winsup/w32api/include in my CC lines when I compile.

Or is Corinna referring to the top-level utils directory?

>I remember running into this when I had an older version of w32api
>and gcc installed, and tried an one-tree build. I should dig it
>up and submit a patch for it.

I did submit a patch to include the various include directories when
building gcc:

LIBGCC2_INCLUDES = -I$(srcdir)/../winsup/include \
        -I$(srcdir)/../winsup/cygwin/include \

This is in the sourceware gcc.

I don't have your (Mumit) sources handy but I thought we'd already gone
through this exercise with your sources, too.


More information about the Cygwin-developers mailing list