Message-ID: <790680.25836.qm@web25507.mail.ukl.yahoo.com>
Date: Tue, 14 Sep 2010 10:15:06 +0000 (GMT)
From: Marco Atzeri <marco_atzeri AT yahoo DOT it>
Subject: Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1
To: cygwin AT cygwin DOT com, JonY <jon_y AT users DOT sourceforge DOT net>
In-Reply-To: <4C8F1CF2.8000703@users.sourceforge.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

--- Mar 14/9/10,  ha scritto:

> On 9/14/2010 13:11, Andy Koppe
> wrote:
> > On 14 September 2010 03:13, JonY wrote:
> >> Version 4.5.1-1 of "mingw64-x86_64-gcc" has been
> uploaded.
> >>
> >> mingw64-x86_64-gcc contains GCC sources used by
> the 64bit target toolchain.
> >> See mingw64-x86_64-gcc-core,
> mingw64-x86_64-gcc-objc,
> >> mingw64-x86_64-gcc-ada, mingw64-x86_64-gcc-g++
> and
> >> mingw64-x86_64-gcc-fortran for binaries.
> >
> > Great stuff.
> >
> > First issue: 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.
> >
> > $ /bin/x86_64-w64-mingw32-gcc hello.c -v
> > Using built-in specs.
> > COLLECT_GCC=3D/bin/x86_64-w64-mingw32-gcc
> >
> COLLECT_LTO_WRAPPER=3D/bin/../lib/gcc/x86_64-w64-mingw32/4.5.1/lto-wrappe=
r.exe

> >
> > Andy
>=20
> That is weird.
>=20
> Do you have mingw64 binutils installed? Somehow the cygwin
> binutils was=20
> used.
>=20


It is not so weird, I have already seen it in other programs=20
that expect to be installed in /usr/bin
and are unable to find the other portions if they
are called from /bin

Instead of
/bin/../lib/gcc/x86_64-w64-mingw32/4.5.1/lto-wrapper.exe
that doesn't work

/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.1/lto-wrapper.exe
means
/usr/lib/gcc/x86_64-w64-mingw32/4.5.1/lto-wrapper.exe

Usually assuring the /usr/bin is before /bin in the path=20
solves the problems. For cygwin we could also remove /bin
at all from the path.

Marco


=20=20=20


--
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