This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] [1.7] Updated: binutils-2.19.51-1
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 05 Jul 2009 14:12:50 +0100
- Subject: Re: [ANNOUNCEMENT] [1.7] Updated: binutils-2.19.51-1
- References: <4A5067EB.5080203@bonhard.uklinux.net>
Fergus wrote:
> Two packaging oddities after this update:
>
> 1) New directory \usr\i686-pc-cygwin\ containing
>
> \usr\i686-pc-cygwin\bin
> \usr\i686-pc-cygwin\bin\ar.exe.lnk
> \usr\i686-pc-cygwin\bin\as.exe.lnk
> \usr\i686-pc-cygwin\bin\ld.exe.lnk
> \usr\i686-pc-cygwin\bin\nm.exe.lnk
> \usr\i686-pc-cygwin\bin\ranlib.exe.lnk
> \usr\i686-pc-cygwin\bin\strip.exe.lnk
What's with the wrong slashes? Anyway, that's not new, the old one had it too:
$ tar tfj binutils-20080624-2.tar.bz2 | grep 'i686-pc-cygwin'
usr/i686-pc-cygwin/
usr/i686-pc-cygwin/bin/
usr/i686-pc-cygwin/bin/ar.exe
usr/i686-pc-cygwin/bin/as.exe
usr/i686-pc-cygwin/bin/ld.exe
usr/i686-pc-cygwin/bin/nm.exe
usr/i686-pc-cygwin/bin/ranlib.exe
usr/i686-pc-cygwin/bin/strip.exe
$ tar tfj binutils-2.19.51-1.tar.bz2 | grep 'i686-pc-cygwin'
usr/i686-pc-cygwin/
usr/i686-pc-cygwin/bin/
usr/i686-pc-cygwin/bin/ar.exe
usr/i686-pc-cygwin/bin/as.exe
usr/i686-pc-cygwin/bin/ld.exe
usr/i686-pc-cygwin/bin/nm.exe
usr/i686-pc-cygwin/bin/ranlib.exe
usr/i686-pc-cygwin/bin/strip.exe
$
(you can add 'v' to tar options to check that they're links in both cases;
they are.)
> 2) New directory \usr\i686-pc-mingw32\ containing
>
> \usr\i686-pc-mingw32\include.lnk
> \usr\i686-pc-mingw32\lib.lnk
> \usr\i686-pc-mingw32\bin.lnk
Don't know where you picked up that, but it wasn't from binutils:
$ tar tfj binutils-2.19.51-1.tar.bz2 | grep 'i686-pc-ming'
$
> Also (3) I get a STATUS_ACCESS_VIOLATION as reported by others
>
>>bash
This is not a binutils bug report any longer! Try downgrading bash; there's
a problem with the new libreadline7 build, which hopefully a respin with gcc-4
and this new binutils will fix.
cheers,
DaveK
--
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