shyouhei bb41909d8b Skip syslog tests that rely on LOG_PERROR unless it's defined ... Instead of checking looking at the platform to determine if the tests relying on LOG_PERROR should be run, look for the definition of the constant as this will be robust against all platforms as long as the underlying syslog.c code sets it up correctly. This specifically addresses failures on Solaris 9. Signed-off-by: Ben Walton <bwalton@artsci.utoronto.ca> Signed-off-by: URABE, Shyouhei <shyouhei@ruby-lang.org> git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@31178 b2dd03c8-39d4-4d8f-98ff-823fe69b080e		2011-03-25 11:06:57 +00:00
..
-ext-
base64
benchmark
bigdecimal
cgi
coverage
csv
date
dbm
digest
dl
drb
erb
etc
fiddle
fileutils
gdbm
iconv
io
irb
json
logger
matrix
minitest
misc
mkmf
monitor
net
nkf
objspace
open-uri
openssl
optparse
ostruct
pathname
psych
rake
rdoc
readline
resolv
rexml
rinda
ripper
rss
ruby
rubygems
scanf
sdbm
socket
stringio
strscan
syck
testunit
thread
uri
webrick
win32ole
xmlrpc
zlib
inlinetest.rb
profile_test_all.rb
runner.rb
test_cmath.rb
test_delegate.rb
test_find.rb
test_ipaddr.rb
test_mathn.rb
test_mutex_m.rb
test_open3.rb
test_pp.rb
test_prettyprint.rb
test_prime.rb
test_pstore.rb
test_pty.rb
test_set.rb
test_shellwords.rb
test_singleton.rb
test_syslog.rb
test_tempfile.rb
test_time.rb
test_timeout.rb
test_tracer.rb
test_tsort.rb
with_different_ofs.rb