X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4C8F5125.9080504@users.sourceforge.net> Date: Tue, 14 Sep 2010 18:40:37 +0800 From: JonY User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1 References: <4C8F1CF2.8000703@users.sourceforge.net> <790680.25836.qm@web25507.mail.ukl.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 9/14/2010 18:46, Andy Koppe wrote: > On 14 September 2010 11:15, Marco Atzeri wrote: >>>> Is this to be expected? >>>> >>>> $ x86_64-w64-mingw32-gcc hello.c >>>> [compiles fine] >>>> >>>> $ /bin/x86_64-w64-mingw32-gcc hello.c >>>> /Users/Andy/AppData/Local/Temp/cckcwv49.s: Assembler >>> messages: >>>> /Users/Andy/AppData/Local/Temp/cckcwv49.s:10: Error: >>> bad register name `%rbp' >>>> /Users/Andy/AppData/Local/Temp/cckcwv49.s:11: Error: >>> bad register name `%rsp' >>>> /Users/Andy/AppData/Local/Temp/cckcwv49.s:12: Error: >>> bad register name `%rsp' >>>> /Users/Andy/AppData/Local/Temp/cckcwv49.s:14: Error: >>> bad register name `%rip)' >>>> >>>> It's obviously picking up the wrong assembler that >>> way > >> Usually assuring the /usr/bin is before /bin in the path >> solves the problems. > > /usr/bin is put before /bin in /etc/profile anyway, so it's not a > critical issue. I just happened to try it with the /bin prefix first, > probably because I was using tab completion on /bin to find the > executable name of the compiler. > > Andy > OK, so calling "x86_64-w64-mingw32-gcc" or "/usr/bin/x86_64-w64-mingw32-gcc" in the shell usually works, but not "/bin/x86_64-w64-mingw32-gcc"? -- 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