mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
ChangeLog for it
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@31179 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
parent
bb41909d8b
commit
8c6a73ded3
1 changed files with 19 additions and 0 deletions
19
ChangeLog
19
ChangeLog
|
@ -1,3 +1,22 @@
|
||||||
|
Fri Mar 25 19:39:40 2011 Ben Walton <bwalton@artsci.utoronto.ca>
|
||||||
|
|
||||||
|
* test/test_syslog.rb:
|
||||||
|
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.
|
||||||
|
|
||||||
|
Use LOG_PID instead of LOG_PERROR in Syslog.open test
|
||||||
|
|
||||||
|
LOG_PERROR isn't a POSIX option for syslog, so it fails on platforms
|
||||||
|
that don't define it. Solaris 9 and 10 are examples of this.
|
||||||
|
|
||||||
|
Use LOG_PID instead.
|
||||||
|
|
||||||
Fri Mar 25 15:42:17 2011 NARUSE, Yui <naruse@ruby-lang.org>
|
Fri Mar 25 15:42:17 2011 NARUSE, Yui <naruse@ruby-lang.org>
|
||||||
|
|
||||||
* ext/sdbm/_sdbm.c (sdbm_open): use size_t.
|
* ext/sdbm/_sdbm.c (sdbm_open): use size_t.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue