X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4C2CA007.9040604@iname.com> References: <4C2CA007 DOT 9040604 AT iname DOT com> Date: Thu, 1 Jul 2010 16:11:14 +0200 Message-ID: Subject: Re: GCC on 64-bit windows From: Csaba Raduly To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 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 Thu, Jul 1, 2010 at 4:02 PM, Daniel Jensen wrote: > I'm running Windows 7 64-bit, and I installed Cygwin 1.7 (snip) > Unsupported 16-bit Application > The program or feature "\??\c:\cygwin\bin\g++.exe" cannot start or run due > to incompatibility with 64-bit versions of Windows. > Anyone know why gcc would be different? ls -l /usr/bin/g++ is likely to report that g++ is a symlink. You need to configure Eclipse to launch g++-4.exe (or g++-3.exe) -- Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- 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