From: "Dave Korn" <dave.korn@artimi.com>
To: <binutils@sourceware.org>
Subject: Results for binutils-2.16.92 testsuite on i686-pc-cygwin
Date: Mon, 17 Apr 2006 13:46:00 -0000 [thread overview]
Message-ID: <000c01c6621d$d41c0ea0$a501a8c0@CAM.ARTIMI.COM> (raw)
uname -a:
CYGWIN_NT-5.1 rainbow 1.5.20(0.155/4/2) 2006-03-17 12:29 i686 unknown unknown
Cygwin
gcc -v:
Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs
Configured with: /gcc/gcc-3.4.4/gcc-3.4.4-1/configure --verbose --prefix=/usr
--exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --libexecdir=/usr/lib
--mandir=/usr/share/man --infodir=/usr/share/info
--enable-languages=c,ada,c++,d,f77,java,objc --enable-nls
--without-included-gettext --enable-version-specific-runtime-libs --without-x
--enable-libgcj --disable-java-awt --with-system-zlib --enable-interpreter
--disable-libgcj-debug --enable-threads=posix --enable-java-gc=boehm
--disable-win32-registry --enable-sjlj-exceptions
--enable-hash-synchronization --enable-libstdcxx-debug : (reconfigured)
Thread model: posix
gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)
LAST_UPDATED:
Native configuration is i686-pc-cygwin
=== binutils tests ===
Running target unix
=== binutils Summary ===
# of expected passes 73
# of expected failures 1
=== gas tests ===
Running target unix
=== gas Summary ===
# of expected passes 108
# of expected failures 1
=== ld tests ===
Running target unix
FAIL: cdtest with -Ur
XPASS: align1
FAIL: weak symbols
=== ld Summary ===
# of expected passes 33
# of unexpected failures 2
# of unexpected successes 1
# of expected failures 3
# of untested testcases 6
# of unsupported tests 1
Compiler version: gcc
Platform: i686-pc-cygwin
configure flags: -v
cheers,
DaveK
--
Can't think of a witty .sigline today....
reply other threads:[~2006-04-17 12:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000c01c6621d$d41c0ea0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).