public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Christian Joensson" <christian.joensson@gmail.com>
To: binutils <binutils@sources.redhat.com>
Subject: Results for 2.16.93 20060517 testsuite on i686-pc-cygwin
Date: Fri, 19 May 2006 17:25:00 -0000	[thread overview]
Message-ID: <5460e3330605190830k533f9acfi5f694f19ea92155c@mail.gmail.com> (raw)

Windows XP Pro/SP2 cygwin Pentium M processor 2.13GHz system with packages:

binutils             20050610-1     2.16.91 20050610
bison                2.1-1          2.1
cygwin               1.5.19-4
dejagnu              20021217-2     1.4.2.x
expect               20030128-1     5.26
gcc                  3.4.4-1
gmp                  4.1.4-2
make                 3.80-1	
tcltk                20030901-1     8.4
w32api               3.7-1	

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		39
# of unexpected failures	2
# of unexpected successes	1
# of expected failures		3
# of unsupported tests		1

version: 2.16.93 20060517
Platform: i686-pc-cygwin
configure flags: none
Counting all warnings,
there are 4 warnings in stage0 of this bootstrap.

Number of warnings per file:
      2 libtool
      1 libiberty/strsignal.c
      1 ../../src/intl/l10nflist.c

Number of warning types:
      2 undefined symbols not allowed in i686-pc-cygwin shared libraries
      1 comparison between signed and unsigned
      1 assignment makes pointer from integer without a cast

                 reply	other threads:[~2006-05-19 15:30 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=5460e3330605190830k533f9acfi5f694f19ea92155c@mail.gmail.com \
    --to=christian.joensson@gmail.com \
    --cc=binutils@sources.redhat.com \
    /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).