[PATCH] New *-*-solaris2.x cross configury, including looser wchar_t requirements for all targets
Benjamin Kosnik
bkoz@redhat.com
Fri Sep 26 20:22:00 GMT 2003
>This fails because filebuf_members-1.txt was not writable and the
>system call underneath line 53 fails with EACCES. Changing the file
>permissions made this test run fine.
>
>The following tests all failed due to incorrect file permissions on
>their associated (provided) input files. The tests all tried to do
>something which required the file to be writable, and it wasn't.
>Changing the file permissions made them work. This was a source of
>seemingly endless entertainment. Unfortunately, I didn't track
>exactly which files needed +w.
>
>FAIL: 27_io/basic_filebuf/is_open/char/1.cc execution test
>FAIL: 27_io/basic_filebuf/open/char/1.cc execution test
>FAIL: 27_io/basic_filebuf/sbumpc/char/1-io.cc execution test
>FAIL: 27_io/basic_filebuf/sbumpc/char/2-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekoff/char/1-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekoff/char/1-out.cc execution test
>FAIL: 27_io/basic_filebuf/seekoff/char/2-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekoff/char/2-out.cc execution test
>FAIL: 27_io/basic_filebuf/seekoff/char/3-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekoff/char/3-out.cc execution test
>FAIL: 27_io/basic_filebuf/seekpos/char/1-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekpos/char/1-out.cc execution test
>FAIL: 27_io/basic_filebuf/seekpos/char/2-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekpos/char/2-out.cc execution test
>FAIL: 27_io/basic_filebuf/seekpos/char/3-io.cc execution test
>FAIL: 27_io/basic_filebuf/seekpos/char/3-out.cc execution test
>FAIL: 27_io/basic_filebuf/setbuf/char/1.cc execution test
>FAIL: 27_io/basic_filebuf/sgetc/char/1-io.cc execution test
>FAIL: 27_io/basic_filebuf/sgetc/char/2-io.cc execution test
>FAIL: 27_io/basic_filebuf/sgetn/char/1-io.cc execution test
>FAIL: 27_io/basic_filebuf/sgetn/char/2-io.cc execution test
>FAIL: 27_io/basic_filebuf/snextc/char/1-io.cc execution test
>FAIL: 27_io/basic_filebuf/snextc/char/2-io.cc execution test
>FAIL: 27_io/basic_istream/seekg/char/fstream.cc execution test
>FAIL: 27_io/basic_istream/tellg/char/fstream.cc execution test
Huh. My copy of the sources have these files (in
libstdc++-v3/testsuite/data) as already writable. I wonder what is up
here?
>The following tests all failed due to a missing "std::" on some
>exception names. I fixed and confirmed this with each.
>
>FAIL: 27_io/basic_filebuf/cons/wchar_t/10132-1.cc (test for excess
>errors)
>WARNING: 27_io/basic_filebuf/cons/wchar_t/10132-1.cc compilation
>failed to produce executable
>FAIL: 27_io/basic_istream/sentry/char/3983-fstream.cc (test for excess
>errors)
>WARNING: 27_io/basic_istream/sentry/char/3983-fstream.cc compilation
>failed to produce executable
>FAIL: 27_io/basic_istream/sentry/char/3983-sstream.cc (test for excess
>errors)
>WARNING: 27_io/basic_istream/sentry/char/3983-sstream.cc compilation
>failed to produce executable
>FAIL: 27_io/basic_ostream/sentry/char/3983-fstream.cc (test for excess
>errors)
>WARNING: 27_io/basic_ostream/sentry/char/3983-fstream.cc compilation
>failed to produce executable
>FAIL: 27_io/basic_ostream/sentry/char/3983-sstream.cc (test for excess
>errors)
>WARNING: 27_io/basic_ostream/sentry/char/3983-sstream.cc compilation
>failed to produce executable
Odd, as there is a using directive in scope. However, I've checked in
your patch to explicitly qualify, and removed the directive.
Thanks!
best,
benjamin
More information about the Libstdc++
mailing list