Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <010501befe05$0c3da250$656aadcf@qsicorp.com>
Reply-To: "Michael K. Elwood" <mkelwood AT qsicorp DOT com>
From: "Michael K. Elwood" <mkelwood AT qsicorp DOT com>
To: <cygwin AT sourceware DOT cygnus DOT com>
Subject: Building native Mingw32 tools
Date: Mon, 13 Sep 1999 10:28:44 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Mumit, I know you hate answering questions about this stuff. Maybe the
answer is quick and easy, or perhaps somebody else knows how to fix this.

I have been following the howto posted at
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/mingw-cross-howto.txt
to attempt to build mingw32-hosted tools on a linux (Mandrake 6.0) box. I am
using the gcc 2.95 source, the 1999-07-31 runtime and your win32 patch for
gcc 2.95. The linux-x-mingw32 compiler built without a hitch and seems to
work very nicely. I then built binutils for a mingw32 host -- again no
problem.

But when I try to build the mingw32 hosted compiler using the linux-x-ming32
cross compiler, the build croaks when it tries to link collect2. It
complains that it can't find functions for certain system calls,
specifically pipe, kill and fork. I know that mingw32 doesn't implement all
POSIX system calls, but your howto seems to indicate that gcc should build
properly (i.e. that this should not be a problem). I searched your patch,
and collect2.c (where the calls are located) isn't touched.

Am I missing something here? Any help greatly appreciated. Please let me
know if you need more specification information about the configure, build,
etc.

Best regards,

MKE



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com