X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEF@bespdc01.mediaxim.local> References: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFD0 AT bespdc01 DOT mediaxim DOT local> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEF AT bespdc01 DOT mediaxim DOT local> Date: Mon, 23 Apr 2012 09:43:59 -0400 Message-ID: Subject: Re: Building for nocygwin From: Earnie Boyd To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 On Mon, Apr 23, 2012 at 9:09 AM, Michel Bardiaux wrote: > [snip] > >> Sure, --host=i686-pc-mingw32 or some other appropriate host string during configure. >> You'll need to make sure you have the appropriate files for cross compiling. >> The -mno-cygwin has been gone for some months moving into years. > > That much I could guess. I am pretty sure I could muddle through until I can configure and build, say, libav. I was hoping for a general solution. That is the "general solution". The error message was appropriate and gave a clue. Beyond that you'll need to communicate a patch to the maintainers of the package that is still using -mno-cygwin. -- Earnie -- https://sites.google.com/site/earnieboyd -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple