Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1

[JonY <jon_y at users dot sourceforge dot net>]

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