Please do not top-post.
On Wednesday 10 March 2010 20:38:52 Natalie Tasman wrote:
> Apologies for the not-useful error report. I'm not able to
> reproduce this on the commandline, running what I think is similar
> to to the xming cross-compiler build script:
> ./configure --target=i686-pc-mingw32 --with-gcc --with-gnu-as
> --with-gnu-ld --disable-nls --disable-debug
> In this case both 2.20-1 and 2.19-1 configure and build without
The release in question is 2.20.1, not 2.20-1.
> However, I must be missing something because this does not
> actually work when using the cross-compiler build script with
> 2.20-1. So perhaps this is an issue more with that script, rather
> than binutils. I'm not enough of a mingw/binutils/cross-compiler
> guru to take it farther than this myself, though.
Following your initial bug report, I've identified two issues with
Chris' 2.20.1 release, as described in my response in the original
1) Chris incorrectly named the source tarball.
2) The upstream release provided a defective tarball in any case;
they broke GCS conformance by distributing a bfd.info which was out
of date with respect to its source, (an error which alas, they seem
to make all to frequently).
I've updated our copy of that source tarball, to correct the defect.
I've also released a new version of the build scripts, to address
the change in SF's hosting structure, (a change which I'd already
addressed in CVS some three months ago).
For further details, see my reply to your post in this thread: