manojoswal
asked on
Mono Installation on RHE3
Hello,
I've been trying to install Mono on Red Hat Enterprise Linux 3.
So far I downloaded the rpms and installed them all using rpm -Uvh --nodeps --force *rpm.
Then I installed Apache 2.50 in a different location and was sucessfully able to configure and make the mod_mono.
The problem am facing is with building the ModMono.dll
mcs ModMono.cs -target:library -reference:/home/user/mono /install/l ib/System. Web.dll
I found various System.Web.dll on my server and being not sure to use which one, I tried to build ModMono.dll using all of them one by one. But every time I am facing this problem:
usr/local/bin/mono: error while loading shared libraries: libc.so.0: cannot handle TLS data
Can anyone tell me if I've installed Mono correctly or there is some installation issue.
I've installed the rpms three time already, once using those of RH 9.0 and then of Fedora 2.
Thanks in Advance.
I've been trying to install Mono on Red Hat Enterprise Linux 3.
So far I downloaded the rpms and installed them all using rpm -Uvh --nodeps --force *rpm.
Then I installed Apache 2.50 in a different location and was sucessfully able to configure and make the mod_mono.
The problem am facing is with building the ModMono.dll
mcs ModMono.cs -target:library -reference:/home/user/mono
I found various System.Web.dll on my server and being not sure to use which one, I tried to build ModMono.dll using all of them one by one. But every time I am facing this problem:
usr/local/bin/mono: error while loading shared libraries: libc.so.0: cannot handle TLS data
Can anyone tell me if I've installed Mono correctly or there is some installation issue.
I've installed the rpms three time already, once using those of RH 9.0 and then of Fedora 2.
Thanks in Advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I got it working finally. There was a library missing and on top of that, the Documentation on the site was outdated. Hence couldn't get the module working with Apache.
Thanks for your comment.