[Mono-list] RE: serving off solaris
Michael
stuff@dustsmoke.com
Wed, 12 May 2004 14:06:58 -0700 (MST)
Well, it would appear that mono and solaris are not good friends. I have
tried to use the (may 12) cvs of mono, xsp, and mod_mono. However mono
would not get past autogen.sh...
../autogen.sh
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.
Running libtoolize...
You should update your `aclocal.m4' by running aclocal.
Running aclocal ...
Running autoheader...
WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
WARNING: and `config.h.top', to define templates for `config.h.in'
WARNING: is deprecated and discouraged.
WARNING: Using the third argument of `AC_DEFINE' and
WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
WARNING: `acconfig.h':
WARNING: AC_DEFINE([NEED_MAIN], 1,
WARNING: [Define if a function `main' is needed.])
WARNING: More sophisticated templates can also be produced, see the
WARNING: documentation.
autoheader: `config.h.in' is unchanged
Running automake --gnu ...
runtime/Makefile.am:36: `monotwo_DATA' is used but `monotwodir' is undefined.
runtime/Makefile.am:33: `monoone_DATA' is used but `monoonedir' is undefined.
runtime/Makefile.am:29: `monobins_DATA' is used but `monobinsdir' is
undefined.
**Error**: automake failed.
So I am currenly running cvs of mod_mono and xsp with beta1 of mono.
But neither apache nor xsp appear to like serving...
APACHE ERROR
/usr/local/apache2/bin/apachectl start
Syntax error on line 232 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/local/apache2/modules/libmod_mono.so into server:
ld.so.1: /usr/local/apache2/bin/httpd: fatal: relocation error: file
/usr/local/apache2/modules/libmod_mono.so: symbol setenv: referenced
symbol not found
XSP ERROR
mono /usr/local/bin/xsp.exe --root . --applications /mono:.
Listening on port: 8080
Listening on address: 0.0.0.0
Root directory: /usr/local/apache2/htdocs/test
Hit Return to stop the server.
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Runtime.Remoting.Lifetime.LifetimeServices
Server stack trace:
in (unmanaged)
System.Runtime.Remoting.Lifetime.LifetimeServices:get_LeaseTime ()
in <0x00028> System.Runtime.Remoting.Lifetime.Lease:.ctor ()
in <0x00084> (wrapper remoting-invoke-with-check)
System.Runtime.Remoting.Lifetime.Lease:.ctor ()
in <0x00024> System.MarshalByRefObject:InitializeLifetimeService ()
in <0x00008>
System.Runtime.Remoting.ObjectHandle:InitializeLifetimeService ()
in <0x00098>
System.Runtime.Remoting.RemotingServices:CreateClientActivatedServerIdentity
(System.MarshalByRefObject,System.Type,string)
in <0x003fc> System.Runtime.Remoting.RemotingServices:Marshal
(System.MarshalByRefObject,string,System.Type)
in <0x00010> System.Runtime.Remoting.RemotingServices:Marshal
(System.MarshalByRefObject)
in <0x001bc>
System.Runtime.Remoting.Messaging.CADMessageBase:MarshalArgument
(object,System.Collections.ArrayList&)
in <0x000c8>
System.Runtime.Remoting.Messaging.CADMethodReturnMessage:.ctor
(System.Runtime.Remoting.Messaging.IMethodReturnMessage)
in <0x0014c>
System.Runtime.Remoting.Messaging.CADMethodReturnMessage:Create
(System.Runtime.Remoting.Messaging.IMessage)
in <0x000c8> System.AppDomain:ProcessMessageInDomain
(byte[],System.Runtime.Remoting.Messaging.CADMethodCallMessage,byte[]&,System.Runtime.Remoting.Messaging.CADMethodReturnMessage&)
in <0x000dc> (wrapper remoting-invoke-with-check)
System.AppDomain:ProcessMessageInDomain
(byte[],System.Runtime.Remoting.Messaging.CADMethodCallMessage,byte[]&,System.Runtime.Remoting.Messaging.CADMethodReturnMessage&)
in <0x00050>
System.Runtime.Remoting.Channels.CrossAppDomainSink:ProcessMessageInDomain
(byte[],System.Runtime.Remoting.Messaging.CADMethodCallMessage)
Exception rethrown at [0]:
---> System.OverflowException: Resulting timespan is too big.
in <0x00298> System.TimeSpan:FromMilliseconds (double)
in <0x0005c> System.TimeSpan:FromSeconds (double)
in <0x0005c> System.Runtime.Remoting.Lifetime.LifetimeServices:.cctor ()
--- End of inner exception stack trace ---
in <0x00320> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
(System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage,System.Exception&,object[]&)
So it would be greatly appreciated if anyone could shead any light on (I'm
sure) my silly user errors. Thanks everyone!