public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Myles Uyema <myles@uyema.nws.net>
To: egcs@cygnus.com
Subject: egcs-971105, i586-linux (glibc-2.0.5c) test results.
Date: Thu, 06 Nov 1997 17:24:00 -0000	[thread overview]
Message-ID: <19971106151942.13139@uyema.nws.net> (raw)

This is my first posting to the list, please tell me if there are
more informative ways to display my testsuite results, or less messy?
-rw-------   1 myles    uyema           8 Nov  6 06:56 libio.a
-rw-------   1 myles    uyema     1079562 Nov  6 06:58 libiostream.a

the test isn't including the flag -L/usr/src/i586/libraries/libio
It still doesn't seem like linking to libio.a would do much, judging
from the miniscule size of the library.

Test Run By myles on Thu Nov  6 14:36:14 1997
Native configuration is i586-pc-linux-gnu
=== libio tests ===
		
Running ../../../../egcs-971105/libio/testsuite/libio.tests/tfformat.exp ...
Executing on host: /usr/src/i586/gcc/xgcc -B/usr/src/i586/gcc/
../../../../egcs-971105/libio/testsuite/../tests/tfformat.c  -O3 -I..
-I../../../../egcs-971105/libio/testsuite/..  -DTEST_LIBIO -DTEST_EXACTNESS
-L/usr/src/i586/libraries/libiberty -g -lio -liberty   -lm  -o
/usr/src/i586/libraries/libio/testsuite/tfformat
compiler exited with status 1
output is:
/usr/i586-linux/bin/ld: cannot open -lio: No such file or directory
collect2: ld returned 1 exit status

FAIL: tfformat.c compilation
FAIL: tiformat.c compilation
FAIL: tstdiomisc.c compilation

=== libio Summary ===
		
# of expected passes            33
# of unexpected failures        3
# of expected failures          4

=== libstdc++ Summary ===

# of expected passes            30

=== g++ tests ===

FAIL: g++.benjamin/warn01.C (test for excess errors)
/usr/src/egcs-971105/gcc/testsuite/g++.old-deja/g++.benjamin/warn01.C:63:
warning: __unused__' attribute does not apply to types
/usr/src/egcs-971105/gcc/testsuite/g++.old-deja/g++.benjamin/warn01.C:72:
warning: __unused__' attribute does not apply to types
FAIL: g++.jason/template31.C (test for excess errors)
/usr/src/egcs-971105/libstdc++/stl/stl_uninitialized.h:57: warning: control
reaches end of non-void function __uninitialized_copy_aux<const Component *,
Component *>(const Component *, const Component *, Component *, __false_type)'
/usr/src/egcs-971105/libstdc++/stl/stl_vector.h:231: warning: control
reaches end of non-void function
vector<Component,__default_alloc_template<false,0>
>::allocate_and_copy(unsigned int, const Component *, const Component *)'
FAIL: g++.mike/eh23.C  Execution test
Executing on host: /usr/src/i586/gcc/testsuite/../xgcc
-B/usr/src/i586/gcc/testsuite/../
/usr/src/egcs-971105/gcc/testsuite/g++.old-deja/g++.mike/eh24.C
-fexceptions  -I/usr/src/egcs-971105/libg++
-I/usr/src/egcs-971105/libg++/src -I/usr/src/egcs-971105/libstdc++
-I/usr/src/egcs-971105/libstdc++/stl
-I/usr/src/i586/gcc/testsuite/../include -lstdc++    -lm  -o /tmp/a.out
FAIL: g++.mike/p6610a.C  Execution test
Executing on host: /usr/src/i586/gcc/testsuite/../xgcc
-B/usr/src/i586/gcc/testsuite/../
/usr/src/egcs-971105/gcc/testsuite/g++.old-deja/g++.mike/p6610b.C  -ansi
-pedantic-errors  -I/usr/src/egcs-971105/libg++
-I/usr/src/egcs-971105/libg++/src -I/usr/src/egcs-971105/libstdc++
-I/usr/src/egcs-971105/libstdc++/stl
-I/usr/src/i586/gcc/testsuite/../include -lstdc++    -lm  -o /tmp/a.out

=== gcc Summary ===

# of expected passes            4883
# of expected failures          5
# of unsupported tests          7

=== g++ Summary ===

# of expected passes            3377
# of unexpected failures        4
# of unexpected successes       3
# of expected failures          79
# of untested testcases         6

-- 
Myles Uyema
myles@puck.nether.net

                 reply	other threads:[~1997-11-06 17:24 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=19971106151942.13139@uyema.nws.net \
    --to=myles@uyema.nws.net \
    --cc=egcs@cygnus.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).