[Mono-dev] Compiling Mono on CygWin/Windows: Monoburg problem?
Hello! I posted a couple of days back because I'd thought that my compilation of Mono on Windows (using CygWin, not the VS build) worked; apparently it didn't. I'm running into problems with the monoburg component of the build. The symptom of the problem is that it' not producing any output. I tried running it by hand, within the mono-2.0.1./mono/monoburg directory, using the line: ./monoburg ./sample.brg > sample.c Afterwards, sample.c is 0 bytes in size. This seems odd, but is the same symptom that I was seeing when the build finished (mono-based programs producing literally no output). Next, I tried running monoburg directly under the pre-compiled version of mono that I had already installed (which is what I thought I was doing - I had /cygdrive/c/Programs/Mono-2.0/bin/ in my path already) The thing that confuses me is that I've got my pre-compiled Mono's bin directory in my path, so if there are any needed .dll's, monoburg should find it there. When I try to run it under gdb, it exits with error code 0xc07b. catch stop, catch load, and a couple other things (catch start?) aren't implemented, which would seem to be the way to get a closer look at what's going on; 0xc07b appears to be a (?)Windows error code for "application did not initialize properly", which does suggest that a .DLL is missing, somewhere Sorry to bug y'all with this, but if anyone has any ideas about what to look at next, or what I might be doing wrong, I'd greatly appreciate it! THanks! --Mike -- View this message in context: http://www.nabble.com/Compiling-Mono-on-CygWin-Windows%3A-Monoburg-problem--tp20292758p20292758.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Windows/CygWin: Mono doesn't work after compiling
>> I'm having a bit of trouble compiling mono on Windows (using CygWin). >> The >> weird thing is that the compilation seems to have gone ok, but the >> mono/mcs/gmcs programs do nothing afterwards. >> > >This usually happens when a dll needed by the executable (most likely >libglib.dll or something like that) is not in the PATH. Thanks for the tip! Is there a way that I can find out what .DLLs it's missing? I have a really old copy of a Windows Dependency Walker (DEPENDS.EXE), which claims that I"ve got all the .DLLs that I need, but mono -V still does nothing. (Also - Depends.exe said that I was missing INTL.DLL, which was definitely not in the same bin directory as mono.exe - if this is actually required, shouldn't it have been built in the compilation process?) Even having a list of .DLLs from a text file (maybe a file that make uses) would be a great help! Also - are there any post-build verification (unit) tests that I can run, in order to double-check that my build actually went ok? Again - thank you (all) very much for the help - sorry for asking such newbie questions :) Thanks! --Mike -- View this message in context: http://www.nabble.com/Windows-CygWin%3A-Mono-doesn%27t-work-after-compiling-tp20233695p20276415.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Windows/CygWin: Mono doesn't work after compiling
Hello! I'm having a bit of trouble compiling mono on Windows (using CygWin). The weird thing is that the compilation seems to have gone ok, but the mono/mcs/gmcs programs do nothing afterwards. To compile, I followed the directions at http://www.mono-project.com/Compiling_Mono#Windows_Compilation. I started by installing the "Mono 2.0 For Windows" binaries onto my computer, got everything that CygWin needs, then grabbed the mono-2.0.1.tar.bz2 from http://ftp.novell.com/pub/mono/sources-stable/. I then tried to build everything, failed because I didn't have the right version of make (which I then got). With the older version of make everything seemed to compile just fine - there were no error messages printed at the end of the build. Now here's where it gets weird: when I add mono's bin directory to my path, and type "mono" into my bash shell, nothing happens. I hit enter, there's a brief pause, then the command prompt re-appears. There's no error messages (and "which mono" correctly identifies the mono.exe that I"m trying to use), but there's no output, either. mono -V also produces no output. When I run through the console basics example at http://mono-project.com/Mono_Basics, mcs and gmcs do no produce error messages, but they also don't produce a .exe, either. The other odd thing is that if I use the gmcs compiler directly (/lib/mono/2.0/gmcs.exe hello.cs), I get an exception (Unhandled Exception: System.ArgumentException: Illegal enum value: 2050. Parameter name: access), but if I use /lib/mono/1.0/mcs.exe hello.cs, it at least gives me a compiled .exe. At least for Windows, it looks like the compilers in $MONO_LOCATION/bin are just bash scripts that point to the above executables (I'm not sure why the scripts don't work, but the compilers themselves do) I'm really sorry for posting this, since I'm 100% sure that it's something I'm missing on my end, but if anyone has any suggestions, I'd love to hear them. I think I"m going to try a clean build again (in case the wrong make somehow messed things up), but I'm not really hopeful that that will fix things :} Thanks! --Mike -- View this message in context: http://www.nabble.com/Windows-CygWin%3A-Mono-doesn%27t-work-after-compiling-tp20233695p20233695.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
