Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <80575AFA5F0DD31197CE00805F650D7602CE9F@wilber.adroit.com> From: "Robinow, David" To: cygwin AT cygwin DOT com Subject: RE: Can't build Make from source because Windows header filesmove d to /usr/include/w32api? Date: Thu, 1 Mar 2001 09:30:09 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" > My point is very simple. The main point of configure is that > "configure; make" should work without the person running it needing to > do any additional configuration. If the person running it needs to do > additional configuration, then the configure script needs to be > updated somehow. That's all there is to it. All I'm asking is, is > the fact that "-mwin32" is now required and wasn't before going to be > reflected in autoconf and in the configure scripts used to compile the > various packages that compile under Cygwin? Yes, I think it will, someday. When somebody gets around to it. Preferably someone with experience submitting patches to configure scripts. Note, however: 1) This has only become a problem recently with a change to gcc 2) A working binary is distributed 3) Most people likely to need to rebuild make are likely to be untroubled by this small problem. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple