Well it's been quite some time since I've been able to try compiling Mono from
source.

I downloaded the mono-build-w32.sh script, set my ACLOCAL_FLAGS="-I
/usr/local/share/aclocal" and PKG_CONFIG_PATH="/usr/local/bin" (the mono
compiling page says only to set the appropriate variables but doesn't say to
what or why or how--not too helpful to us windows spoiled compiling noobs, I
got instructions on what to set these to from
http://www.gotmono.com/docs/installation/windows.html#build). I then ran the
script according to instructions from the mono compiling page. Initially the
script said that a file was broken and I should delete a line (can't recal the
file name but the line to delet was something like #define ftruncate...). So I
found the file the error message mentioned, deleted the line and ran the script
again.


Well then the script seemed to run just fine for a long time. make was going
along through the directory structure of the source code for a long time (like,
an hour). I was seeing quite a few warnings but no errors until...suddenly
there were a *lot* of "undefined reference to.." messages that all seemed to
refer to files in the ~/glib-2.0.4/glib/ directory and its subdirectories.
Then make exited with the following output:
collect2: ld returned 1 exit status
make[3]: ***[pedump.exe] Error 1
make[3]: Leaving directory '/home/michael/mono/mono/mono/metadata'
make[3]: *** [all-recursive] Error 1


...then some other lines that just show that make is recursively leaving the
directory structure, then...

make: *** [all] Error 2

So, what should I look at next?

Quoting Jambunathan Jambunathan <[EMAIL PROTECTED]>:

Hello Michael

All you need to do is folow the instructions mentioned in
the two links below.

http://www.mono-project.com/contributing/anoncvs.html
http://www.mono-project.com/contributing/compiling.html

Once you are able to successfully build mono and mcs tree
you are all set.

If you run in to any issues, do post the specific errors that
you encounter and the community will be happy to help you
out.

Regards,
Jambunathan K.




<[EMAIL PROTECTED]> 10/22/04 11:24 PM >>>
Jambunathan,

Thank you so much for your detailed and encouraging replies.

I am pretty much a noob as far as the linux/open source software
world.
Consequently, I have never built an app by checking the code out from
cvs and
building the app from the checked out source.  I guess building mono
from CVS
would be the next step because the newer version may have the VB
runtime issue
I'm running into fixed already.  I'm not really sure what the steps are
to do
this.  I have a linux box too, but I'd like to stick to Windows for now

because
DotNetNuke is highly dependant on SQL server (lots of stored
procedures) and
I'd like to try to see if I can get it running using SQL Server first,
then
look into what it would take to port the DB stuff to PostgreSQL or
MySQL.

I recently purchased the Mono Developers Notebook, I think it has
instructions
on building Mono from source on Windows so I'll enter into a learning
process
and take that on, then try again with the newer version of Mono.

If folks can suggest a link to a tutorial on the process of building
apps from
source on Windows, that would also be appreciated.

Thanks,

Michael Bradley

Theoretically, it should run on Mono, even though it's written in
VB
(isn't
this true?) because the application is compiled to IL. So Mono
shouldn't need
to compile any VB, just compile or interpret the IL.

Very much true.

Well, if it's a pre-compiled Microsoft's IL then there should be
no issues, except possibly for some yet to be identified glitches in
Microsoft.VisualBasic runtime, which we will be happy to address in
no time :-)

(Just to clarify on my earlier posting, if you would like to build
the
dll
using mbas, we aren't there yet.)

Anybody done this?

I am not aware of any.

Regards,
Jambunathan K.


<[EMAIL PROTECTED]> 10/21/04 10:38 PM >>>
Thanks for your response.  Unfortunately, there is no c# version of
DotNetNuke.
The core team has talked about porting it, there's even a
csharpNuke.com
website. However, no c# version has yet been made available and
various
posts
on the DotNetNuke forum leads me to believe it will be some time (if
ever)
before a c# port is done.

I was hoping maybe someone else has tried to run DNN on Mono. I'ts
a
very
capable and easy to use portal framework which I'm already familiar
with.
Theoretically, it should run on Mono, even though it's written in VB
(isn't
this true?) because the application is compiled to IL.  So Mono
shouldn't need
to compile any VB, just compile or interpret the IL.

Anybody done this?


I would start off by grabbing the c# version of dotnetnuke because
I
am
unsure if the vb support is 100% in mono right now.


[EMAIL PROTECTED] wrote:

Hello,

I tried running the DotNetNuke open source ASP.NET portal system using XSP (mono
1.0.2 installed on WindowsXP). I got the following error
messages:

Server error in '/' application Description: Error processing request.

Error Message: HTTP 500.

Stack Trace:

System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. ---> System.ArgumentOutOfRangeException: Argument is
out of range.
Parameter name: count
in <0x0004a> System.String:Split (char[],int)
in <0x0012d> Microsoft.VisualBasic.Strings:Split
(string,string,int,Microsoft.VisualBasic.CompareMethod)
in <0x00085> DotNetNuke.Data.SqlDataProvider:ExecuteScript
(string,bool)
in <0x0001e> DotNetNuke.Data.SqlDataProvider:ExecuteScript
(string)
in <0x0011e> DotNetNuke.Data.SqlDataProvider:GetProviderPath ()
in <0x0001a> DotNetNuke.PortalSettings:GetProviderPath ()
in <0x00130> DotNetNuke.Upgrade:AutoUpgrade ()
in <0x000dd> DotNetNuke.Global:Application_Start
(object,System.EventArgs)
in (unmanaged) (wrapper managed-to-native)
System.Reflection.MonoMethod:InternalInvoke (object,object[])
in <0x00004> (wrapper managed-to-native)
System.Reflection.MonoMethod:InternalInvoke (object,object[])
in <0x0007a> System.Reflection.MonoMethod:Invoke


(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
--- End of inner exception stack trace ---

in <0x000b9> System.Reflection.MonoMethod:Invoke


(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
in <0x00021> System.Reflection.MethodBase:Invoke (object,object[])
in <0x000b2> System.Web.HttpApplicationFactory:FireEvent
(string,object,object[])
in <0x00063> System.Web.HttpApplicationFactory:FireOnAppStart
(System.Web.HttpApplication)
in <0x00077> System.Web.HttpApplicationFactory:InitializeFactory
(System.Web.HttpContext)
in <0x00070> System.Web.HttpApplicationFactory:GetInstance
(System.Web.HttpContext)
in <0x000ee> System.Web.HttpRuntime:InternalExecuteRequest
(System.Web.HttpWorkerRequest)

I'm pretty new to Mono and not a .NET expert (though I have developed a couple
of small and simple web applications using Visual Studio and
ASP.NET)
so I'm
not sure what the above error message is telling me. I *think* what's going on
is that something in the VB runtime threw an exeption?


Is this something that can be easily addressed? Can someone more knowledgeable
point me in the right direction? Or should I just hold off on
running
DotNetNuke on Mono until better compatibility with stuff written in

VB has been
established?

Thanks,

mbradley
_______________________________________________
Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list



_______________________________________________
Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________
Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list



_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list



_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to