X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "Joe Smith" Subject: Re: Eliminating -mno-cygwin from gcc. Date: Wed, 7 Feb 2007 17:21:06 -0500 Lines: 13 Message-ID: References: <020d01c748b4$62d8b170$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20070205030939 DOT GB24653 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 "Christopher Faylor" wrote in message news:20070205030939 DOT GB24653 AT trixie DOT casa DOT cgf DOT cx... >[snip] > I guess this means that I need to generate a cross-binutils, too. Is a cross-binutils really needed? Which (if any) of the binutils act differently when targeted at MingW32 than when targeted at Cygwin? (I've never worked with a cross toolchain where the executable format of the host and target are the same.) -- 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/