docker container for building cygwin on Linux

Hi list, I just published a docker image with all the necessary build dependencies (except for dumper.exe) for building cygwin. We are using it to compile our WinDRBD driver and with a few additional packages it was possible to compile cygwin (newlib-cygwin) as well. This is how to obtain it

Re: Problem building cygwin-3_1_7-release tagged newlib.

On 2020-10-10 12:39, Ken Brown wrote: On 10/10/2020 3:22 PM, Kaz Kylheku (Cygwin) via Cygwin wrote:  4896 |   typedef struct _MEM_ADDRESS_REQUIREMENTS {   |  ^ This looks like a clash between the installed toolchain header and the one in the winsup

Re: Problem building cygwin-3_1_7-release tagged newlib.

On 10/10/2020 3:22 PM, Kaz Kylheku (Cygwin) via Cygwin wrote: Hi, I'm trying to build the 3.1.7 tagged newlib. It runs into this problem: c++wrap -O2 -g -fno-rtti -fno-exceptions -fno-use-cxa-atexit -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0 -MMD

Problem building cygwin-3_1_7-release tagged newlib.

Hi, I'm trying to build the 3.1.7 tagged newlib. It runs into this problem: c++wrap -O2 -g -fno-rtti -fno-exceptions -fno-use-cxa-atexit -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0 -MMD -Wimplicit-fallthrough=5 -Werror -fmerge-constants -ftracer -c -

building cygwin packages

Hello, I need to tweak and build some packages that depend on many others. Figuring out the recursive dependencies and build order is tedious. What is the easiest way to simply download and build *all* cygwin packages? I have disk space and cpu time. First, I would do 32 bit, then 64 bit. Tia,

Re: Building Cygwin DLL

On 2013-07-12 02:33, Alexey Pavlov wrote: When trying building Cygwin DLL with cygport under Cygwin I have error: Actually, that error is in building the LSA module: x86_64-w64-mingw32-gcc -g -ggdb -O2 -pipe -fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/build=/usr/src/debug/cygwin-1.7.21-6

Building Cygwin DLL

Hi, all! When trying building Cygwin DLL with cygport under Cygwin I have error: make[3]: Entering directory `/home/alexey/cygwin-1.7.21-6/build/i686-pc-cygwin/winsup/cygwin' /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/gendef --cpu=i686 --output-def=cygwin.def --tlsoffsets=/home/a

Re: Error building cygwin-1_7_18-release from cvs

On Mon, Jul 08, 2013 at 05:58:40PM +1000, Shaddy Baddah wrote: >On 2013-07-08 17:51+1000, Shaddy Baddah wrote: >> I am encountering an error build cygwin-1_7_18-release from CVS. >> >> Before I plunge into that, it might be wise to address why I would want >> to do that in the first place. >> >> I

Re: Error building cygwin-1_7_18-release from cvs

Hi, On 2013-07-08 17:51+1000, Shaddy Baddah wrote: I am encountering an error build cygwin-1_7_18-release from CVS. Before I plunge into that, it might be wise to address why I would want to do that in the first place. I apply a local patch for my own use to the DLL to enable sharing of the in

Re: Problem building Cygwin from CVS

On 12/17/2012 4:53 AM, Corinna Vinschen wrote: Yes, don't try to build tcl/tk from the sourceware repo. It's old, it's unmaintained. Corinna Ok, thanks. Are there any other parts of the CVS source tree that I should be wary of? -- Chris J. Breisch -- Problem

Re: building cygwin from cvs

On Dec 17 11:00, marco atzeri wrote: > Corinna, > trying to build the cygwin dll from cvs with just > configure and build stop here : > > checking whether we are cross compiling... no > checking for suffix of object files... (cached) o > checking whether we are using the GNU C compiler... (cached)

building cygwin from cvs

Corinna, trying to build the cygwin dll from cvs with just configure and build stop here : checking whether we are cross compiling... no checking for suffix of object files... (cached) o checking whether we are using the GNU C compiler... (cached) yes checking whether gcc -L/pub/cygwin/cvs/build

Re: Problem building Cygwin from CVS

On Dec 15 15:20, Chris J. Breisch wrote: > I'm having difficulty building the Cygwin tree. My cygcheck.out is > attached. > > I have the "Default" Cygwin set up, with the following additions: > gcc4, make, perl, cocom, bison, flex, vim, m4, and libiconv. > > I've checked the archives for similar

Problem building Cygwin from CVS

I'm having difficulty building the Cygwin tree. My cygcheck.out is attached. I have the "Default" Cygwin set up, with the following additions: gcc4, make, perl, cocom, bison, flex, vim, m4, and libiconv. I've checked the archives for similar issues and have found none. After my research, it

Re: "Bad address" error while building cygwin with make -j2

I can agree all works fine ... good job I wish all a Merry Christmas and a Happy New Year. Heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin

Re: "Bad address" error while building cygwin with make -j2

On Thu, Dec 22, 2011 at 11:47:54AM -0500, Chris Sutcliffe wrote: >On 18 December 2011 18:30, Chris Sutcliffe wrote: >> Tested with the 20111218 snapshot and the vim build now fails with as >> a result of a different issue: >> >> make[1]: *** read jobs pipe: Resource temporarily unavailable. ?Stop.

Re: "Bad address" error while building cygwin with make -j2

On 18 December 2011 18:30, Chris Sutcliffe wrote: > Tested with the 20111218 snapshot and the vim build now fails with as > a result of a different issue: > > make[1]: *** read jobs pipe: Resource temporarily unavailable.  Stop. > make[1]: *** Waiting for unfinished jobs > make[1]: Leaving dire

Re: "Bad address" error while building cygwin with make -j2

Chris Sutcliffe writes: > > Tested with the 20111218 snapshot and the vim build now fails with as > a result of a different issue: > > make[1]: *** read jobs pipe: Resource temporarily unavailable. Stop. > make[1]: *** Waiting for unfinished jobs > make[1]: Leaving directory `/usr/src/vim/s

Re: "Bad address" error while building cygwin with make -j2

On 16 December 2011 21:55, Chris Sutcliffe wrote: > On 16 December 2011 16:05, Chris Sutcliffe wrote: >> Things improved with the 20111216 snapshot, in that vim build >> completed, but something still isn't quite right: >> >> make[1]: Leaving directory `/usr/src/vim/src' >> make: INTERNAL: Exiting

Re: "Bad address" error while building cygwin with make -j2

On 16 December 2011 16:05, Chris Sutcliffe wrote: > Things improved with the 20111216 snapshot, in that vim build > completed, but something still isn't quite right: > > make[1]: Leaving directory `/usr/src/vim/src' > make: INTERNAL: Exiting with 1 jobserver tokens available; should be 4! Just tes

Re: "Bad address" error while building cygwin with make -j2

On 15 December 2011 20:11, Chris Sutcliffe wrote: > I'm not sure if the 20111214 snapshot was supposed to address this > issue, but I'm continuing to experience the issue as well: > > csutclif@bmotec3017201lt:[~] $ uname -a > CYGWIN_NT-5.1 BMOTEC3017201LT 1.7.10s(0.255/5/3) 20111214 15:56:36 i686 C

Re: "Bad address" error while building cygwin with make -j2

On 15 December 2011 02:16, Heiko Elger wrote: > I tested it - still same issue! > > *** snip snp snip ** > $ uname -a > CYGWIN_NT-6.1-WOW64 PCFX061 1.7.10s(0.255/5/3) 20111214 15:56:36 i686 Cygwin > > $ make -j2 > make: *** read jobs pipe: Bad address.  Stop. > make: *** Waiting for unfinish

Re: "Bad address" error while building cygwin with make -j2

Heiko Elger writes: > > Christopher Faylor writes: > > > > > It's easy to reproduce. It's the result of changes I made in recent > snapshots > > to handle signals in threads. > > > that sounds good. > > Is it easy to fix it! > Is it fixed in latest snapshot 20111214? I tested it - still sa

Re: "Bad address" error while building cygwin with make -j2

Christopher Faylor writes: > > It's easy to reproduce. It's the result of changes I made in recent snapshots > to handle signals in threads. > that sounds good. Is it easy to fix it! Is it fixed in latest snapshot 20111214? I read somthing about signal handling in ChangeLog. regars Heiko

Re: "Bad address" error while building cygwin with make -j2

On Wed, Dec 14, 2011 at 07:06:04PM +0100, marco atzeri wrote: >On 12/14/2011 4:22 PM, Heiko Elger wrote: > >> make: *** read jobs pipe: Bad address. Stop. >> make: *** Waiting for unfinished jobs >> make: INTERNAL: Exiting with 1 jobserver tokens available; should be 2! > >I saw the same issue

Re: "Bad address" error while building cygwin with make -j2

On 12/14/2011 1:06 PM, marco atzeri wrote: On 12/14/2011 4:22 PM, Heiko Elger wrote: make: *** read jobs pipe: Bad address. Stop. make: *** Waiting for unfinished jobs make: INTERNAL: Exiting with 1 jobserver tokens available; should be 2! I saw the same issue building another program on

Re: "Bad address" error while building cygwin with make -j2

On 12/14/2011 4:22 PM, Heiko Elger wrote: make: *** read jobs pipe: Bad address. Stop. make: *** Waiting for unfinished jobs make: INTERNAL: Exiting with 1 jobserver tokens available; should be 2! I saw the same issue building another program on W7/64 I noticed that it happens on very hi

"Bad address" error while building cygwin with make -j2

Hello, I spend much of time in reproducing a testcase - I hope that this problem can be reproduced by others too. While looking for a testcase for reproducing our other problem with "Bad address" errors - I tried to build cygwin snapshot 20111213. I did a fresh cygwin intallation for this test.

Syntax error from 'mingw' script while building cygwin DLL from source

I was compiling the cygwin DLL from the latest src package 1.7.9-1 following FAQ 6.18 as always. After a lot of successful activity in the 'make' step, I see: [...] ar cru libautomode.a automode.o ar cru libbinmode.a binmode.o ar cru libtextmode.a textmode.o ar cru libtextreadmode.a textreadmode.o

Compiler for building Cygwin

It should probably noted on the website that building Cygwin requires the gcc4 package. For example, here: http://cygwin.com/faq.html#faq.programming.building-cygwin -Edward -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq

problem finding 'i686-pc-mingw32' directory when building cygwin from source

I was interested in building the cygwin system from source because I wanted to make some customizations. I followed the instructions in the FAQ for building cygwin: http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin Well into the build, I see the following error

Re: character set for building cygwin documentation ?

On Wed, 2010-06-16 at 18:35 +, Marco Atzeri wrote: > Hi, > trying to build last snapshot, every thing go fine, except > documentation. > > cd cygwin-ug-net && docbook2pdf ../cygwin-ug-net.sgml > Using catalogs: /etc/sgml/xml-docbook-4.5.cat > Using stylesheet: /usr/share/sgml/docbook/utils-0.

character set for building cygwin documentation ?

Hi, trying to build last snapshot, every thing go fine, except documentation. cd cygwin-ug-net && docbook2pdf ../cygwin-ug-net.sgml Using catalogs: /etc/sgml/xml-docbook-4.5.cat Using stylesheet: /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print Working on: /pub/snapshots/cygwin-snapsh

Building cygwin src dll help

I'm building the cygwin source and having a bit of trouble with the following. /bin/sh ../../.././winsup/cygwin/speclib /home/cwingert/cygwin-1.5.24-2/i686-pc-cygwin/winsup/cygwin/libpthread.a "nm" "ar" /home/cwingert/cygwin-1.5.24-2/i686-pc-cygwin/winsup/cygwin/libcygwin.a pthread.o thread.o in

Re: Error building cygwin DLL from CVS HEAD

On Dec 20 20:35, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to David Rothenberger on 12/20/2006 2:06 PM: > > I'm encountering an error while trying to build dumper.cc. This is with > > the latest CVS HEAD. > > > > In file included from /usr/src/cygwin/src/wi

Re: Error building cygwin DLL from CVS HEAD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to David Rothenberger on 12/20/2006 2:06 PM: > I'm encountering an error while trying to build dumper.cc. This is with > the latest CVS HEAD. > > In file included from /usr/src/cygwin/src/winsup/utils/dumper.cc:16: > /usr/src/cygwin/src/incl

Error building cygwin DLL from CVS HEAD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'm encountering an error while trying to build dumper.cc. This is with the latest CVS HEAD. In file included from /usr/src/cygwin/src/winsup/utils/dumper.cc:16: /usr/src/cygwin/src/include/elf/external.h:248: error: `ATTRIBUTE_PACKED' does not nam

Re: Building Cygwin

"Jerry D. Hedden" wrote: > I downloaded the source for cygwin-1.5.19-4, and successfully compiled > it using: > > ./configure > make You really should do a VPATH build as instructed in . > What settings do I nee

Building Cygwin

I downloaded the source for cygwin-1.5.19-4, and successfully compiled it using: ./configure make My interest was in the ps command. It runs fine, but when I looked at the size of the executable: 146 cygwin-1.5.19-4 > ls -l i686-pc-cygwin/winsup/utils/ps.exe -rwxr-xr-x 1 jhedden

Re: Building Cygwin from CVS

aq.programming.building-cygwin > >I forgot to mention, I also pointed the FAQ link in cvs.html directly >there, and simplified the FAQ entry so it should be more >straightforward for first-timers. (For example, I got rid of the "how >to use tar on a src tarball" since I doub

Re: Building Cygwin from CVS

nd simplified the FAQ entry so it should be more straightforward for first-timers. (For example, I got rid of the "how to use tar on a src tarball" since I doubt people who can't figure out tar should be building Cygwin. Or at least they should be doing it from CVS!) -- Unsubscr

Re: Building Cygwin from CVS

On 1/26/06, Corinna Vinschen wrote: > On Jan 26 13:44, Christopher Faylor wrote: > > On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote: > > >On Jan 25 20:41, Joshua Daniel Franklin wrote: > > >>I've added this info to > > >>http://cygwin.com/faq/faq.programming.html#faq.programming.b

Re: Building Cygwin from CVS

On Jan 26 13:44, Christopher Faylor wrote: > On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote: > >On Jan 25 20:41, Joshua Daniel Franklin wrote: > >>I've added this info to > >>http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin > >>and I'd like to put it in a

Re: Building Cygwin from CVS

On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote: >On Jan 25 20:41, Joshua Daniel Franklin wrote: >>On 1/20/06, Brian Dessent wrote: >>>Joshua Daniel Franklin wrote: >>> gcc make binutils cocom dejagnu >>> >>>gcc depends on binutils, so there's no need to list it as requirement.

Re: Building Cygwin from CVS

On Jan 25 20:41, Joshua Daniel Franklin wrote: > On 1/20/06, Brian Dessent wrote: > > Joshua Daniel Franklin wrote: > > > > > gcc make binutils cocom dejagnu > > > > gcc depends on binutils, so there's no need to list it as requirement. > > Perl is used in the build process as well. > > > > http://

Re: Building Cygwin from CVS

On 1/20/06, Brian Dessent wrote: > Joshua Daniel Franklin wrote: > > > gcc make binutils cocom dejagnu > > gcc depends on binutils, so there's no need to list it as requirement. > Perl is used in the build process as well. > > http://cygwin.com/ml/cygwin/2005-01/msg01266.html Thanks Brian, I think

Re: Building Cygwin from CVS

Joshua Daniel Franklin wrote: > gcc make binutils cocom dejagnu gcc depends on binutils, so there's no need to list it as requirement. Perl is used in the build process as well. http://cygwin.com/ml/cygwin/2005-01/msg01266.html Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe

Re: Building Cygwin from CVS

On Fri, Jan 20, 2006 at 10:21:35AM +0100, Corinna Vinschen wrote: >On Jan 20 09:10, Cliff Hones wrote: >> Christopher Faylor wrote: >> > Before we do that can we please find out WHAT is actually wrong? There >> > is no description of the problem beyond the above. I run the testsuite >> > several

RE: Building Cygwin from CVS

Joshua Daniel Franklin wrote: > > I think I'd tried to come up with a list before but never figured it > out since I'd > long ago installed what was needed. Is this a complete enough list? > > gcc make binutils cocom dejagnu > > This might even be worth adding to a winsup/README file. I bel

Re: Building Cygwin from CVS

On Jan 20 09:10, Cliff Hones wrote: > Christopher Faylor wrote: > > Before we do that can we please find out WHAT is actually wrong? There > > is no description of the problem beyond the above. I run the testsuite > > several times a day by cd'ing to winsup/testsuite so I know that works. > > Let

Re: Building Cygwin from CVS

Christopher Faylor wrote: > On Thu, Jan 19, 2006 at 08:53:26PM -0800, Joshua Daniel Franklin wrote: > >>> . The FAQ info describing how to run the tests is wrong. It worked for >>>me when I ran "make check" in the i686-pc-cygwin/winsup subdirectory of >>>my build directory. >> >>OK, I'll

Re: Building Cygwin from CVS

On Thu, Jan 19, 2006 at 08:53:26PM -0800, Joshua Daniel Franklin wrote: >> . The FAQ info describing how to run the tests is wrong. It worked for >> me when I ran "make check" in the i686-pc-cygwin/winsup subdirectory of >> my build directory. > >OK, I'll fix that. Before we do that can

Re: Building Cygwin from CVS

On 1/18/06, Cliff Hones wrote: > It's rather a long time since I tried building my own cygwin from CVS. With > the new release out, I thought I'd give it a try, as I imagine HEAD is very > close to 1.5.19-2. I followed the instructions in the FAQ: > http://cygwin.com/faq/faq.programming.html

RE: Building Cygwin from CVS

Dave Korn wrote: > Hmm. My local copy of devices.cc regenerated itself today as well, > although I didn't notice it fly past in the build. Mystery solved. Cgf updated devices.h and regenerated devices.cc back in December, but overlooked doing the regenerate when he reverted the change the

RE: Building Cygwin from CVS

Brian Dessent wrote: > Cliff Hones wrote: > >> Well, maybe it is a timestamp problem, but the make did fail trying to >> regenerate devices.cc using the gendevices script. After I'd installed >> cocom it worked, and overwrote devices.cc in the src/winsup/cygwin >> directory. > > That does sound

Re: Building Cygwin from CVS

Cliff Hones wrote: > Well, maybe it is a timestamp problem, but the make did fail trying to > regenerate > devices.cc using the gendevices script. After I'd installed cocom it worked, > and overwrote devices.cc in the src/winsup/cygwin directory. That does sound like a timestamp issue then.

Re: Building Cygwin from CVS

Corinna Vinschen wrote: > Do you want to write a few words yourself and send an appropriate docs > patch to the cygwin-patches list? You know, http://cygwin.com/acronyms#PTC If anyone feels like rewording that section, it might be a good time to mention the peculiarities of the sourceware CVS mo

Re: Building Cygwin from CVS

Brian Dessent wrote: > Cliff Hones wrote: > >> . It would be useful to mention in the FAQ which packages need to be >> installed >>to perform the build. I expect everyone will realise make, gcc, binutils >> etc. >>are required, but I found I needed cocom (for shilka) which I'd not come

Re: Building Cygwin from CVS

Dave Korn wrote: > Cliff Hones wrote: > >> . When I ran the tests, I got five unexpected failures (devdsp, >>msgtest, pthread-cancel1, semtest and shmtest). Is this to >>be expected :-). > > Is the smiley there to indicate that you already understand perfectly well > that these tests

Re: Building Cygwin from CVS

Cliff Hones wrote: > . It would be useful to mention in the FAQ which packages need to be > installed > to perform the build. I expect everyone will realise make, gcc, binutils > etc. > are required, but I found I needed cocom (for shilka) which I'd not come > across > before, an

RE: Building Cygwin from CVS

Cliff Hones wrote: > > . When I ran the tests, I got five unexpected failures (devdsp, > msgtest, pthread-cancel1, semtest and shmtest). Is this to > be expected :-). Is the smiley there to indicate that you already understand perfectly well that these tests would require cygserver

Re: Building Cygwin from CVS

On Jan 18 18:28, Cliff Hones wrote: > It's rather a long time since I tried building my own cygwin from CVS. With > the new release out, I thought I'd give it a try, as I imagine HEAD is very > close to 1.5.19-2. I followed the instructions in the FAQ: > http://cygwin.com/faq/faq.programming.

Building Cygwin from CVS

It's rather a long time since I tried building my own cygwin from CVS. With the new release out, I thought I'd give it a try, as I imagine HEAD is very close to 1.5.19-2. I followed the instructions in the FAQ: http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin A few

Configure error building cygwin

All, Discussions of various configure-related errors on the list today reminded me of something I ran into last week when trying to rebuild the cygwin DLL. After syncing with CVS, the configure stage of a clean rebuild results in the following error. Source has been checked out into src, configu

Re: Problems building Cygwin CVS HEAD

Apologies to all, this got sent to the wrong list by mistake. Please ignore. Igor On Tue, 13 Jul 2004, Igor Pechtchanski wrote: > Hi, > > I'm getting the following error building Cygwin CVS HEAD: > > c++ -L/usr/src/cygwin-cvs/build/i686-pc-cygwin/winsup > -L/u

Problems building Cygwin CVS HEAD

Hi, I'm getting the following error building Cygwin CVS HEAD: c++ -L/usr/src/cygwin-cvs/build/i686-pc-cygwin/winsup -L/usr/src/cygwin-cvs/build/i686-pc-cygwin/winsup/cygwin -L/usr/src/cygwin-cvs/build/i686-pc-cygwin/winsup/w32api/lib -isystem /usr/src/cygwin-cvs/src/winsup/include -is

More "vague assertions" (RE: Problems building cygwin from source)

> From: Christopher Faylor > Sent: Wednesday, November 05, 2003 2:50 PM > On Wed, Nov 05, 2003 at 12:36:46PM +0100, Hannu E K Nevalainen wrote: > >> From: Peter J. Stieber > >> I think I foolishly picked this up from some misinformation in > >> the mailing > >> list thread "Can't build cygwin fro

Re: Problems building cygwin from source

On Wed, Nov 05, 2003 at 12:36:46PM +0100, Hannu E K Nevalainen wrote: >> From: Peter J. Stieber >> Sent: Wednesday, November 05, 2003 12:37 AM > > >> > ../src/configure --prefix=/usr/install --enable-debugging -v >> >^ >> > no 'winsup' >> >> Thanks Chris, >> >> I think I foolishly picked

RE: Problems building cygwin from source

> From: Peter J. Stieber > Sent: Wednesday, November 05, 2003 12:37 AM > > ../src/configure --prefix=/usr/install --enable-debugging -v > >^ > > no 'winsup' > > Thanks Chris, > > I think I foolishly picked this up from some misinformation in the mailing > list thread "Can't build cygwin

Re: Problems building cygwin from source

> >I'm interested in building the cygwin DLL from the source, but I'm having > >problems. > > > >I've attached my cygcheck output. I tried the following sequence under my > >home directory... > > > >$ mkdir cygwin-src > >$ cd cygwin-src > >$ export CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs/src > >$ c

Re: Problems building cygwin from source

On Tue, Nov 04, 2003 at 02:08:35PM -0800, Peter J. Stieber wrote: >I'm interested in building the cygwin DLL from the source, but I'm having >problems. > >I've attached my cygcheck output. I tried the following sequence under my >home directory... > >$ mkdir cygwin-src >$ cd cygwin-src >$ export CV

Problems building cygwin from source

I'm interested in building the cygwin DLL from the source, but I'm having problems. I've attached my cygcheck output. I tried the following sequence under my home directory... $ mkdir cygwin-src $ cd cygwin-src $ export CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs/src $ cvs -z3 co winsup $ mkdir Build

Problems building cygwin

Hi, I detected a problem compiling cygwin with gcc 3.2. gcc 3.2 always tries to put /usr/include/w32api/ to the system search path. Fix: Provide -mno-win32 to the make command line. I want to know if this is a new 'feature' of 3.2? In this cas I will provide a patch for buiding cygwin. Regards