X-Spam-Check-By: sourceware.org Date: Thu, 5 Jan 2006 17:21:47 +0100 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Message-ID: <261310060387.20060105172147@familiehaase.de> To: Ivan Godard CC: cygwin AT cygwin DOT com Subject: Re: ping In-Reply-To: <43BC8CD9.7090309@pacbell.net> References: <43BC8CD9 DOT 7090309 AT pacbell DOT net> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Ivan wrote: > Many thanks; cross-building from another directory did in fact > eliminate my problem. Anybody want a report saying that cross-build is > required on Cygwin but not on any (of several) other systems? I admit > the bell is more interesting :-) It is usual way to build any package outside of the source directory in a separate build directory, it is a well known fact for packages using Cygnus configure and for GCC it is stated in the README somewhere, don't know if binutils makes this clear in the README. At least for gcc it is a requirement since it will fail when trying to build inside the source directory. If this works for you on another platform, you're a lucky man. IMO every package not supporting builds outside the source tree is buggy. Gerrit -- =^..^= http://nyckelpiga.de/donate.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/