Re: [Mono-dev] Windows/CygWin: Mono doesn't work after compiling
The hermes bags historical http://www.earlshop.com mens watches past news charcoal absorbing and arresting till date, and the designs with the http://www.sonbags.com designer handbags accoutrements from Hermes, Paris, seem to become an afflatus for abounding clean and accessible http://www.earlshop.com rolex watches look designers, and in addition for those alive accurately in the backpack market. The http://www.earlshop.com/Watches-Breitling.html breitling watches Hermes accoutrements may be calmly start at any from the official Hermes outlets or with authorised sellers of Hermes bags. You will find furthermore http://www.sonbags.com/gucci.html gucci bags abounding dealers of Hermes accoutrements who settle for web sites of their own, and advertise these accoutrements on the internet with http://www.sonbags.com/gucci-handbags.html gucci handbags considerable delivers of chargeless aircraft beyond the world, and some abundant discounts as well. You will discover abounding altered colour alternatives obtainable, and in excess of the a long time, the affectionate of abstracts referred http://www.earlshop.com/Watches-Franck-Muller.html Franck Muller to as to architecture the Kelly handbag settle for in addition changed, giving the archetypal structure abounding clean versions. It is possible to acquisition out about all these accoutrements at the Hermes web site, or at any of their retailers. So in the event you as well are absorbed with the news and http://www.sonbags.com/balenciaga.html balenciaga historical past abaft the authoritative of your Kelly Travelling bag, once again go and get your self a person of these accoutrements right now! 138. Search Louis Vuitton http://www.earlshop.com/Watches-Gucci.html gucci watches Bags on the internet -- View this message in context: http://software.1713.n2.nabble.com/Windows-CygWin-Mono-doesn-t-work-after-compiling-tp1394915p5707555.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
Thanks for the tip! I tried adding /cygdrive/c/Programs/Mono-2.0/bin to the end of my path, but it didn't seem to help. When I added it to the beginning of my path, it helped a lot, but I think that's because I was using only the pre-compiled binaries :) I noticed that I've got a lot of junk in my PATH, went back & cleaned it up, and now have just:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/e/Pers/Updates/Mono/CustomBuilt/install/bin:/cygdrive/c/Programs/Mono-2.0/bin mono -V (and mono --versio) still produce no output (at all). (Also, once the build is done, isn't it supposed to produce (or copy from the build directories) everything it needs, so that the new Mono build is completely self-sufficient? Also (just to make sure this doesn't get lost on this thread) - are there post-build verification (unit) tests that can be run, to verify that my new build works? Thanks! --Mike> To: mono-devel-list@lists.ximian.com> From: [EMAIL PROTECTED]> Date: Sat, 1 Nov 2008 13:57:25 +> Subject: Re: [Mono-dev] Windows/CygWin: Mono doesn't work after compiling> > Hi,> > MikeTheTall wrote:> > > >>> 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? > > You're missing all dependency dlls installed by Mono's Windows> installer into Mono's bin directory.> > Just assure that this directory is listed the PATH environment> variable after your install directory.> > Robert> > ___> Mono-devel-list mailing list> Mono-devel-list@lists.ximian.com> http://lists.ximian.com/mailman/listinfo/mono-devel-list___ 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
Hi, MikeTheTall wrote: > >>> 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? You're missing all dependency dlls installed by Mono's Windows installer into Mono's bin directory. Just assure that this directory is listed the PATH environment variable after your install directory. Robert ___ 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
Re: [Mono-dev] Windows/CygWin: Mono doesn't work after compiling
Hi, On Wed, Oct 29, 2008 at 8:00 PM, MikeTheTall <[EMAIL PROTECTED]> wrote: > > 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. > This usually happens when a dll needed by the executable (most likely libglib.dll or something like that) is not in the PATH. > 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), Don't do that. Executing gmcs.exe directly runs gmcs under the MS runtime, which won't work. Zoltan ___ 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
