Displaying 3 results from an estimated 3 matches for "tc_daemon".
Did you mean:
rpc_daemon
2005 Feb 28
3
test/unit error report for win32-service
...''
tc_service.rb:140:in `test_start_stop''
3) Failure:
test_version(TC_Win32Service) [tc_service.rb:52]:
Bad version.
<"0.4.5"> expected but was
<"0.4.4">.
25 tests, 78 assertions, 2 failures, 1 errors
C:\win32utils\win32-service\test>ruby tc_daemon.rb
Loaded suite tc_daemon
Started
...F
Finished in 0.02 seconds.
1) Failure:
test_version(TC_Daemon) [tc_daemon.rb:24]:
<"0.4.5"> expected but was
<"0.4.4">.
4 tests, 12 assertions, 1 failures, 0 errors
C:\win32utils\win32-service\test>
2005 Mar 16
1
Problem with win32-service
It compiles fine, but when the resulting library is required, it says:
C:\_co\source\build\ruby\extensions\win32-service-0.4.5\test>ruby tc_daemon.rb
C:/_co/source/build/ruby/extensions/win32-service-0.4.5/win32/service.so:
`interactive?'' is not proper name for a struct member (NameError)
from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:18:in
`require''
from tc_daemon.rb:14
ruby -v says:
ru...
2005 Feb 14
8
DONT_RESOLVE_DLL_REFERENCES info
For future reference, it looks like we should avoid
DONT_RESOLVE_DLL_REFERENCES in any extensions.
http://weblogs.asp.net/oldnewthing/archive/2005/02/14/372266.aspx
Regards,
Dan