Hi Rob,
I hope it is OK to file bug reports this way. I couldn't see a bug report
script so I used the one from GCC.
We generally use bugzilla for filing binutils bug reports:
http://www.sourceware.org/bugzilla/
You do not actually say what bug you are reporting. Presumably you
consider the testsuite failures to be bugs, yes ?
FAIL: windres/bmpalign (parse)
This failure should now be resolved.
=== ld Summary ===
# of expected passes 309
# of unexpected failures 103
I am now showing 8 unexpected failures for an x86_64-linux-gnulibc
toolchain based on today's gcc and binutils sources.
Compiler version: gcc 4.2.0 20070501 (prerelease)
Binutils version: binutils-2.17cvs20070426
Platform: i686-pc-linux-gnu
configure flags: --enable-64-bit-bfd --enable-shared
--enable-targets=i686-pc-linux-gnu,x86_64-pc-linux-gnu,i686-pc-cygwin,arm-epoc-pe,arm-none-symbianelf
,arm-none-eabi
This is a complicated set of targets. Is there any particular reason
for them ?
I applied this patch:
http://ftp.debian.org/debian/pool/main/b/binutils/binutils_2.17cvs20070426-6.diff.gz
I tried to look at this patch but it was not available for download from
that URL. What does it do ?
Cheers
Nick
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils
