RE: [Mono-devel-list] mono 1.1.8 - monodebug - what do i need to do tomake it run?
Currently, the only way to get mono-debugger working correctly is compiling it from source. We're still working on some prebuilt packages, and we will announce when they are ready. Wade P.S. The debugger was accidentally included in the 1.1.8.1 linux installer, but it does not work. On Thu, 2005-06-30 at 13:00 -0400, Gary M. Smithrud wrote: > Yes, they will coexist, but you need to make sure that the correct > libraries are being accessed by mono (1.1.8.1 and not 1.1.4). Mono, the > shell script, does this, but I think that it might not set things at the > beginning of PATH and LD_LIBRARY_PATH and the alternate version can be > retrieved instead. I just removed the old mono when I installed 1.1.8.1 > (noticed this with 1.1.7). You will need to check, since I am not > running Linux at the moment. > > Gary M. Smithrud > Haley Systems, Inc. > Phone: 724-934-7853 > [EMAIL PROTECTED] > www.haley.com > Moving at the Speed of Change > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of mike > horsley > Sent: Thursday, June 30, 2005 12:25 PM > To: mono-devel-list@lists.ximian.com > Subject: [Mono-devel-list] mono 1.1.8 - monodebug - what do i need to do > tomake it run? > > martin > > the "installer for all linux versions" is what i used to install the > latest mono version (1.1.8.1). > > i'm using suse 9.3 pro. > > several questions please: > > 1. mono (version 1.1.4?) was installed as part of the suse 9.3 install. > i didnt uninstall it because the readme for 1.1.8.1 suggests it will > co-exist with older versions. do you know if that is true? > > 2. i actually want to get to the state where i'm running monodevelop > with mdb integrated but had thought i'd go step-by-step. what do i need > to do to run autogen? (exact commands please). i have a c# app i want to > try moving over to linux but i cant really do much without a debugger. > > thanks > mike > > ___ > 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 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
RE: [Mono-devel-list] mono 1.1.8 - monodebug - what do i need to do tomake it run?
RPMs for mono-debugger have been posted to www.go-mono.com and are available in the OpenCarpet and yum channels. Wade On Fri, 2005-07-01 at 11:02 -0600, Wade Berrier wrote: > Currently, the only way to get mono-debugger working correctly is > compiling it from source. We're still working on some prebuilt > packages, and we will announce when they are ready. > > Wade > > P.S. The debugger was accidentally included in the 1.1.8.1 linux > installer, but it does not work. > > > On Thu, 2005-06-30 at 13:00 -0400, Gary M. Smithrud wrote: > > Yes, they will coexist, but you need to make sure that the correct > > libraries are being accessed by mono (1.1.8.1 and not 1.1.4). Mono, the > > shell script, does this, but I think that it might not set things at the > > beginning of PATH and LD_LIBRARY_PATH and the alternate version can be > > retrieved instead. I just removed the old mono when I installed 1.1.8.1 > > (noticed this with 1.1.7). You will need to check, since I am not > > running Linux at the moment. > > > > Gary M. Smithrud > > Haley Systems, Inc. > > Phone: 724-934-7853 > > [EMAIL PROTECTED] > > www.haley.com > > Moving at the Speed of Change > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of mike > > horsley > > Sent: Thursday, June 30, 2005 12:25 PM > > To: mono-devel-list@lists.ximian.com > > Subject: [Mono-devel-list] mono 1.1.8 - monodebug - what do i need to do > > tomake it run? > > > > martin > > > > the "installer for all linux versions" is what i used to install the > > latest mono version (1.1.8.1). > > > > i'm using suse 9.3 pro. > > > > several questions please: > > > > 1. mono (version 1.1.4?) was installed as part of the suse 9.3 install. > > i didnt uninstall it because the readme for 1.1.8.1 suggests it will > > co-exist with older versions. do you know if that is true? > > > > 2. i actually want to get to the state where i'm running monodevelop > > with mdb integrated but had thought i'd go step-by-step. what do i need > > to do to run autogen? (exact commands please). i have a c# app i want to > > try moving over to linux but i cant really do much without a debugger. > > > > thanks > > mike > > > > ___ > > 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 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
RE: [Mono-devel-list] mono 1.1.8 - monodebug - what do i need to do tomake it run?
The Mono Linux Installer (1.1.8.2_1) has been updated to include the mono-debugger. Wade On Tue, 2005-07-05 at 12:11 -0600, Wade Berrier wrote: > RPMs for mono-debugger have been posted to www.go-mono.com and are > available in the OpenCarpet and yum channels. > > Wade > > On Fri, 2005-07-01 at 11:02 -0600, Wade Berrier wrote: > > Currently, the only way to get mono-debugger working correctly is > > compiling it from source. We're still working on some prebuilt > > packages, and we will announce when they are ready. > > > > Wade > > > > P.S. The debugger was accidentally included in the 1.1.8.1 linux > > installer, but it does not work. > > > > > > On Thu, 2005-06-30 at 13:00 -0400, Gary M. Smithrud wrote: > > > Yes, they will coexist, but you need to make sure that the correct > > > libraries are being accessed by mono (1.1.8.1 and not 1.1.4). Mono, the > > > shell script, does this, but I think that it might not set things at the > > > beginning of PATH and LD_LIBRARY_PATH and the alternate version can be > > > retrieved instead. I just removed the old mono when I installed 1.1.8.1 > > > (noticed this with 1.1.7). You will need to check, since I am not > > > running Linux at the moment. > > > > > > Gary M. Smithrud > > > Haley Systems, Inc. > > > Phone: 724-934-7853 > > > [EMAIL PROTECTED] > > > www.haley.com > > > Moving at the Speed of Change > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of mike > > > horsley > > > Sent: Thursday, June 30, 2005 12:25 PM > > > To: mono-devel-list@lists.ximian.com > > > Subject: [Mono-devel-list] mono 1.1.8 - monodebug - what do i need to do > > > tomake it run? > > > > > > martin > > > > > > the "installer for all linux versions" is what i used to install the > > > latest mono version (1.1.8.1). > > > > > > i'm using suse 9.3 pro. > > > > > > several questions please: > > > > > > 1. mono (version 1.1.4?) was installed as part of the suse 9.3 install. > > > i didnt uninstall it because the readme for 1.1.8.1 suggests it will > > > co-exist with older versions. do you know if that is true? > > > > > > 2. i actually want to get to the state where i'm running monodevelop > > > with mdb integrated but had thought i'd go step-by-step. what do i need > > > to do to run autogen? (exact commands please). i have a c# app i want to > > > try moving over to linux but i cant really do much without a debugger. > > > > > > thanks > > > mike > > > > > > ___ > > > 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 > > ___ > 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-devel-list] mono 1.1.8.2 problems with mdb
Hi Mike, It almost sounds like the default mono that came with suse 9.3 is being used to run mdb without setting up the environment vars to find the libs included with the installer. The installer puts some settings in $HOME/.bashrc that need to be loaded. You can do this by starting a new shell or: ~/.bashrc This will set up your path correctly. Hopefully that helps. Also, make sure your ~/.bashrc file contains something similar: export PATH=$PATH:/opt/mono-1.1.8.2/bin export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/opt/mono-1.1.8.2/lib/pkgconfig" Wade On Thu, 2005-07-07 at 16:24 +0100, mike horsley wrote: > hi > > i downloaded the new linux installer for 1.1.8.2, installed it. i did > have to set $PATH because the new installed so maybe this is indicative > of another problem at my end. > > I compiled my test app "Main.cs" using -debug > > I then tried running mdb and got the following error: > > [EMAIL PROTECTED]:~/monotest1> mcs -debug Main.cs > [EMAIL PROTECTED]:~/monotest1> mdb Main.exe > > Unhandled Exception: System.TypeInitializationException: An exception > was thrown by the type initializer for > Mono.Debugger.Frontend.GnuReadLine ---> System.DllNotFoundException: > libmonodebuggerreadline > in (wrapper managed-to-native) > Mono.Debugger.Frontend.GnuReadLine:mono_debugger_readline_static_init () > in <0x7> Mono.Debugger.Frontend.GnuReadLine:.cctor ()--- End of > inner exception stack trace --- > > in <0x0> > in <0x00043> Mono.Debugger.Frontend.CommandLineInterpreter:Main > (System.String[] args) > [EMAIL PROTECTED]:~/monotest1> mdb > > Unhandled Exception: System.TypeInitializationException: An exception > was thrown by the type initializer for > Mono.Debugger.Frontend.GnuReadLine ---> System.DllNotFoundException: > libmonodebuggerreadline > in (wrapper managed-to-native) > Mono.Debugger.Frontend.GnuReadLine:mono_debugger_readline_static_init () > in <0x7> Mono.Debugger.Frontend.GnuReadLine:.cctor ()--- End of > inner exception stack trace --- > > in <0x0> > in <0x00043> Mono.Debugger.Frontend.CommandLineInterpreter:Main > (System.String[] args) > [EMAIL PROTECTED]:~/monotest1> > > As you can see, i get the same problem if i just launch mdb. > > I'm using SUSE 9.3 Pro with the GNOME desktop. > > Any ideas? > > regards > Mike > > > ___ > 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: re[2]: [Mono-devel-list] Re: mono 1.1.8.2 problems with mdb
The solution for SuSE 9.3 ended up being to install the compat-readline4 package. I may end up adding the readline binaries to the installer so that it doesn't matter if you have the readline4 binaries installed or not. Wade On Tue, 2005-07-12 at 16:35 +0100, Mike Horsley wrote: > Gary > > no. i'm using 32bit SUSE 9.3 pro. > > thanks > mike > > > > Do you have a 64 bit system? If so, then it wont load a 32-bit > library (at least it didnt for me when I was doing something else). > > > Gary M. Smithrud > Haley Systems, Inc. > Phone: 724-934-7853 > [EMAIL PROTECTED] > www.haley.com > Moving at the Speed of Change > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mike > Horsley > Sent: Tuesday, July 12, 2005 11:06 AM > To: Robert Jordan; mono-devel-list@lists.ximian.com > Subject: re: [Mono-devel-list] Re: mono 1.1.8.2 problems with mdb > > > Rob > > > > thanks. I checked this RPM and it was not installed. I installed it > and got the same problem. > > > > Might there be a sequencing issue? e.g., i need to have installed > readline-devel before installing mono? > > > > regards > > Mike > > > mike, > > >i downloaded the new linux installer for 1.1.8.2, installed it. i did > >have to set $PATH because the new installed so maybe this is > indicative > >of another problem at my end. > > > >I compiled my test app "Main.cs" using -debug > > > >I then tried running mdb and got the following error: > > > >[EMAIL PROTECTED]:~/monotest1> mcs -debug Main.cs > >[EMAIL PROTECTED]:~/monotest1> mdb Main.exe > > > >Unhandled Exception: System.TypeInitializationException: An exception > >was thrown by the type initializer for > >Mono.Debugger.Frontend.GnuReadLine ---> System.DllNotFoundException: > >libmonodebuggerreadline > > You must install the readline-devel RPM. > > Rob > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > __ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > __ > > < > > > > > > --- Original Message --- > > > > From: Robert Jordan <[EMAIL PROTECTED]> > > To: mono-devel-list@lists.ximian.com > > Date: Thu, 07 Jul 2005 22:12:39 +0200 > > Subject: [Mono-devel-list] Re: mono 1.1.8.2 problems with mdb > > > > mike, > > >i downloaded the new linux installer for 1.1.8.2, installed it. i did > >have to set $PATH because the new installed so maybe this is > indicative > >of another problem at my end. > > > >I compiled my test app "Main.cs" using -debug > > > >I then tried running mdb and got the following error: > > > >[EMAIL PROTECTED]:~/monotest1> mcs -debug Main.cs > >[EMAIL PROTECTED]:~/monotest1> mdb Main.exe > > > >Unhandled Exception: System.TypeInitializationException: An exception > >was thrown by the type initializer for > >Mono.Debugger.Frontend.GnuReadLine ---> System.DllNotFoundException: > >libmonodebuggerreadline > > You must install the readline-devel RPM. > > Rob > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > __ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > __ > __ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > __ > < > > > > > --- Original Message --- > > From: "Gary M. Smithrud" <[EMAIL PROTECTED]> > To: "Mike Horsley" <[EMAIL PROTECTED]>,"Robert Jordan" > <[EMAIL PROTECTED]>, > Date: Tue, 12 Jul 2005 11:12:38 -0400 > Subject: RE: [Mono-devel-list] Re: mono 1.1.8.2 problems with mdb > > Do you have a 64 bit system? If so, then it won’t load a 32-bit > library (at least it didn’t for me when I was doing something else). > > > > Gary M. Smithrud > > Haley Systems, Inc. > > Phone: 724-934-7853 > > [EMAIL PROTECTED] > > www.haley.com > > Moving at the Speed of Change > > > > __ > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mike > Horsley > Sent: Tuesday, July 12, 2005 11:06 AM > To: Robert Jordan; mono-devel-list@lists.ximia
Re: [Mono-dev] What about the Windows setup of Mono?
Hi Kornél, I'm working on the windows installer and it should be finished shortly. I'm shooting for today but it may be tomorrow. The good news is that after I'm done automating it the installers will be released in parallel with the mono releases. Your suggestions are very much appreciated. I believe (Paco, correct me if I'm wrong) the reason Paco used batch files instead of setting up environment variables was so that multiple mono versions could be installed in parallel. I will look into packaging libgdiplus with the installer. I think that's a great idea. Wade On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: > Hi, > > Is anyone working on it? When will it be released? > > Some suggestions: > I don't like to have bat files in bin directory while having executables in > lib directory. I think environment variables should be set in Windows > instead of using batch files. And I would like to have an option to add > mono\bin directory to PATH. > > Some others from the archive: > http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html > http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html > > Kornél > > ___ > 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] What about the Windows setup of Mono?
Take a look at svn for what I'm doing with the setup script: http://svn.myrealbox.com/viewcvs/trunk/release/windows-installer/ Specifically Mono_template.iss. The process I'm using is quite different than previous windows installers. That being said, there will potentially be some unexpected surprises with the installers being built this way because the process is so different. Please extend your (as in the mono community) patience as we work through any problems that may (and probably will) come up. Wade On Wed, 2005-09-28 at 23:58 +0200, Kornél Pál wrote: > These are good news.:) > > May I have a look at the setup script before you build the installer? > > Kornél > > - Original Message - > From: "Wade Berrier" <[EMAIL PROTECTED]> > To: > Sent: Wednesday, September 28, 2005 11:47 PM > Subject: Re: [Mono-dev] What about the Windows setup of Mono? > > > > Hi Kornél, > > > > I'm working on the windows installer and it should be finished shortly. > > I'm shooting for today but it may be tomorrow. > > > > The good news is that after I'm done automating it the installers will > > be released in parallel with the mono releases. > > > > Your suggestions are very much appreciated. > > > > I believe (Paco, correct me if I'm wrong) the reason Paco used batch > > files instead of setting up environment variables was so that multiple > > mono versions could be installed in parallel. > > > > I will look into packaging libgdiplus with the installer. I think > > that's a great idea. > > > > > > Wade > > > > > > > > On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: > >> Hi, > >> > >> Is anyone working on it? When will it be released? > >> > >> Some suggestions: > >> I don't like to have bat files in bin directory while having executables > >> in > >> lib directory. I think environment variables should be set in Windows > >> instead of using batch files. And I would like to have an option to add > >> mono\bin directory to PATH. > >> > >> Some others from the archive: > >> http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html > >> http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html > >> > >> Kornél > >> > >> ___ > >> 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 > > > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono 1.1.9.1 Windows Installer Released
Get 'em while it's hot: http://www.go-mono.com/archive/1.1.9.1_1/windows/mono-1.1.9.1-gtksharp-1.0.10-2.3.91-win32-0.exe Thanks for the suggestions and input. There are improvements to be made, but this should do for now. Let me know of any installer issues. Thanks Paco, you rock :) Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released
Hey,
On Fri, 2005-09-30 at 12:52 +0200, Kornél Pál wrote:
> Hi,
>
> AppID is {found} that will result in
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{found}_is1
> that seems to be bug in the script.
Thanks, this has been corrected.
>
> BTW is there any reason why you decided not to include gdiplus.dll?
>
I'm still waiting for Miguel to approve it. He wasn't sure if we should
or not.
Wade
> Kornél
>
> - Original Message -
> From: "Wade Berrier" <[EMAIL PROTECTED]>
> To: ;
> Cc: "Francisco Martinez" <[EMAIL PROTECTED]>
> Sent: Friday, September 30, 2005 12:37 PM
> Subject: [Mono-dev] Mono 1.1.9.1 Windows Installer Released
>
>
> > Get 'em while it's hot:
> >
> > http://www.go-mono.com/archive/1.1.9.1_1/windows/mono-1.1.9.1-gtksharp-1.0.10-2.3.91-win32-0.exe
> >
> > Thanks for the suggestions and input. There are improvements to be
> > made, but this should do for now. Let me know of any installer issues.
> >
> > Thanks Paco, you rock :)
> >
> >
> > Wade
> >
> > ___
> > 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] Mono 1.1.9.1 Windows Installer Released
I agree with not needing to set the env vars for the bat files. What about the SET/END LOCAL? I'm not sure what you're suggesting for this bug though: http://bugzilla.ximian.com/show_bug.cgi?id=54677 Wade On Fri, 2005-09-30 at 18:01 +0200, Kornél Pál wrote: > That's good. > > Then Batch files should look like this: > > @"C:\Program Files\Mono-1.1.9.1\bin\mono.exe" "C:\Program > Files\Mono-1.1.9.1\lib\mono\1.0\mcs.exe" %* > > Without new line at the end as it results in a prompt being displayed. > Otherwise @echo off should be used. > > There is no need for setting environment variables (the values we currently > set are default values and these variables are for external use) and long > file names can be used as we don't support 9x. Furthermore %* requires NT so > there is no use to use short file names. > > Using EXIT is not a good idea as when you call .bat files from other .bat > files all of them will exit resulting in similar behaviour as you use no > call command. When you call .bat files from .bat files using call they will > preserve ERRORLEVEL. > > There are shell scripts as well I think they should be used in cygwin. > > Kornél > > - Original Message - > From: "Zoltan Varga" <[EMAIL PROTECTED]> > To: "Kornél Pál" <[EMAIL PROTECTED]> > Cc: "Francisco Martinez" <[EMAIL PROTECTED]>; "Wade Berrier" > <[EMAIL PROTECTED]>; > Sent: Friday, September 30, 2005 5:33 PM > Subject: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released > > > It uses relative paths, so its ok. > >Zoltan > > On 9/30/05, Kornél Pál <[EMAIL PROTECTED]> wrote: > > Hi, > > > > >I take that back. I had MONO_CFG_DIR set in my environment, this is why > > >it didn't work. > > > > Is mono.exe using directories relative to it's own location or does it > > have > > any hardcoded paths? > > > > Kornél > > > > - Original Message - > > From: "Zoltan Varga" <[EMAIL PROTECTED]> > > To: "Wade Berrier" <[EMAIL PROTECTED]> > > Cc: "Francisco Martinez" <[EMAIL PROTECTED]>; > > > > Sent: Friday, September 30, 2005 4:37 PM > > Subject: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released > > > > > > Hi, > > > > > > - also, bug > > > > > > http://bugzilla.ximian.com/show_bug.cgi?id=75815 > > > > > > still doesn't work. The problem here is that the MONO_CFG_DIR > > > variable, which was > > > set in the mono.bat file in the past, is now not set at all, so the > > > runtime defaults to a > > > value from the build environment, i.e. > > > > > > C:\cygwin\usr\local\etc\mono\1.0\machine.config () > > > > > > I will try to fix this. > > > > > > > I take that back. I had MONO_CFG_DIR set in my environment, this is why > > it didn't work. > > > > Zoltan > > > > > - also, as Kornel said, the runtime should not be statically linked, > > > but instead it should be > > > dynamically linked against a mono-1.dll file. This should be the > > > default in our build process, so I don't know why this isn't > > > happening. What configure arguments are you > > > using when building the runtime ? > > > > > > Zoltan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 9/30/05, Wade Berrier <[EMAIL PROTECTED]> wrote: > > > > Get 'em while it's hot: > > > > > > > > http://www.go-mono.com/archive/1.1.9.1_1/windows/mono-1.1.9.1-gtksharp-1.0.10-2.3.91-win32-0.exe > > > > > > > > Thanks for the suggestions and input. There are improvements to be > > > > made, but this should do for now. Let me know of any installer > > > > issues. > > > > > > > > Thanks Paco, you rock :) > > > > > > > > > > > > Wade > > > > > > > > ___ > > > > 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 > > > > > ___ > 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
[Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
--- Begin Message --- > - also, as Kornel said, the runtime should not be statically linked, > but instead it should be > dynamically linked against a mono-1.dll file. This should be the > default in our build process, so I don't know why this isn't > happening. What configure arguments are you > using when building the runtime ? > First, from Kornél: "Note that most of your modifications are welcome and I like them (especially that you moved native exe's to bin directory)" I didn't do anything special here. That's the way the build came out. The only ./configure switch I used was "--prefix=" Here's the scoop on the static linking. I ended up compiling gtk-sharp 1 and 2 with Paco's snapshot of cygwin March of 2004. (gcc 3.3.1 cygming special). That was the only way I get get it to link. Then I noticed that when I built mono on the newest cygwin, the native exe's (mono.exe, monodis.exe, etc...) were statically linked and each around 9 MB. So, I then tried to compile mono under Paco's environment and ended up getting errors: /monobuild/mono/mono/handles/semdel: No such file or directory So I packaged up the statically linked version. I'd like to be able to build with the latest cygwin but have not been able to get it linking correctly: *** Warning: linker path does not have real file for library -lintl. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libintl and none of the candidates passed a file format test *** using a file magic. Last file checked: /cygdrive/c/mono/Mono-1.1.8.3/bin/libintl-1.dll *** Warning: libtool could not satisfy all declared inter-library *** dependencies of module libglibsharpglue. Therefore, libtool will create *** a static module, that should work as long as the dlopening *** application is linked with the -dlopen flag. ar cru .libs/libglibsharpglue.a error.o list.o object.o slist.o type.o unichar.o value.o valuearray.o ranlib .libs/libglibsharpglue.a creating libglibsharpglue.la I'm not sure why the file magic is failing with the latest cygwin. I would at least like to build with the same version of cygwin that our buildbot is using so that I don't run into all these last minute build issues. I was also thinking: maybe we should be using msys/mingw instead of cygwin. They provide a less-changing environment. Some excerpts from their website: .. (previously MinGW was a moving target with all the constant updates to individual packages, but now it is easier to verify things as being "MinGW 1.0 compatible"). ... The updates to this package and it's utilities are more controlled ... We're using the mingw compiler from cygwin anyway. That's the scoop. As soon as these issues are solved I'll be able to post a windows build of mono that includes the dll files. Wade --- End Message --- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released
On Fri, 2005-09-30 at 07:03 -0500, Francisco Martinez wrote: > > Wade it shows all the hard work you have put into this. Good job! > Since some of the exe(s) are now in a different location, I will have to > adjust the tools like MonoLaunch and the Visual Studio .NET add-in > (vsprj2make). However, that is the way it should be :) I am now > officially the third party and it is my responsibility to adjust to the > direction that Novell is setting on the installer. > Hi Paco, as noted in another message on the list, I didn't do any moving of the mono wrapper or the mono.exe. The make install set it up like that. Seems to be working fine though. Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released
How long has it used relative paths? I'm wondering because the linux installer still uses wrapper scripts for the native binaries (mono, monodis, etc...). Maybe that's not needed anymore as well? Wade On Fri, 2005-09-30 at 17:33 +0200, Zoltan Varga wrote: > It uses relative paths, so its ok. > >Zoltan > > On 9/30/05, Kornél Pál <[EMAIL PROTECTED]> wrote: > > Hi, > > > > >I take that back. I had MONO_CFG_DIR set in my environment, this is why > > >it didn't work. > > > > Is mono.exe using directories relative to it's own location or does it have > > any hardcoded paths? > > > > Kornél > > > > - Original Message - > > From: "Zoltan Varga" <[EMAIL PROTECTED]> > > To: "Wade Berrier" <[EMAIL PROTECTED]> > > Cc: "Francisco Martinez" <[EMAIL PROTECTED]>; > > > > Sent: Friday, September 30, 2005 4:37 PM > > Subject: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released > > > > > > Hi, > > > > > > - also, bug > > > > > > http://bugzilla.ximian.com/show_bug.cgi?id=75815 > > > > > > still doesn't work. The problem here is that the MONO_CFG_DIR > > > variable, which was > > > set in the mono.bat file in the past, is now not set at all, so the > > > runtime defaults to a > > > value from the build environment, i.e. > > > > > > C:\cygwin\usr\local\etc\mono\1.0\machine.config () > > > > > > I will try to fix this. > > > > > > > I take that back. I had MONO_CFG_DIR set in my environment, this is why > > it didn't work. > > > > Zoltan > > > > > - also, as Kornel said, the runtime should not be statically linked, > > > but instead it should be > > > dynamically linked against a mono-1.dll file. This should be the > > > default in our build process, so I don't know why this isn't > > > happening. What configure arguments are you > > > using when building the runtime ? > > > > > > Zoltan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 9/30/05, Wade Berrier <[EMAIL PROTECTED]> wrote: > > > > Get 'em while it's hot: > > > > > > > > http://www.go-mono.com/archive/1.1.9.1_1/windows/mono-1.1.9.1-gtksharp-1.0.10-2.3.91-win32-0.exe > > > > > > > > Thanks for the suggestions and input. There are improvements to be > > > > made, but this should do for now. Let me know of any installer issues. > > > > > > > > Thanks Paco, you rock :) > > > > > > > > > > > > Wade > > > > > > > > ___ > > > > 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 > > > > > ___ > 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: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
Hey, On Sat, 2005-10-01 at 02:23 +0200, Zoltan Varga wrote: > This works fine on my system using latest cygwin. My libint is in > /lib/libintl.a. Perhaps you don't have that package installed, or > libintl-1.dll is in a directory > in your PATH so libtool finds it first ? This same error happens with a lot of deps when I link (gmodule-2.0, gthread-2.0, glib-2.0, intl, iconv, ws2_32, psapi, ole32). I do have libintl-1.dll in my path. What should my environment be? Are you using the cygwin glib deps? I'm using the following glib deps: ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-2.6.6.zip ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-dev-2.6.6.zip http://www.gimp.org/~tml/gimp/win32/pkgconfig-0.15.zip http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip I'm using these so that I can build with them and also package them up for the installer. I guess the only other place I know about that I could get the deps is from gladewin32. He doesn't offer zip files (which is easier to automate with) but if I had to, I could create a zip file from what his installer lays down. I don't think that using the gladewin32 fixes the problem though. I still get the same errors when I build against the 1.1.8.3 mono installer, and 1.1.8.3 came with the gladewin32 files. Ideas? Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
Here's another error which makes me think something is wrong besides my environment or the libraries I have. *** Warning: linker path does not have real file for library -lole32. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libole32 and none of the candidates passed a file format test *** using a file magic. Last file checked: /lib/w32api/libole32.a *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. That's a file provided by cygwin in the w32api package. I'm trying to keep my cygwin installation to a minimum: autoconf automake bison cpio gcc-mingw-core gcc-mingw-g++ make openssh unzip zip wget cvs cygrunsrv patch subversion vim wget And of course other packages get selected by dependency. Am I missing something obvious? Wade On Mon, 2005-10-03 at 13:19 -0600, Wade Berrier wrote: > Hey, > > On Sat, 2005-10-01 at 02:23 +0200, Zoltan Varga wrote: > > > This works fine on my system using latest cygwin. My libint is in > > /lib/libintl.a. Perhaps you don't have that package installed, or > > libintl-1.dll is in a directory > > in your PATH so libtool finds it first ? > > This same error happens with a lot of deps when I link (gmodule-2.0, > gthread-2.0, glib-2.0, intl, iconv, ws2_32, psapi, > ole32). > > I do have libintl-1.dll in my path. What should my environment be? > > Are you using the cygwin glib deps? I'm using the following glib deps: > > ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-2.6.6.zip > ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-dev-2.6.6.zip > http://www.gimp.org/~tml/gimp/win32/pkgconfig-0.15.zip > http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip > http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip > > I'm using these so that I can build with them and also package them up > for the installer. > > I guess the only other place I know about that I could get the deps is > from gladewin32. He doesn't offer zip files (which is easier to > automate with) but if I had to, I could create a zip file from what his > installer lays down. > > I don't think that using the gladewin32 fixes the problem though. I > still get the same errors when I build against the 1.1.8.3 mono > installer, and 1.1.8.3 came with the gladewin32 files. > > Ideas? > > Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
Hey, A little while ago I discovered a dumb mistake on my part: I didn't have libtool installed. It's installed now and here's my cygwin versions: $ libtool --version ltmain.sh (GNU libtool) 1.5.20 (1.1220.2.287 2005/08/31 18:54:15) $ automake --version automake (GNU automake) 1.9.6 Also, I'm building from the mono 1.1.9.1 tarball, not from the tag or trunk: http://go-mono.com/sources/mono-1.1/mono-1.1.9.1.tar.gz So, now when I build, the .dll files are generated, but now the build fails with the same error I got when building under Paco's cygwin environment of Mar 2004: MONO_PATH="../../class/lib/basic; $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper ../../class/lib/basic/mcs.exe /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB /debug+ /debug:full /noconfig -r:mscorlib.dll -r:System.dll -nowarn:0162 -nowarn:0618 -nowarn:0612 -target:library -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr '/' ''` @../../build/deps/basic_System.Xml.dll.response make[8]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' make[7]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' make[6]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class' make[5]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 255 make[7]: *** [do-all] Error 2 make[6]: *** [all-recursive] Error 1 make[5]: *** [all-recursive] Error 1 make[4]: *** [profile-do--basic--all] Error 2 make[3]: *** [profiles-do--all] Error 2 make[4]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' make[3]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' make[2]: Leaving directory `/tmp/scratch/mono-1.1.9.1/runtime' make[1]: Leaving directory `/tmp/scratch/mono-1.1.9.1' /tmp/scratch/mono-1.1.9.1/libtool: line 6594: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: No such file or directory /tmp/scratch/mono-1.1.9.1/libtool: line 6594: exec: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: cannot execute: No such file or directory make[2]: *** [all-local] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Then I go into mono/handles where semdel.c is and when I run make, I get a slew of errors. Looks like some clash with the win32 api...? I'll attach the log. I'll also CC Dick because is looks like he does a lot with semdel. Getting closer. Wade On Tue, 2005-10-04 at 00:00 +0200, Zoltan Varga wrote: > Hi, > > mono builds fine using the latest cygwin libs for me. Altought, it > is still statically linked > even if I tell disable it, so its not all good. What version of > automake and libtool are you using, ie what does automake --version > and libtool --version return ? > > Zoltan > > On 10/3/05, Wade Berrier <[EMAIL PROTECTED]> wrote: > > Here's another error which makes me think something is wrong besides my > > environment or the libraries I have. > > > > *** Warning: linker path does not have real file for library -lole32. > > *** I have the capability to make that library automatically link in > > when > > *** you link to this library. But I can only do this if you have a > > *** shared version of the library, which you do not appear to have > > *** because I did check the linker path looking for a file starting > > *** with libole32 and none of the candidates passed a file format test > > *** using a file magic. Last file checked: /lib/w32api/libole32.a > > *** The inter-library dependencies that have been dropped here will be > > *** automatically added whenever a program is linked with this library > > *** or is declared to -dlopen it. > > > > That's a file provided by cygwin in the w32api package. I'm trying to > > keep my cygwin installation to a minimum: > > > > autoconf > > automake > > bison > > cpio > > gcc-mingw-core > > gcc-mingw-g++ > > make > > > > openssh > > unzip > > zip > > wget > > > > cvs > > cygrunsrv > > patch > > subversion > > vim > > wget > > > > And of course other packages get selected by dependency. > > > > Am I missing something obvious? > > > > Wade > > > > > > On Mon, 2005-10-03 at 13:19 -0600, Wade Berrier wrote: > > > Hey, > > > > > > On Sat, 2005-10-01 at 02:23 +0200, Zoltan Varga wrote: > > > > > > > This works fine on my system using latest cygwin. My libint is in > > > > /lib/libintl.a. Perhaps you don't have that package installed, or
Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
One more note, looks like monodis.exe, mono.exe, and monograph.exe were not statically linked. On Mon, 2005-10-03 at 18:05 -0600, Wade Berrier wrote: > Hey, > > A little while ago I discovered a dumb mistake on my part: I didn't > have libtool installed. > > It's installed now and here's my cygwin versions: > > $ libtool --version > ltmain.sh (GNU libtool) 1.5.20 (1.1220.2.287 2005/08/31 18:54:15) > > $ automake --version > automake (GNU automake) 1.9.6 > > Also, I'm building from the mono 1.1.9.1 tarball, not from the tag or > trunk: > > http://go-mono.com/sources/mono-1.1/mono-1.1.9.1.tar.gz > > So, now when I build, the .dll files are generated, but now the build > fails with the same error I got when building under Paco's cygwin > environment of Mar 2004: > > MONO_PATH="../../class/lib/basic; > $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper > ../../class/lib/basic/mcs.exe /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 > -d:BOOTSTRAP_WITH_OLDLIB /debug+ /debug:full /noconfig -r:mscorlib.dll > -r:System.dll -nowarn:0162 -nowarn:0618 -nowarn:0612 -target:library > -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs > Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr '/' > ''` @../../build/deps/basic_System.Xml.dll.response > make[8]: Leaving directory > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > make[7]: Leaving directory > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > make[6]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class' > make[5]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 255 > make[7]: *** [do-all] Error 2 > make[6]: *** [all-recursive] Error 1 > make[5]: *** [all-recursive] Error 1 > make[4]: *** [profile-do--basic--all] Error 2 > make[3]: *** [profiles-do--all] Error 2 > make[4]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > make[3]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > make[2]: Leaving directory `/tmp/scratch/mono-1.1.9.1/runtime' > make[1]: Leaving directory `/tmp/scratch/mono-1.1.9.1' > /tmp/scratch/mono-1.1.9.1/libtool: line > 6594: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: No such file or > directory > /tmp/scratch/mono-1.1.9.1/libtool: line 6594: > exec: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: cannot execute: No > such file or directory > make[2]: *** [all-local] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > > Then I go into mono/handles where semdel.c is and when I run make, I get > a slew of errors. Looks like some clash with the win32 api...? I'll > attach the log. I'll also CC Dick because is looks like he does a lot > with semdel. > > Getting closer. > > Wade > > > On Tue, 2005-10-04 at 00:00 +0200, Zoltan Varga wrote: > > Hi, > > > > mono builds fine using the latest cygwin libs for me. Altought, it > > is still statically linked > > even if I tell disable it, so its not all good. What version of > > automake and libtool are you using, ie what does automake --version > > and libtool --version return ? > > > > Zoltan > > > > On 10/3/05, Wade Berrier <[EMAIL PROTECTED]> wrote: > > > Here's another error which makes me think something is wrong besides my > > > environment or the libraries I have. > > > > > > *** Warning: linker path does not have real file for library -lole32. > > > *** I have the capability to make that library automatically link in > > > when > > > *** you link to this library. But I can only do this if you have a > > > *** shared version of the library, which you do not appear to have > > > *** because I did check the linker path looking for a file starting > > > *** with libole32 and none of the candidates passed a file format test > > > *** using a file magic. Last file checked: /lib/w32api/libole32.a > > > *** The inter-library dependencies that have been dropped here will be > > > *** automatically added whenever a program is linked with this library > > > *** or is declared to -dlopen it. > > > > > > That's a file provided by cygwin in the w32api package. I'm trying to > > > keep my cygwin installation to a minimum: > > > > > > autoconf > > > automake > > > bison > > > cpio > > > gcc-mingw-core > > > gcc-mingw-g++ > > > make > > > > > > openssh > > > u
Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
I almost think that System.XML isn't compiling. This command doesn't output a dll: MONO_PATH="../../class/lib/basic; $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper ../../class/lib/basic/mcs.exe /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB /debug+ /debug:full /noconfig -r:mscorlib.dll -r:System.dll -nowarn:0162 -nowarn:0618 -nowarn:0612 -target:library -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr '/' ''` @../../build/deps/basic_System.Xml.dll.response Yet using the locally compiled mcs does output a dll: mcs /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB /debug+ /debug:full /noconfig -r:mscorlib.dll -r:System.dll -nowarn:0162 -nowarn:0618 -nowarn:0612 -target:library -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr '/' ''` @../../build/deps/basic_System.Xml.dll.response That's about all I've been able to figure out. Wade On Mon, 2005-10-03 at 18:07 -0600, Wade Berrier wrote: > One more note, looks like monodis.exe, mono.exe, and monograph.exe were > not statically linked. > > On Mon, 2005-10-03 at 18:05 -0600, Wade Berrier wrote: > > Hey, > > > > A little while ago I discovered a dumb mistake on my part: I didn't > > have libtool installed. > > > > It's installed now and here's my cygwin versions: > > > > $ libtool --version > > ltmain.sh (GNU libtool) 1.5.20 (1.1220.2.287 2005/08/31 18:54:15) > > > > $ automake --version > > automake (GNU automake) 1.9.6 > > > > Also, I'm building from the mono 1.1.9.1 tarball, not from the tag or > > trunk: > > > > http://go-mono.com/sources/mono-1.1/mono-1.1.9.1.tar.gz > > > > So, now when I build, the .dll files are generated, but now the build > > fails with the same error I got when building under Paco's cygwin > > environment of Mar 2004: > > > > MONO_PATH="../../class/lib/basic; > > $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper > > ../../class/lib/basic/mcs.exe /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 > > -d:BOOTSTRAP_WITH_OLDLIB /debug+ /debug:full /noconfig -r:mscorlib.dll > > -r:System.dll -nowarn:0162 -nowarn:0618 -nowarn:0612 -target:library > > -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs > > Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr '/' > > ''` @../../build/deps/basic_System.Xml.dll.response > > make[8]: Leaving directory > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > > make[7]: Leaving directory > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > > make[6]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class' > > make[5]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > > make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 255 > > make[7]: *** [do-all] Error 2 > > make[6]: *** [all-recursive] Error 1 > > make[5]: *** [all-recursive] Error 1 > > make[4]: *** [profile-do--basic--all] Error 2 > > make[3]: *** [profiles-do--all] Error 2 > > make[4]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > > make[3]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > > make[2]: Leaving directory `/tmp/scratch/mono-1.1.9.1/runtime' > > make[1]: Leaving directory `/tmp/scratch/mono-1.1.9.1' > > /tmp/scratch/mono-1.1.9.1/libtool: line > > 6594: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: No such file or > > directory > > /tmp/scratch/mono-1.1.9.1/libtool: line 6594: > > exec: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: cannot execute: No > > such file or directory > > make[2]: *** [all-local] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all] Error 2 > > > > Then I go into mono/handles where semdel.c is and when I run make, I get > > a slew of errors. Looks like some clash with the win32 api...? I'll > > attach the log. I'll also CC Dick because is looks like he does a lot > > with semdel. > > > > Getting closer. > > > > Wade > > > > > > On Tue, 2005-10-04 at 00:00 +0200, Zoltan Varga wrote: > > > Hi, > > > > > > mono builds fine using the latest cygwin libs for me. Altought, it > > > is still statically linked > > > even if I tell disable it, so its not all good. What version of > > > automake and libtool are you using, ie what does automake --ve
Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
On Tue, 2005-10-04 at 15:14 +0200, Zoltan Varga wrote: > Hi, > > The problem is not with System.XML, but with the runtime itself. The > line which compiles > System.XML is the first time the newly compiled runtime is executed, > all prior commands > use the locally installed mcs and the locally installed runtime. Try running > > /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper > > without any parameters to see if the runtime works at all. > You're right on this one. Running this doesn't do anything except return an error code of 255. So it probably turns out that System.XML is the first dll that gets compiled from the mini wrapper? I wonder what could be causing this? Wade > On 10/4/05, Raja R Harinath <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Wade Berrier <[EMAIL PROTECTED]> writes: > > > > [snip] > > > So, now when I build, the .dll files are generated, but now the build > > > fails with the same error I got when building under Paco's cygwin > > > environment of Mar 2004: > > > > > > MONO_PATH="../../class/lib/basic; > > > $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper > > > ../../class/lib/basic/mcs.exe /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 > > > -d:BOOTSTRAP_WITH_OLDLIB /debug+ /debug:full /noconfig -r:mscorlib.dll > > > -r:System.dll -nowarn:0162 -nowarn:0618 -nowarn:0612 -target:library > > > -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs > > > Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr '/' > > > ''` @../../build/deps/basic_System.Xml.dll.response > > > make[8]: Leaving directory > > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > > > make[7]: Leaving directory > > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > > > make[6]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class' > > > make[5]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > > > make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 255 > > > > This is the actual error. It probably means that the runtime couldn't > > execute (it uses mono-wrapper). > > > > > /tmp/scratch/mono-1.1.9.1/libtool: line > > > 6594: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: No such file or > > > directory > > > /tmp/scratch/mono-1.1.9.1/libtool: line 6594: > > > exec: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: cannot execute: No > > > such file or directory > > > > This is not actually an error, even though it looks like one. > > > > - Hari > > > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
On Tue, 2005-10-04 at 18:36 +0200, Kornél Pál wrote: > > From: Wade Berrier > > So it probably turns out that System.XML is the first dll that gets > > compiled from the mini wrapper? > > Yes, it is, but this was mentioned by Zoltán in the message you replyed to: > > >> From: Zoltan Varga > >> The line which compiles System.XML is the first time the newly > >> compiled runtime is executed, ... True, must have missed that, thank you for pointing that out. > > Also note that I get some zombie mono.exe like this when I use a glib that > is compiled to use cygwin (or use cygwing glib-devel package). So check this > as it may be the cause of the behaviour you experience. As noted in a previous email in this thread, I'm using the glib deps from listed on tml's win32 gtk download page: ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-2.6.6.zip ftp://ftp.gtk.org/pub/gtk/v2.6/win32/glib-dev-2.6.6.zip http://www.gimp.org/~tml/gimp/win32/pkgconfig-0.15.zip http://www.gimp.org/~tml/gimp/win32/libiconv-1.9.1.bin.woe32.zip http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip Also, Zoltan is also having the same issues that I'm having with the latest cygwin, where as he was able to compile about a month ago. Are you able to build? If so, are you using the latest cygwin? What deps are you using? Wade > > Kornél > > - Original Message - > From: "Wade Berrier" <[EMAIL PROTECTED]> > To: "Zoltan Varga" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; "Raja R Harinath" <[EMAIL PROTECTED]>; > > Sent: Tuesday, October 04, 2005 6:09 PM > Subject: Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released] > > > > On Tue, 2005-10-04 at 15:14 +0200, Zoltan Varga wrote: > >> Hi, > >> > >> The problem is not with System.XML, but with the runtime itself. The > >> line which compiles > >> System.XML is the first time the newly compiled runtime is executed, > >> all prior commands > >> use the locally installed mcs and the locally installed runtime. Try > >> running > >> > >> /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper > >> > >> without any parameters to see if the runtime works at all. > >> > > > > You're right on this one. Running this doesn't do anything except > > return an error code of 255. > > > > So it probably turns out that System.XML is the first dll that gets > > compiled from the mini wrapper? > > > > I wonder what could be causing this? > > > > Wade > > > > > > > > > >> On 10/4/05, Raja R Harinath <[EMAIL PROTECTED]> wrote: > >> > Hi, > >> > > >> > Wade Berrier <[EMAIL PROTECTED]> writes: > >> > > >> > [snip] > >> > > So, now when I build, the .dll files are generated, but now the build > >> > > fails with the same error I got when building under Paco's cygwin > >> > > environment of Mar 2004: > >> > > > >> > > MONO_PATH="../../class/lib/basic; > >> > > $MONO_PATH" /tmp/scratch/mono-1.1.9.1/runtime/mono-wrapper > >> > > ../../class/lib/basic/mcs.exe /nologo > >> > > /optimize -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB /debug+ > >> > > /debug:full > >> > > /noconfig -r:mscorlib.dll -r:System.dll -nowarn:0162 -nowarn:0618 > >> > > -nowarn:0612 > >> > > -target:library -out:System.Xml.dll `echo System.Xml.XPath/Parser.cs > >> > > Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs | tr > >> > > '/' ''` @../../build/deps/basic_System.Xml.dll.response > >> > > make[8]: Leaving directory > >> > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > >> > > make[7]: Leaving directory > >> > > `/tmp/scratch/mono-1.1.9.1/mcs/class/System.XML' > >> > > make[6]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs/class' > >> > > make[5]: Leaving directory `/tmp/scratch/mono-1.1.9.1/mcs' > >> > > make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 255 > >> > > >> > This is the actual error. It probably means that the runtime couldn't > >> > execute (it uses mono-wrapper). > >> > > >> > > /tmp/scratch/mono-1.1.9.1/libtool: line > >> > > 6594: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: No such file or > >> > > directory > >> > > /tmp/scratch/mono-1.1.9.1/libtool: line 6594: > >> > > exec: /tmp/scratch/mono-1.1.9.1/mono/handles/semdel: cannot execute: > >> > > No > >> > > such file or directory > >> > > >> > This is not actually an error, even though it looks like one. > >> > > >> > - Hari > >> > > >> > > > > ___ > > 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: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released]
Hi Kornél, Thanks for the details! I guess the only question I have is whether the 1.1.9.1 tarball works for you in this environment. Zoltan checked in a libtool patch into trunk that fixes the issues I was having: http://lists.ximian.com/pipermail/mono-patches/2005-October/065089.html Sorry the gettext-dev wasn't on the list, it was left out for some reason. I like using the zip files for build time deps and they are easy to include with the installer. We're getting there... Thanks again! Wade On Wed, 2005-10-05 at 02:24 +0200, Kornél Pál wrote: > > Are you able to build? If so, are you using the latest cygwin? What > > deps are you using? > > I tried to reproduce you build environment: > > I installed a brand new basic cygwin (latest installer, latest packages) > only with default components and Mono requirements selected. (See later the > exact list of packages.) > > Then I extracted the directories inside the zip's you listed to C:\cygwin or > C:\cygwin\usr depending on where the target directory existed. Overwritten > existing > files. Edited glib-2.0 .pc files to make prefix=/usr. > > Executed: > autogen.sh, make, make install. > > Everything compiled, mono-1.dll and MonoPosixHelper.dll were created and > exe's link to mono-1.dll. Binaries are not dependent on cygwin. So I got the > result I expected. > > Note that however that I had to download and install gettext-dev-0.14.5.zip > as well that wasn't listed by you. If you used this package from cygwin it > may cause problems but I did not try it. > > Also note that I prefer to use cygwin pkgconf as Win32 pkgconf replaces > prefix in .pc with ../../ relative to the .pc file that is something I > really don't like. So I did not use pkgconfig-0.15.zip at all. I used cygwin > pkgconfig instead. > > As I can remember I selected the following components in Devel and the > others were added by the setup: > > autoconf > automake > binutils > bison > gcc > libtool > make > > Exact list of installed packages (from install log): > terminfo > texinfo > _update-info-dir > libreadline6 > libncurses8 > bash > base-passwd > libiconv2 > libintl2 > cygwin > libintl3 > alternatives > ash > m4 > libgdbm4 > libdb4.2 > libdb4.3 > crypt > expat > bzip2 > libbz2_1 > perl > mktemp > autoconf2.1 > autoconf2.5 > autoconf > automake1.4 > automake1.6 > automake1.7 > automake1.8 > automake1.9 > coreutils > findutils > sed > base-files > binutils > bison > libncurses7 > ncurses > clear > cygrunsrv > libpopt0 > cygutils > gawk > groff > gzip > termcap > libpcre0 > less > libcharset1 > libiconv > man > cygwin-doc > diffutils > editrights > zlib > file > w32api > mingw-runtime > gcc-mingw-core > gcc-core > gcc-mingw-g++ > gcc-g++ > gcc > libgdbm3 > gdbm > glib > libintl1 > libintl > grep > libapr0 > libgdbm > libgdbm-devel > libltdl3 > libncurses5 > libncurses6 > libreadline4 > libreadline5 > libtool1.5 > openssl097 > openssl > links > login > lynx > make > mc > minires > openssh > patch > patchutils > pkgconfig > tar > wget > which > > Note that this list includes some of my needs not required by Mono like mc, > wget, openssh, patch, ... > > And of course this list don't include dependencies installed from zip files. > > And note that libiconv was installed as something needed it, but was > overwritten with the version in the zip file. > > I like this new environment so I decided to use it instead of my previous > cygwin installation that has some older and some unnecessary packages.:) > > Hope this helps. > > Kornél > > - Original Message - > From: "Wade Berrier" <[EMAIL PROTECTED]> > To: "Kornél Pál" <[EMAIL PROTECTED]> > Cc: "Zoltan Varga" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Raja R Harinath" > <[EMAIL PROTECTED]>; > Sent: Tuesday, October 04, 2005 7:26 PM > Subject: Re: [Fwd: Re: [Mono-dev] Mono 1.1.9.1 Windows Installer Released] > > > > On Tue, 2005-10-04 at 18:36 +0200, Kornél Pál wrote: > >> > From: Wade Berrier > >> > So it probably turns out that System.XML is the first dll that gets > >> > compiled from the mini wrapper? > >> > >> Yes, it is, but this was mentioned by Zoltán in the message you replyed > >> to: > >> > >> >> From: Zoltan Varga > >> >> The line which compiles System.XML is the first time the newly > >> &g
Re: [Mono-dev] Building Mono on Windows is extremely slow
Could also cross compile from linux :) Right now ./configure treats mingw and cygwin the same. You'd have to make some adjustments for the mingw target, but the compile times would definitely be faster. Wade On Thu, 2005-10-06 at 06:52 -0400, Jonathan Pryor wrote: > On Wed, 2005-10-05 at 13:32 +0200, Kornél Pál wrote: > > Building Mono on Windows is much slower than building it on Linux for > > example. The problem seems to be that our scripts use a lot of processes. > > Processes on Linux are lightweight but are heavyweight on Windows that > > results in delays because of process construction and destruction. Can > > anything be done to speed up build? > > Not without using something other than automake/autoconf, since it's the > `configure' script that's responsible for most of that process > generation (creating & compiling test programs to check for libraries > and functions, checking for the presence of programs, checking for...). > > Alternatively, create a Makefile (or similar) setup explicitly for Win32 > users, so they don't have to run configure (if you want to assume that > all Win32 systems are alike). Of course, then you'd have to deal with > synchronization issues... > > - Jon > > > ___ > 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] What about the Windows setup of Mono?
Hi Jim, I currently delete the .la and .a files from the windows installer to conserve space. I'm not sure of an easier way to do this. Wade On Thu, 2005-09-29 at 10:49 +0100, Jim Purbrick wrote: > Hi Wade, > > I'd really like mono.dll and mono.lib files packaged > with the Windows install so I can embed mono on > Windows. Currently I have to use cygwin to build on > Windows from source just to generate a dll and lib to > link against (there may be an easier way to do this, > please let me know). > > Cheers, > > Jim. > > --- Daniel Morgan <[EMAIL PROTECTED]> wrote: > > > Hopefully, you can continue allowing the Mono Win32 > > installers to allow > > parallel installs. > > > > I need the ability to have multiple versions of mono > > installed. Some > > application working in one version, such as, Mono > > 1.1.6 do not work in > > Mono 1.1.8. > > > > Wade Berrier wrote: > > > > >Hi Kornél, > > > > > >I'm working on the windows installer and it should > > be finished shortly. > > >I'm shooting for today but it may be tomorrow. > > > > > >The good news is that after I'm done automating it > > the installers will > > >be released in parallel with the mono releases. > > > > > >Your suggestions are very much appreciated. > > > > > >I believe (Paco, correct me if I'm wrong) the > > reason Paco used batch > > >files instead of setting up environment variables > > was so that multiple > > >mono versions could be installed in parallel. > > > > > >I will look into packaging libgdiplus with the > > installer. I think > > >that's a great idea. > > > > > > > > >Wade > > > > > > > > > > > >On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál > > wrote: > > > > > > > > >>Hi, > > >> > > >>Is anyone working on it? When will it be released? > > >> > > >>Some suggestions: > > >>I don't like to have bat files in bin directory > > while having executables in > > >>lib directory. I think environment variables > > should be set in Windows > > >>instead of using batch files. And I would like to > > have an option to add > > >>mono\bin directory to PATH. > > >> > > >>Some others from the archive: > > > >>http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html > > > >>http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html > > >> > > >>Kornél > > >> > > >>___ > > >>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 > > > > > > > > > > > > > ___ > > Mono-devel-list mailing list > > Mono-devel-list@lists.ximian.com > > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > > > ___ > How much free photo storage do you get? Store your holiday > snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Installers and relative paths
The latest Windows installer doesn't set any environment variables in the wrapper scripts and batch files (MONO_PATH, etc...). This works fine in finding the gac binaries. I've looked into doing this for the linux installer as well, and some programs didn't work. gmcs worked, but mcs didn't (couldn't locate a hardcoded dll). Why would this be different on the different oses? Is only windows set up to use relative paths? Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] libgdiplus gcc4 cairo patch
Hey, I noticed this in SuSE autobuild... looks like gcc4 was updated in SuSE's build system and now this patch is required to build libgdiplus. Wade --- cairo/pixman/src/pixman-remap.h 2005-08-29 20:11:27.0 +0200 +++ cairo/pixman/src/pixman-remap.h 2005-11-21 18:36:11.200147358 +0100 @@ -1,9 +1,9 @@ #define pixman_add_trapezoids _cairo_pixman_add_trapezoids -#define INT_pixman_color_to_pixel _cairo_pixman_color_to_pixel +/* #define INT_pixman_color_to_pixel _cairo_pixman_color_to_pixel */ #define pixman_color_to_pixel _cairo_pixman_color_to_pixel #define composeFunctions _cairo_pixman_compose_functions #define fbComposeSetupMMX _cairo_pixman_compose_setup_mmx -#define INT_pixman_composite _cairo_pixman_composite +/* #define INT_pixman_composite _cairo_pixman_composite */ #define pixman_composite _cairo_pixman_composite #define fbCompositeCopyAreammx _cairo_pixman_composite_copy_area_mmx #define fbCompositeSolidMask_nxx0565Cmmx _cairo_pixman_composite_solid_mask_nxx0565Cmmx signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono daily packages missing
The daily downloads are now updated and will happen at 1 am EST. Also, the bug where mono-latest.tar.gz pointing to the wrong file has been fixed. (It previously pointed to 1.1.9 downloads instead of 1.1.10). Wade On Thu, 2005-12-01 at 10:44 -0500, Miguel Icaza wrote: > Hello, > > > there haven't been any new mono daily packages on > > http://mono.ximian.com/daily/ since November 10th. Is it a build problem ? > > > > I'm using these packages for regression benchmarks - I've added IA64 > > platform recently - (http://nenya.ms.mff.cuni.cz/projects/mono), but the > > benchmarks are most useful for the latest versions, of course > > We are working on restoring the daily builds. > > Miguel. > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] How to get mdb to work as installed with the Mono 1.1.12 Linux installer
Hi Hans,
Thanks for the great feedback and solution. The debugger needs some
slight changes in order to work in a relocated environment.
I went ahead and filed a bug:
http://bugzilla.ximian.com/show_bug.cgi?id=77062
Wade
On Wed, 2005-12-21 at 18:42 +0100, Hans Kratz wrote:
> Hi!
>
> I tried to use mdb for some Mono.Debugger library testing and
> encountered some some problems with the way it is shipped in the Mono
> 1.1.12 Linux installer.
>
> I used the installer to install mono in my home directory on Debian
> Unstable.
>
>
> The problems:
>
> 1) mdb does not start.
>
> [EMAIL PROTECTED]:~$ cat ~/mono-1.1.12/bin/mdb
> mono --debug /usr/lib/mono/1.0/mdb.exe $*
>
> As you can see the assembly path is wrong causing mdb to fail on
> startup. Furthermore exec should be used and the full path to the mono
> binary should be specified (as is done e.g. in the mcs shell script).
>
>
> 2) Starting mdb using the correct path does not work either.
>
> [EMAIL PROTECTED]:~$ ~/mono-1.1.12/bin/mono ~/mono-1.1.12/lib/mono/1.0/mdb.exe
>
> Unhandled Exception: System.TypeInitializationException: An exception
> was thrown by the type initializer for
> Mono.Debugger.Frontend.CommandLineInterpreter --->
> System.DllNotFoundException: monodebuggerserver
> in (wrapper managed-to-native)
> Mono.Debugger.Frontend.CommandLineInterpreter:mono_debugger_server_static_init
>
> ()
> in <0x7> Mono.Debugger.Frontend.CommandLineInterpreter:.cctor ()---
> End of inner exception stack trace ---
>
> I am not sure how this is supposed to work. Setting the LD_LIBRARY_PATH
> helped however:
>
> [EMAIL PROTECTED]:~$ export LD_LIBRARY_PATH=~/mono-1.1.12/lib/
> [EMAIL PROTECTED]:~$ ~/mono-1.1.12/bin/mono ~/mono-1.1.12/lib/mono/1.0/mdb.exe
> Mono Debugger
> (mdb)
>
>
> 3) Even then mdb can not be used for actual debugging.
>
> [EMAIL PROTECTED]:/tmp/Debug$ ~/mono-1.1.12/bin/mono
> ~/mono-1.1.12/lib/mono/1.0/mdb.exe ConsoleApplication70.exe
> Mono Debugger
> (mdb) run
> Starting program: ConsoleApplication70.exe
> Corlib not in sync with this runtime: expected corlib version 45, found 41.
> Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.
>
> Here mdb tries to use /usr/lib/mono/1.0/mscorlib.dll. I assume this is
> because mdb starts the child process using mono-debugger-mini-wrapper
> and mono-debugger-mini-wrapper is not recognized in mono/os/unix/util.c
> which is responsible for the correct setup via mono_set_dirs.
>
> Setting MONO_PATH and MONO_CFG_DIR manually seems to resolve this:
>
> [EMAIL PROTECTED]:/tmp/Debug$ export MONO_PATH=~/mono-1.1.12/lib/mono/1.0/
> [EMAIL PROTECTED]:/tmp/Debug$ export MONO_CFG_DIR=~/mono-1.1.12/etc/
> [EMAIL PROTECTED]:/tmp/Debug$ ~/mono-1.1.12/bin/mono
> ~/mono-1.1.12/lib/mono/1.0/mdb.exe ConsoleApplication70.exe
> Mono Debugger
> (mdb) run
> Starting program: ConsoleApplication70.exe
> Process @4 stopped at #0: 0xb789f73b in
> ConsoleApplication70.Program.Main(System.String[])+0xb at
> /home/hans/.xdevelop/projects/ConsoleApplication70/ConsoleApplication70/Program.cs:11.
>11Console.WriteLine("Hello world!");
> (mdb)
>
>
> I hope this analysis helps to improve the mdb and mdb packaging.
>
>
> Best regards,
>
>
> Hans
signature.asc
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Getting Ready for 1.1.13 Release
Hey all, We're getting ready for the 1.1.13 release. Tarballs will be created Thursday evening MST. This will probably be our last drop into the upcoming SuSE products. Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Re: [Mono-patches] r55877 - trunk/mono-tools
Currently the monodoc browser is available on many older distros as well as win32. But with this change it won't work on older distros nor win32. Also, distros that use the linux installer without being able to run gtk#2 also won't be able to use the browser. I thought that mono-tools was using gtk-sharp1 on purpose. Now, other the other hand, I have no idea how these bugs would get fixed by using gtk-sharp1. Wade On Sat, 2006-01-21 at 09:36 -0500, Rafael ([EMAIL PROTECTED]) wrote: > Author: rferreira > Date: 2006-01-21 09:36:10 -0500 (Sat, 21 Jan 2006) > New Revision: 55877 > > Modified: >trunk/mono-tools/ChangeLog >trunk/mono-tools/configure.in > Log: > changed it to build against the 2.0 series gtk# and gecko# > > Modified: trunk/mono-tools/ChangeLog > === > --- trunk/mono-tools/ChangeLog2006-01-21 14:35:14 UTC (rev 55876) > +++ trunk/mono-tools/ChangeLog2006-01-21 14:36:10 UTC (rev 55877) > @@ -1,3 +1,7 @@ > +2006-01-16 Rafael Ferreira <[EMAIL PROTECTED]> > + * configure.in: updated to use gtk-sharp-2.0/gecko-sharp-2.0 > + this fixes bugs# 76054 & 76544 related to Pango bugs. > + > 2005-11-27 C.J. Collier <[EMAIL PROTECTED]> > * docbrowser/monodoc.desktop.in: Added patch from [EMAIL PROTECTED] > > > Modified: trunk/mono-tools/configure.in > === > --- trunk/mono-tools/configure.in 2006-01-21 14:35:14 UTC (rev 55876) > +++ trunk/mono-tools/configure.in 2006-01-21 14:36:10 UTC (rev 55877) > @@ -37,17 +37,17 @@ > AC_SUBST(MONODOC_LIBS) > > > -#PKG_CHECK_MODULES(GTK_SHARP, gtk-sharp-2.0 glade-sharp-2.0 gconf-sharp-2.0) > -PKG_CHECK_MODULES(GTK_SHARP, gtk-sharp glade-sharp gconf-sharp) > +PKG_CHECK_MODULES(GTK_SHARP, gtk-sharp-2.0 glade-sharp-2.0 gconf-sharp-2.0) > +#PKG_CHECK_MODULES(GTK_SHARP, gtk-sharp glade-sharp gconf-sharp) > AC_SUBST(GTK_SHARP_LIBS) > > > -PKG_CHECK_MODULES(GTKHTML_SHARP, gtkhtml-sharp, enable_gtkhtml=yes, > enable_gtkhtml=no) > +PKG_CHECK_MODULES(GTKHTML_SHARP, gtkhtml-sharp-2.0, enable_gtkhtml=yes, > enable_gtkhtml=no) > AC_SUBST(GTKHTML_SHARP_LIBS) > AM_CONDITIONAL(ENABLE_GTKHTML, test "x$enable_gtkhtml" = "xyes") > > > -PKG_CHECK_MODULES(GECKO_SHARP, gecko-sharp = 0.6, enable_gecko=yes, > enable_gecko=no) > +PKG_CHECK_MODULES(GECKO_SHARP, gecko-sharp-2.0, enable_gecko=yes, > enable_gecko=no) > AC_SUBST(GECKO_SHARP_LIBS) > AM_CONDITIONAL(ENABLE_GECKO, test "x$enable_gecko" = "xyes") > > > ___ > Mono-patches maillist - Mono-patches@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-patches > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Re: [Mono-patches] r55877 - trunk/mono-tools
On Thu, 2006-02-09 at 09:18 -0600, Mike Kestner wrote: > On Wed, 2006-02-08 at 21:49 -0700, Wade Berrier wrote: > > Currently the monodoc browser is available on many older distros as well > > as win32. But with this change it won't work on older distros nor > > win32. > > It looks like sles9, rh9, and rhel3 are the only distros mono is > packaging that don't have Gtk#2 packages at this point. It seems > reasonable to freeze at the previous version of monodoc-browser for > those platforms. Those platforms just don't get new features and live > with the existing bugs. We can continue to update the documentation > content independently since that lives in monodoc, not mono-tools. The website updates are scripted. I'll need to update these anyway, so I'll add a feature of "latest version" for these older distros. > > As far as win32, is it the gconf-sharp dependency that's blocking us? > How did you get around that for 1.0 on win32? > I believe it boils down to that I can't compile gnome-sharp2 because it depends on libpanelapplet, which isn't available on win32. Without gnome-sharp2, I can't compile gtkhtml-sharp2, which I'm able to do with 1.0.10, because 1.0.10's gnome-sharp doesn't require libpanelapplet. Now, if I could use gecko-sharp on win32 (which I haven't figured out how to do this yet), then yes, the only missing piece would be gconf-sharp2. Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Is anyone using mono develop in 1.1.13.2?
Could you run monodevelop with increased logging? Do this with the following from a terminal window: export MONO_LOG_LEVEL=debug monodevelop That could help shed some light on this. If you have gtk+2.4 installed (which it appears you do), I'm not sure what the problem could be, other than some missing libraries required by libgnomesharpglue. My guess is that you're missing some gnome libraries. Doing the above suggestion will say which libraries are not there. From the wiki link that Lluis referenced: The solution: run a distro that has gtk+ 2.4 or above, make sure Gnome is installed, and make sure you load the settings from .bashrc which were created by the installer. (They are also listed in the above faq question) Wade On Mon, 2006-02-20 at 17:04 -0900, Joshua Kugler wrote: > On Monday 20 February 2006 14:46, Lluis Sanchez wrote: > > Hi, > > > > Please carefully read the mini FAQ in the installer instructions. The > > error you are getting is documented there: > > > > http://www.mono-project.com/InstallerInstructions > > > > Lluis. > > Hmm...well, since other mono apps ran, I guess I overlooked that part. But > it > seems I have gtk+ 2.4 installed. > > [EMAIL PROTECTED] /home/joshua]# ll /usr/lib/gtk-2.0 > total 20 > drwxr-xr-x 3 root root 4096 Sep 23 2004 2.2.0/ > drwxr-xr-x 6 root root 4096 Nov 16 15:31 2.4.0/ > drwxr-xr-x 2 root root 4096 Jan 11 04:04 bin/ > drwxr-xr-x 2 root root 4096 Jul 29 2005 engines/ > drwxr-xr-x 2 root root 4096 Nov 16 15:31 modules/ > > I have the installer from the web site installed. I have gtk-sharp2-1.9.2. > I'm a little unclear as to the version numbers. In the gtk-2.0 directory > above, I have a 2.4.0 directory. Does that man I have gtk 2.0 or 2.4.0? In > the latest version of Mandrake, the package is libgtk+2.0_0-2.8.3. What > version is that? 2.0 or 2.8.3? On my current Mandrake box, I have > gtk+2.0-2.6.4 installed. That means I should be able to run gtk+ 2.4 apps, > right? > > OK, as to the second part. I'm not using the native gtk-sharp2 libraries, > I'm > using the ones that come with the installer. How do I check to make sure > those don't have unresolved symbols? > > Sorry to be so much trouble about this. But I'm stuck! :) > > j- k- > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Is anyone using mono develop in 1.1.13.2?
Thanks for the debug output. It may be easier to install all of Gnome. But, if you're taking the minimalistic approach, try installing the libpanel applet package. Repeat this same process of running monodevelop with the debug logs turned on and install additional packages until you don't get any exceptions with libgnomesharpglue. Wade On Wed, 2006-03-01 at 14:37 -0900, Joshua Kugler wrote: > OK, the run is attached. > > Near the end, I see things like: > (./MonoDevelop.exe:30692): Mono-WARNING **: DllImport unable to load library > 'libpanel-applet-2.so.0: cannot open shared object > > But I am seeing a lot of "cannot open shared object or file" with dll's that > don't seem to have anything to do with Gnome. Should I just install gnome > (the whole thing) and see if my problem goes away, or is there a subset that > I would be better off installing if Gnome isn't my primary environment? > > j- k- > > On Wednesday 01 March 2006 14:00, Wade Berrier wrote: > > Could you run monodevelop with increased logging? Do this with the > > following from a terminal window: > > > > export MONO_LOG_LEVEL=debug > > monodevelop > > > > > > That could help shed some light on this. If you have gtk+2.4 installed > > (which it appears you do), I'm not sure what the problem could be, other > > than some missing libraries required by libgnomesharpglue. My guess is > > that you're missing some gnome libraries. Doing the above suggestion > > will say which libraries are not there. > > > > From the wiki link that Lluis referenced: > > > > The solution: run a distro that has gtk+ 2.4 or above, make sure Gnome > > is installed, and make sure you load the settings from .bashrc which > > were created by the installer. (They are also listed in the above faq > > question) > > > > Wade > > > > On Mon, 2006-02-20 at 17:04 -0900, Joshua Kugler wrote: > > > On Monday 20 February 2006 14:46, Lluis Sanchez wrote: > > > > Hi, > > > > > > > > Please carefully read the mini FAQ in the installer instructions. The > > > > error you are getting is documented there: > > > > > > > > http://www.mono-project.com/InstallerInstructions > > > > > > > > Lluis. > > > > > > Hmm...well, since other mono apps ran, I guess I overlooked that part > > > But it seems I have gtk+ 2.4 installed. > > > > > > [EMAIL PROTECTED] /home/joshua]# ll /usr/lib/gtk-2.0 > > > total 20 > > > drwxr-xr-x 3 root root 4096 Sep 23 2004 2.2.0/ > > > drwxr-xr-x 6 root root 4096 Nov 16 15:31 2.4.0/ > > > drwxr-xr-x 2 root root 4096 Jan 11 04:04 bin/ > > > drwxr-xr-x 2 root root 4096 Jul 29 2005 engines/ > > > drwxr-xr-x 2 root root 4096 Nov 16 15:31 modules/ > > > > > > I have the installer from the web site installed. I have > > > gtk-sharp2-1.9.2. I'm a little unclear as to the version numbers. In the > > > gtk-2.0 directory above, I have a 2.4.0 directory. Does that man I have > > > gtk 2.0 or 2.4.0? In the latest version of Mandrake, the package is > > > libgtk+2.0_0-2.8.3. What version is that? 2.0 or 2.8.3? On my current > > > Mandrake box, I have gtk+2.0-2.6.4 installed. That means I should be able > > > to run gtk+ 2.4 apps, right? > > > > > > OK, as to the second part. I'm not using the native gtk-sharp2 > > > libraries, I'm using the ones that come with the installer. How do I > > > check to make sure those don't have unresolved symbols? > > > > > > Sorry to be so much trouble about this. But I'm stuck! :) > > > > > > j- k- > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Call for testing: Mono 1.2.4 Preview Available
Hi, "Preview 2" has been uploaded to this same location. mono/mcs was retagged as mono-1-2-4 from the mono-1-2-4 branch. Thanks to all who have taken a look at the preview releases. Wade On Fri, 2007-04-20 at 22:26 -0600, Wade Berrier wrote: > Hi, > > Mono 1.2.4 preview sources, packages, and installers are available at: > > http://mono.ximian.com/monobuild/preview/download-preview/ > > The beginnings of the release notes for 1.2.4 are available at: > > http://go-mono.com/archive/1.2.4/ > > If no critical bugs are found after the preview period, these same > downloads will be posted on mono-project.com for general consumption. > > If there are critical bugs found, only those packages/sources will be > updated before publishing to mono-project.com. > > Since this release hasn't been pushed to our main download server, some > sources may be retagged if critical bugs are found. Those tags are not > final until we publish to mono-project.com. > > Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Call for testing: Mono 1.2.4 Preview 3 Available
Hi, The preview release has been updated (Preview 3) This includes some fixes, amongst others, to get vb.net working on asp.net. Again, thanks to all who've been trying the previews out. Wade On Wed, 2007-04-25 at 19:57 -0600, Wade Berrier wrote: > Hi, > > "Preview 2" has been uploaded to this same location. mono/mcs was > retagged as mono-1-2-4 from the mono-1-2-4 branch. > > Thanks to all who have taken a look at the preview releases. > > Wade > > On Fri, 2007-04-20 at 22:26 -0600, Wade Berrier wrote: > > Hi, > > > > Mono 1.2.4 preview sources, packages, and installers are available at: > > > > http://mono.ximian.com/monobuild/preview/download-preview/ > > > > The beginnings of the release notes for 1.2.4 are available at: > > > > http://go-mono.com/archive/1.2.4/ > > > > If no critical bugs are found after the preview period, these same > > downloads will be posted on mono-project.com for general consumption. > > > > If there are critical bugs found, only those packages/sources will be > > updated before publishing to mono-project.com. > > > > Since this release hasn't been pushed to our main download server, some > > sources may be retagged if critical bugs are found. Those tags are not > > final until we publish to mono-project.com. > > > > Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Regression Tests Webpage
Hi, On Mon, 2007-06-11 at 13:34 -0700, Matt Jones wrote: > Hi - > > I'm working on improving .net support under wine this summer as an > intern at Google, and I stumbled upon the test suite webpage[1] on the > website. I've tried downloading the scripts used to compile all the > data, but the published versions don't seem to function for me (I get > numerous perl errors / warnings). Are these scripts fully up to date, > and, if so, is there any automation (cron jobs, sh scripts) that would > be good to look at? Those pages [1] haven't been updated for a long time. There is a copy in trunk/release/scripts, but I'm not sure if those scripts were the ones that generated the webpages. Sorry I can't be of more help. I think the person who wrote the scripts is no longer an employee of Novell. > > My goal with the scripts is to publish (most likely on the wine > website) a comparison of mono running the tests on windows and mono > running the tests under wine on linux as a way to see areas wine might > be lacking. There has been some talk about running the testsuite against MS .Net. Not sure what the current status on this is. But, since many of the tests use Nunit, which I believe can output to several formats, you should be able to do some nice comparisons if you were able to get results from running under MS .Net. Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] DeflateStream : bit length overflow
At the suggestion of Paolo, I ran: "strings /usr/lib/libMonoPosixHelper.so |grep overflow" against the file that shipped in the 1.2.3.1 rpm, with no results. Jonathan, could you try running this? Also, could there possibly be another libMonoPosixHelper.so that is getting called? Wade On Wed, 2007-07-04 at 10:44 -0400, Jonathan Gagnon wrote: > I'm using mono 1.2.3.1. I installed the followin rpms : > > mono-data-1.2.3.1-0.novell > mono-core-1.2.3.1-0.novell > > The output of 'ldd /usr/lib/libMonoPosixHelper.so' is : > > linux-gate.so.1 => (0xe000) > libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x55587000) > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x5558b000) > libdl.so.2 => /lib/libdl.so.2 (0x55606000) > libpthread.so.0 => /lib/tls/i686/libpthread.so.0 (0x5560a000) > libm.so.6 => /lib/tls/i686/libm.so.6 (0x5561b000) > libc.so.6 => /lib/tls/i686/libc.so.6 (0x5563e000) > /lib/ld-linux.so.2 (0x56555000) > > Thanks, > > Jonathan > > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] De la part de Paolo Molaro > Envoyé : Wednesday, July 04, 2007 9:56 AM > À : mono-devel-list@lists.ximian.com > Objet : Re: [Mono-dev] DeflateStream : bit length overflow > > On 07/03/07 Jonathan Gagnon wrote: > > The following messages are sent to the console when using the > > DeflateStream class in Mono : > > > > bit length overflow > > code 4 bits 6->7 > > > > The compression is working correctly, so it seems like some kind of > > debug trace. > > > > I did a grep on the sources to see where it comes from, and I found > > this line inside the mono/support/trees.c file : > > > > Trace((stderr,"\nbit length overflow\n")); > > > > Is this something that shouldn't have been checked in? > > What version of mono are you using? What is the output of: > ldd /path/to/libMonoPosixHelper.so > > That message is some debug output that should happen only if you compile > with the DEBUG #define enabled, which we don't. > > lupus > > -- > - > [EMAIL PROTECTED] debian/rules > [EMAIL PROTECTED] Monkeys do it better > ___ > 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 > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] DeflateStream : bit length overflow
I looked at the build logs, and DEBUG is not defined anywhere. (I also checked config.h) Here's the exact make output for trees.c: if /bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I.. -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP -D_FILE_OFFSET_BITS=64 -O2 -march=i586 -mcpu=i686 -fno-strict-aliasing -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -MT trees.lo -MD -MP -MF ".deps/trees.Tpo" -c -o trees.lo trees.c; \ then mv -f ".deps/trees.Tpo" ".deps/trees.Plo"; else rm -f ".deps/trees.Tpo"; exit 1; fi /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I.. -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP -D_FILE_OFFSET_BITS=64 -O2 -march=i586 -mcpu=i686 -fno-strict-aliasing -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -MT trees.lo -MD -MP -MF .deps/trees.Tpo -c trees.c -fPIC -DPIC -o .libs/trees.o /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I.. -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP -D_FILE_OFFSET_BITS=64 -O2 -march=i586 -mcpu=i686 -fno-strict-aliasing -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -MT trees.lo -MD -MP -MF .deps/trees.Tpo -c trees.c -o trees.o >/dev/null 2>&1 Not sure what's going on. Do you have a code snippet I could try out? Wade On Wed, 2007-07-04 at 10:44 -0400, Jonathan Gagnon wrote: > I'm using mono 1.2.3.1. I installed the followin rpms : > > mono-data-1.2.3.1-0.novell > mono-core-1.2.3.1-0.novell > > The output of 'ldd /usr/lib/libMonoPosixHelper.so' is : > > linux-gate.so.1 => (0xe000) > libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x55587000) > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x5558b000) > libdl.so.2 => /lib/libdl.so.2 (0x55606000) > libpthread.so.0 => /lib/tls/i686/libpthread.so.0 (0x5560a000) > libm.so.6 => /lib/tls/i686/libm.so.6 (0x5561b000) > libc.so.6 => /lib/tls/i686/libc.so.6 (0x5563e000) > /lib/ld-linux.so.2 (0x56555000) > > Thanks, > > Jonathan > > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] De la part de Paolo Molaro > Envoyé : Wednesday, July 04, 2007 9:56 AM > À : mono-devel-list@lists.ximian.com > Objet : Re: [Mono-dev] DeflateStream : bit length overflow > > On 07/03/07 Jonathan Gagnon wrote: > > The following messages are sent to the console when using the > > DeflateStream class in Mono : > > > > bit length overflow > > code 4 bits 6->7 > > > > The compression is working correctly, so it seems like some kind of > > debug trace. > > > > I did a grep on the sources to see where it comes from, and I found > > this line inside the mono/support/trees.c file : > > > > Trace((stderr,"\nbit length overflow\n")); > > > > Is this something that shouldn't have been checked in? > > What version of mono are you using? What is the output of: > ldd /path/to/libMonoPosixHelper.so > > That message is some debug output that should happen only if you compile > with the DEBUG #define enabled, which we don't. > > lupus > > -- > - > [EMAIL PROTECTED] debian/rules > [EMAIL PROTECTED] Monkeys do it better > ___ > 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 > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] DeflateStream : bit length overflow
run the program with first setting: MONO_LOG_LEVEL=debug That should give sufficient output as to what file is being used. Wade On Mon, 2007-07-09 at 13:34 -0400, Jonathan Gagnon wrote: > I have no results too when running the given command. I found another > libMonoPosixHelper.so on the machine although they give no results too when > using the strings command. > > I tried running the following command instead "grep overflow > /usr/lib/libMonoPosixHelper.so" and it returned no result too. But when I > tried to grep the other libMonoPosixHelper.so file, it gave me the following > message : > > Binary file /path/libMonoPosixHelper.so matches > > So it seems that this is the file that is being used. Is there a way to > know for sure which .so file is actually used when running mono? > > Thanks, > > Jonathan > > -Message d'origine- > De : Wade Berrier [mailto:[EMAIL PROTECTED] > Envoyé : Monday, July 09, 2007 11:50 AM > À : mono-devel-list@lists.ximian.com > Cc : Jonathan Gagnon > Objet : Re: [Mono-dev] DeflateStream : bit length overflow > > At the suggestion of Paolo, I ran: > > "strings /usr/lib/libMonoPosixHelper.so |grep overflow" > > against the file that shipped in the 1.2.3.1 rpm, with no results. > > Jonathan, could you try running this? > > Also, could there possibly be another libMonoPosixHelper.so that is getting > called? > > Wade > > On Wed, 2007-07-04 at 10:44 -0400, Jonathan Gagnon wrote: > > I'm using mono 1.2.3.1. I installed the followin rpms : > > > > mono-data-1.2.3.1-0.novell > > mono-core-1.2.3.1-0.novell > > > > The output of 'ldd /usr/lib/libMonoPosixHelper.so' is : > > > > linux-gate.so.1 => (0xe000) > > libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x55587000) > > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x5558b000) > > libdl.so.2 => /lib/libdl.so.2 (0x55606000) > > libpthread.so.0 => /lib/tls/i686/libpthread.so.0 (0x5560a000) > > libm.so.6 => /lib/tls/i686/libm.so.6 (0x5561b000) > > libc.so.6 => /lib/tls/i686/libc.so.6 (0x5563e000) > > /lib/ld-linux.so.2 (0x56555000) > > > > Thanks, > > > > Jonathan > > > > -Message d'origine- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] De la part de Paolo > > Molaro Envoyé : Wednesday, July 04, 2007 9:56 AM À : > > mono-devel-list@lists.ximian.com Objet : Re: [Mono-dev] DeflateStream > > : bit length overflow > > > > On 07/03/07 Jonathan Gagnon wrote: > > > The following messages are sent to the console when using the > > > DeflateStream class in Mono : > > > > > > bit length overflow > > > code 4 bits 6->7 > > > > > > The compression is working correctly, so it seems like some kind of > > > debug trace. > > > > > > I did a grep on the sources to see where it comes from, and I found > > > this line inside the mono/support/trees.c file : > > > > > > Trace((stderr,"\nbit length overflow\n")); > > > > > > Is this something that shouldn't have been checked in? > > > > What version of mono are you using? What is the output of: > > ldd /path/to/libMonoPosixHelper.so > > > > That message is some debug output that should happen only if you > > compile with the DEBUG #define enabled, which we don't. > > > > lupus > > > > -- > > - > > [EMAIL PROTECTED] debian/rules > > [EMAIL PROTECTED] Monkeys do it better > > ___ > > 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 > > > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono 1.2.5 Preview
Hi, Mono 1.2.5 preview sources, packages, and installers are available at: http://mono.ximian.com/monobuild/preview/download-preview/ At some point, the release notes for 1.2.5 will be available at: http://go-mono.com/archive/1.2.5/ If no critical bugs are found after the preview period, these same downloads will be posted on mono-project.com for general consumption. If there are critical bugs found, only those packages/sources will be updated before publishing to mono-project.com. Since this release hasn't been pushed to our main download server, some sources may be retagged if critical bugs are found. Those tags are not final until we publish to mono-project.com. Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.2.5 Preview
The release will include md 0.15, but not the windows installer. Wade On Tue, 2007-07-31 at 14:15 +0530, Sharique uddin Ahmed Farooqui wrote: > Will it include Monodevelop 0.15? > > On 7/28/07, Daniel Morgan <[EMAIL PROTECTED]> wrote: > Wow! > > The windows installer includes gtk# 2.10. > > I've been waiting for this. > > Thanks. > > --- Wade Berrier <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Mono 1.2.5 preview sources, packages, and installers > > are available at: > > > > > http://mono.ximian.com/monobuild/preview/download-preview/ > > > > At some point, the release notes for 1.2.5 will be > > available at: > > > > http://go-mono.com/archive/1.2.5/ > > > > If no critical bugs are found after the preview > > period, these same > > downloads will be posted on mono-project.com for > > general consumption. > > > > If there are critical bugs found, only those > > packages/sources will be > > updated before publishing to mono-project.com. > > > > Since this release hasn't been pushed to our main > > download server, some > > sources may be retagged if critical bugs are found. > > Those tags are not > > final until we publish to mono-project.com. > > > > Wade > > > > > > ___ > > Mono-devel-list mailing list > > Mono-devel-list@lists.ximian.com > > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > > > > > Sick sense of humor? Visit Yahoo! TV's > Comedy with an Edge to see what's on, when. > http://tv.yahoo.com/collections/222 > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > -- > Sharique uddin Ahmed Farooqui > (C++/C# Developer, IT Consultant) > A revolution is about to begin. > A world is about to change. > And you and me are "the initiator". ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.2.5 Preview
Definitely. On Tue, 2007-07-31 at 16:56 +0900, Sanghyeon Seo wrote: > 2007/7/28, Wade Berrier <[EMAIL PROTECTED]>: > > Mono 1.2.5 preview sources, packages, and installers are available at: > > This seems to cause IronPython 1.1 to segfault, which is a regression. > Filed as a bug here: > http://bugzilla.ximian.com/show_bug.cgi?id=82246 > > Does this count as a critical bug? > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.2.5
On Wed, 2007-08-01 at 14:33 +0300, Szentpali Janos wrote: > Lluis Sanchez wrote: > > El dc 01 de 08 del 2007 a les 13:49 +0300, en/na Szentpali Janos va > > escriure: > > > >> Is there a point in complaining (reporting) that monodevelop (included > >> in Mono 1.2.5 preview) doesn't work on other platforms than the > >> officially supported ones (I'm talking Zenwalk)? You should report issues with the linux installer to me. Wade > >> > > > > If it is a packaging problem (e.g. you install the package and it > > doesn't work at all due to missing dependencies) you should report the > > problem to whoever created the package. > > > > If you find bugs in when running MonoDevelop, you should report them in > > http://bugzilla.ximian.com. > > > > Lluis. > > > > > > > I'm talking about the official Linux installer from > http://mono.ximian.com/monobuild/preview/download-preview/ > (http://mono.ximian.com/monobuild/preview/archive/1.2.5/linux-installer/0/mono-1.2.5_0-installer.bin). > > To whom do I report about errors in the official linux installer? > Thank you. > > János > > ___ > 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
[Mono-dev] Mono 1.2.5 Preview 2
Hi, Mono 1.2.5 preview 2 sources, packages, and installers are available at: http://mono.ximian.com/monobuild/preview/download-preview/ At some point, the release notes for 1.2.5 will be available at: http://go-mono.com/archive/1.2.5/ If no critical bugs are found after the preview period, these same downloads will be posted on mono-project.com for general consumption. If there are critical bugs found, only those packages/sources will be updated before publishing to mono-project.com. Since this release hasn't been pushed to our main download server, some sources may be retagged if critical bugs are found. Those tags are not final until we publish to mono-project.com. Changes with preview 2 over preview 1: MonoDevelop 0.15 IPCE r6 cocoa-sharp 0.9.4 redcarpet/opencarpet support dropped (all the distros we support can install packages via yast or yum) Several critial bugs fixed that were found in preview1 (Thanks for testing!!) ikvm 0.34.0.2 Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.2.5 Preview 2
Hi Onur, The different platforms and linux distributions will always have differing gtk# versions, but we'll always distribute all of the versions (2.4, 2.8, 2.10) of gtk# in source form. Does that answer your question? Wade On Thu, 2007-08-02 at 09:30 +0300, Onur Gumus wrote: > Hi , for the earlier releases there were differences between the > binary installer and source code compilation . (Like the gtk-sharp > version was 2.04 in binary installer and 2.10 in source code, > futhermore miguel explained me this was intentional). The question > is , Is there now any difference between those installation methods > (source and binary installer) in terms of the assembly versions in > gac ? > > On 8/2/07, Wade Berrier <[EMAIL PROTECTED]> wrote: > Hi, > > Mono 1.2.5 preview 2 sources, packages, and installers are > available at: > > http://mono.ximian.com/monobuild/preview/download-preview/ > > At some point, the release notes for 1.2.5 will be available > at: > > http://go-mono.com/archive/1.2.5/ > > If no critical bugs are found after the preview period, these > same > downloads will be posted on mono-project.com for general > consumption. > > If there are critical bugs found, only those packages/sources > will be > updated before publishing to mono-project.com. > > Since this release hasn't been pushed to our main download > server, some > sources may be retagged if critical bugs are found. Those > tags are not > final until we publish to mono-project.com. > > Changes with preview 2 over preview 1: > > MonoDevelop 0.15 > IPCE r6 > cocoa-sharp 0.9.4 > redcarpet/opencarpet support dropped (all the distros we > support can install packages via yast or yum) > Several critial bugs fixed that were found in preview1 (Thanks > for testing!!) > ikvm 0.34.0.2 > > Wade > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > -- > Warning: If you are reading this then this warning is for you. Every > word you read of this useless fine print is another second off your > life. Don't you have other things to do? Is your life so empty that > you honestly can't think of a better way to spend these moments? Or > are you so impressed with authority that you give respect and credence > to all that claim it? Do you read everything you're supposed to read? > Do you think every thing you're supposed to think? Buy what you're > told to want? Get out of your apartment. Meet a member of the opposite > sex. Stop the excessive shopping and masturbation.Quit your job. Start > a fight. Prove you're alive. If you don't claim your humanity you will > become a statistic. You have been warned - Onur ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono 1.2.5 Released and Published
Hi, Mono 1.2.5 has been released. Release notes are here: http://go-mono.com/archive/1.2.5/ Downloads are available from: http://mono-project.com/Downloads There are also rpms in the openSUSE Build Service (which has RPMS for newer Fedora distros and suse factory): http://download.opensuse.org/repositories/Mono/ The vmware image has been updated with improvements of which several were suggestions based on feedback we received. -Browse Windows network from inside the VMware image (start nmb) -smart installed as an optional/additional package manager -System.Windows.Forms demos don't open a terminal any longer (use .desktop files to call the wrapper scripts) -SWF Demos updated -Obsolete nGallery ASP.Net demo removed -openSUSE 10.2 shipped with a version of Beagle that has some serious bugs, so it was removed -ext3 partition was set to never do consistency checks -probably some more things that I forgot... Thanks to all who tried out the preview releases and filed bugs against it. Enjoy! Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Daily test tarballs no more ?
This was set back up... should have dailies tomorrow. Wade On Wed, 2007-09-12 at 19:42 +0200, Joachim Ante wrote: > Hi, > > It seems the daily test tarballs are not being generated anymore. > The last test tar ball was 21-08, last month. > http://mono.ximian.com/daily/ > > I'd really appreciate if someone can fix this. > > Best regards, > Joachim Ante > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] C bindings VS C++ bindings (Gtk# vs. Kimono?)
On Tue, 2007-10-02 at 16:56 -0400, Miguel de Icaza wrote: > Hello, > > > We had discussed this about a year ago and decided that we had different > > interests, since we were focused on using MS .NET on Windows, and the > > Mono team wanted to (rightfully so) focus on Mono on Windows. > > Are the binaries for .NET and Mono any different, other than the GAC > install directory? I build gtk# on windows with vs .net for the sole purpose of eventually shipping gtk# for ms .net. I think it's ok to have separate installers, but we may want to reconsider the overall picture if we move everything to .msi. (Ie: maybe have an .msi installer for gtk+, or use someone elses, one for core mono, another for gtk#, etc...) Wade > > Do you think it would be possible to have a single installer that could > install the same assemblies into both GACs? > > > > That being said, I'd love to see our efforts combined into one Gtk# > > installer to rule them all. Maybe it would be appropriate to take this > > offline and discuss it when Cody and I are in Cambridge this Friday? > > > > Cheers, > > > > -Brad > > > > ___ > > Mono-devel-list mailing list > > Mono-devel-list@lists.ximian.com > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Class Status pages for Olive
Hi, Status pages are generated for olive on monobuild. Here's the link (which is temporary for now because old builds get removed from mono.ximian.com): http://mono.ximian.com/monobuild/builds/HEAD/suse-100-i586/olive/86908/files/steps/api-diff/ Miguel mentioned that there are some missing assemblies (agclr, System.Silverlight, etc). Is the masterinfo information for those assemblies contained in this link? http://mono.ximian.com/masterinfos/masterinfos-3.0.tar.gz I'm assuming it's not, because it seems that each assembly has it's own corresponding xml file. Does the above masterinfo file need updating, or is there another set of masterinfos I should be using with olive? Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] monobuild documentation on the wiki
Hi, I've updated some monobuild documentation on the wiki: http://www.mono-project.com/BuildSystem/MonoBuild Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] win-4-i386 build hung
I restarted it today... Thanks! Wade On Tue, 2007-10-16 at 09:13 +0100, Andy Hume wrote: > It's still hung! > >install-deps inprogress [ Running for 1682 min(s) ] > > Can it be killed? > > Andy > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf > > Of Andy Hume > > Sent: 15 October 2007 13:49 > > To: mono-devel-list@lists.ximian.com > > Subject: [Mono-dev] win-4-i386 build hung > > > > Looks like the win-4-i386 build is broken. It's been at > > install-deps for 517 mins. There log appears empty. > > (http://mono.ximian.com/monobuild/python/monobuild.py/packages > > tatus?platform=win-4-i386&package=mono&HEAD_or_RELEASE=HEAD) > > > > Should it/can it be killed? > > > > Andy > > > > ___ > > 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 > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Class Status Pages
Hi, I generate class status pages in monobuild now instead of during the nightly daily build. Check out: http://www.mono-project.com/Template:StatusPages I'm pretty sure the description for olive needs to be updated... A cron job will run once a day and collect the latest status pages from monobuild. I'll update the output for each module to include a date and revision. Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Class Status Pages
I think the issue is that the masterinfos that I use on the olive module only has the 3.0 stuff. I think after they are updated, or after we have 2.1 masterinfos, they will have the silverlight assemblies. I'll look into it. Wade On Tue, 2007-10-16 at 22:57 -0400, Miguel de Icaza wrote: > Hello Wade, > > > Check out: > > > > http://www.mono-project.com/Template:StatusPages > > > > I'm pretty sure the description for olive needs to be updated... > > Was Olive supposed to be listed there? It seems to be missing the 2.1 > assemblies for Silverlight. > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] win-4-i386 build hung
Builds are back up... The start times are in UTC on the webserver, but I try some javascript to make them local to the browser timezone. Wade On Wed, 2007-10-17 at 11:47 +0100, Andy Hume wrote: > Err. Seems still running... > http://mono.ximian.com/monobuild/python/monobuild.py/packagestatus?platf > orm=win-4-i386&package=mono&HEAD_or_RELEASE=HEAD > > BTW is the start time reported in UTC or +4? > > Andy > > > > -Original Message- > > From: Wade Berrier [mailto:[EMAIL PROTECTED] > > Sent: 16 October 2007 22:58 > > To: Andy Hume > > Cc: mono-devel-list@lists.ximian.com > > Subject: Re: [Mono-dev] win-4-i386 build hung > > > > I restarted it today... > > > > Thanks! > > > > Wade > > > > On Tue, 2007-10-16 at 09:13 +0100, Andy Hume wrote: > > > It's still hung! > > > > > >install-deps inprogress [ Running for 1682 min(s) ] > > > > > > Can it be killed? > > > > > > Andy > > > > > > > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Andy > > > > Hume > > > > Sent: 15 October 2007 13:49 > > > > To: mono-devel-list@lists.ximian.com > > > > Subject: [Mono-dev] win-4-i386 build hung > > > > > > > > Looks like the win-4-i386 build is broken. It's been at > > > > install-deps for 517 mins. There log appears empty. > > > > (http://mono.ximian.com/monobuild/python/monobuild.py/packages > > > > tatus?platform=win-4-i386&package=mono&HEAD_or_RELEASE=HEAD) > > > > > > > > Should it/can it be killed? > > > > > > > > Andy > > > > > > > > ___ > > > > 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 > > > > > > signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono 1.2.6
Hi, Mono 1.2.6 has been released! Downloads are available: http://mono-project.com/Downloads Rpms in the suse build service will soon be updated. ( http://download.opensuse.org/repositories/Mono/ ) Major highlights: * Mono 1.2.6 can now be used as an SDK for creating Silverlight 1.1 applications on all platforms. This allows developers to create applications that target Silverlight without requiring a Windows installation. * Native Windows.Forms driver for MacOS X allows Winforms-based applications to run without an X server. * Support for the ASP.NET AJAX APIs and controls. * Support for FastCGI deployments: ASP.NET can now be deployed on a multitude of servers that implement the FastCGI protocol (lighttpd for example) in addition to Apache. * Windows.Forms now supports the WebControl on Windows and Linux using Mozilla. * Runtime will now consume much less memory for 2.0-based applications due to various optimizations in generics support as well as including many new performance improvements and an updated verifier and an implementation of CoreCLR security. * C# compiler is quickly approaching full 3.0 support, most of the basics work right now (except support for System.Query.Expression AST generation). Full release notes can be found here: http://go-mono.com/archive/1.2.6/ Thanks to all of our users and contributors. Enjoy! Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.9.0 Preview 2 is out!!
We decided to leave Mono out of the path and instead have a command prompt that sets up the environment. Maybe it's a personal preference, but it also lets you have multiple versions of Mono installed. Maybe we should reconsider? Wade On Thu, 2008-02-14 at 14:52 +1100, Alistair Leslie-Hughes wrote: > Hi, > > In the Windows Installer, could an option be added so that the C:\...\Mono > 1.9\bin directory be added to the system path > and an other Environment variables that may be relevent? > > Best Regards > Alistair Leslie-Hughes > > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.9.0 Preview 2 is out!!
Hi, The 1.9 preview 3 win32 installer will be built with innosetup 5.2.2. Thanks, Wade On Sat, 2008-02-09 at 10:41 +0100, Kornél Pál wrote: > Hi, > > You are building the Windows installer using Inno Setup 5.1.5 that was > released almost three years ago. Currently the latest release is 5.2.2 and I > don't see any major changes in 5.2 series. Also note 5.1.5 has several > Windows Vista related bugs that were addressed in subsequent releases. > > If there is no reason to stay with the old version I would like to ask you > to use Inno Setup 5.2.2 for building the installer. If you need any help > please let me know. > > Kornél > > - Original Message - > From: "Thomas Wiest" <[EMAIL PROTECTED]> > To: "mono-devel" > Sent: Friday, February 08, 2008 10:46 PM > Subject: [Mono-dev] Mono 1.9.0 Preview 2 is out!! > > > > Hey Everyone, > >We've just released Mono 1.9.0 Preview 2 today! This preview has > > Windows and Mac OS X installers. Please help us out by giving it a try > > with your applications. > > > > As always, you can get the preview releases here: > > http://mono.ximian.com/monobuild/preview/download-preview/ > > > > Please report any bugs that you may find using our Bugs page, AND reply to > > this thread with the bug numbers so we can track them! > > http://www.mono-project.com/Bugs > > > > > > The earlier you file the bugs and reply to this message, the more likely > > your bugs will get fixed. > > > > Special attention is given to regressions, so if you can tell us a version > > of Mono where the bug worked and you tag the summary of the bug with > > [Regression], then it is much more likely your bug will get fixed. > > > > Please help the Mono team to make 1.9.0 the best release of Mono ever. > > > > Thanks again! > > > > Mono QA > > > > ___ > > 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 signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Snapshot builds
Hi, As was posted in the news items, I am publishing hourly snapshot sources and rpms for some later suse distros. http://mono.ximian.com/monobuild/snapshot/download-trunk/ The wiki has also been updated with this link: http://mono-project.com/Other_Downloads#Snapshots This may be convenient for those who want to run trunk but don't want to be constantly compiling new versions. Enjoy! Wade ___ Ximian-mono-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/ximian-mono-list signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Snapshot builds
Hi, As was posted in the news items, I am publishing hourly snapshot sources and rpms for some later suse distros. http://mono.ximian.com/monobuild/snapshot/download-trunk/ The wiki has also been updated with this link: http://mono-project.com/Other_Downloads#Snapshots This may be convenient for those who want to run trunk but don't want to be constantly compiling new versions. Enjoy! Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono embedding on win32
Hi, I've had some requests to ship a .lib file in the windows installer in order to embed the mono runtime on windows. I found this information: http://cygwin.com/ml/cygwin/2006-01/msg00667.html We're already shipping libmono.dll.a . (I do run strip --strip-unneeded on it, although I'm not sure that affects it.) According to the above post, it appears that the .dll.a can be renamed to a .lib file. What else is missing? Is the above for static importing only? How is the dynamic import lib generated? Is anyone embedding Mono on win32. If so, care to provide some details, and what possible changes are needed in the installer? Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.9.0 Preview 4 is out!!
Yeah, sorry about that. I think they had the wrong preview number on that page for a day or so before I fixed it. Wade On Mon, 2008-03-10 at 21:01 -0600, Thomas Wiest wrote: > D Bera wrote: > >> We've just released Mono 1.9.0 Preview 4 today! Please help us out by > >> giving it a try with your applications. > >> > >> As always, you can get the preview releases here: > >> http://mono.ximian.com/monobuild/preview/download-preview/ > >> > > > > Are the rpms in the link above preview-3 or preview-4 ? The page title > > says preview-4 but the filenames seem to suggest preview-4. If I go > > the download link for suse-103-i586, the page says preview-3 and the > > filenames seem to suggest preview-3 too. Can someone clarify if they > > are actually preview-4 rpms or not ? > > > > Thanks, > > - dBera > > > > > Yes, these are RPMs for preview 4. Our build guy forgot to update the > top of the page. I've cc'd him on this mail. > > Thanks for pointing this out! :) > > Thomas > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono 1.9 Released
Hi, Mono 1.9 was published on March 13th of 2008: http://www.go-mono.com/mono-downloads/download.html This is our best Mono release yet. More than 400 bugs were fixed between 1.2.6 and 1.9. We branched on January 28th of 2008 and did 6 preview releases. More than 100 of those 400 bugs were fixed during the 1.9 preview cycle. To get a list of goodies and changes, check out the release notes: http://www.go-mono.com/archive/1.9/ Big thanks goes to all the bug reporters and fixers and everyone involved making this release happen. Enjoy! Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] 1.9.1 Mono Release
Hi, We've released 1.9.1 as a minor bugfix update to 1.9. The release notes are here: http://go-mono.com/archive/1.9.1/ and downloads are available here: http://www.mono-project.com/Downloads Thanks to all those who contributed to this release. Enjoy! Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] 1.9.1 VMware and LiveCD
Hi, The livecd and vmware images for 1.9.1 have been posted and are available from our download page: http://www.mono-project.com/Downloads Thanks to Thomas and Marek who got mouse and video integration working, as well as drag and drop. Enjoy! Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.lib on Windows
Wow, libmono.a is 64MB, 15 MB compressed... :( Um, maybe we could have
a win32 embedded Wiki page that describes this rather than ship 2 files
of that size in the installer?
Ideas or recommendations?
Wade
On Fri, 2008-05-30 at 18:23 -0600, Wade Berrier wrote:
> Just to be sure, this was using MSVC, correct?
>
> I'll Update the script to make a copy of libmono.a -> mono.lib.
>
> Thanks for trying this out and reporting!
>
> Wade
>
> On Fri, 2008-05-30 at 19:39 -0400, Bill Holmes wrote:
> > Wade,
> >
> > I finally got around to testing using libmono.a as the library to link
> > on Windows and it work fine for me.
> >
> > I did a simple test to call the first symbol I found in the include
> > directory. (See below.) I guess that is enough proof of concept.
> >
> > So the answer to you questoin on Thursday to use libmono.dll.a or
> > libmono.a, the answer is libmono.a.
> >
> > -bill
> >
> > #include "stdafx.h"
> > extern "C"
> > {
> > #include "mono-path.h"
> > }
> >
> > int _tmain(int argc, _TCHAR* argv[])
> > {
> > mono_path_resolve_symlinks ("");
> >
> > return 0;
> > }
signature.asc
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] boo-devel packaging
Hi, I'm planning on making a package split for boo. This came about from banshee depending on boo, which has an assembly that depends on nant, thus pulling in lots of -devel packages. So I'll take Boo.NAnt.Tasks.dll and put it in boo-devel. Debian does a split of .dlls and .exes. Should the .exes also be moved to -devel? Anyone have an opinion on this? Wade signature.asc Description: PGP signature ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Gtk# not found
On Sat, 2006-04-08 at 00:06 +0100, [EMAIL PROTECTED] wrote: > It was good to know that it was a bug, as a first thing, because i actually > ended up suspecting that it might have not been a bug. > And it is good to know that you are still paying attention to it. > And even better to know that you may be seeing a solution. > > I ended up compiling the program with mono 1.1.13.4, to be sure my users could > run it without having to install another mono. This time in Windows. > Yet another funny thing. Tried it in mono 1.1.13.4 (same) in Linux and it > complained again about not finding Gtk... I had used the .bin installer (the > click and run installer). So you may want to check that one too, if that > wasn't > in the plans already. Could you post some details about the error using the Linux installer? The Linux installer comes with gtk# 2.4, while the windows installer comes with gtk# 2.8. Maybe that was the issue? Please run you app with with setting this first: export MONO_LOG_LEVEL=debug and post the output so we can debug this. Thanks! Wade > > > Citando Mike Kestner <[EMAIL PROTECTED]>: > > On Fri, 2006-03-31 at 16:04 +0100, [EMAIL PROTECTED] wrote: > > That instalation of mono worked. My program seemed to run fine. > > In the mean time, i noticed that there is another version of mono, > 1.1.13.6, > and > > went to try that one. It still gives the same problem. > > > > For watever reason, your experimental installer for Windows runs my Gtk# > 2.4 > > application while the official mono one does not (neither in Windows nor in > > Linux)... > > Talked to Wade about this today and we think we figured out why the > mono-project installers policy stuff wasn't working. He's working on > the issue. > > -- > Mike Kestner <[EMAIL PROTECTED]> > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > __ > Porque insiste em pagar o dobro? > Compare o preço da sua ligação à Internet > http://acesso.portugalmail.pt/maisbarato > ___ > 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] Gtk# not found
I've updated the Windows installer (1.1.14) to contain a new gtk# that includes the gtk# policy.config files. Find it here: http://www.mono-project.com/Downloads Wade On Fri, 2006-04-07 at 19:04 -0600, Wade Berrier wrote: > On Sat, 2006-04-08 at 00:06 +0100, [EMAIL PROTECTED] wrote: > > It was good to know that it was a bug, as a first thing, because i actually > > ended up suspecting that it might have not been a bug. > > And it is good to know that you are still paying attention to it. > > And even better to know that you may be seeing a solution. > > > > I ended up compiling the program with mono 1.1.13.4, to be sure my users > > could > > run it without having to install another mono. This time in Windows. > > Yet another funny thing. Tried it in mono 1.1.13.4 (same) in Linux and it > > complained again about not finding Gtk... I had used the .bin installer (the > > click and run installer). So you may want to check that one too, if that > > wasn't > > in the plans already. > > Could you post some details about the error using the Linux installer? > The Linux installer comes with gtk# 2.4, while the windows installer > comes with gtk# 2.8. Maybe that was the issue? > > Please run you app with with setting this first: > > export MONO_LOG_LEVEL=debug > > and post the output so we can debug this. > > Thanks! > > Wade > > > > > > > Citando Mike Kestner <[EMAIL PROTECTED]>: > > > > On Fri, 2006-03-31 at 16:04 +0100, [EMAIL PROTECTED] wrote: > > > That instalation of mono worked. My program seemed to run fine. > > > In the mean time, i noticed that there is another version of mono, > > 1.1.13.6, > > and > > > went to try that one. It still gives the same problem. > > > > > > For watever reason, your experimental installer for Windows runs my Gtk# > > 2.4 > > > application while the official mono one does not (neither in Windows nor > > in > > > Linux)... > > > > Talked to Wade about this today and we think we figured out why the > > mono-project installers policy stuff wasn't working. He's working on > > the issue. > > > > -- > > Mike Kestner <[EMAIL PROTECTED]> > > > > ___ > > Mono-devel-list mailing list > > Mono-devel-list@lists.ximian.com > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > > > > > > __ > > Porque insiste em pagar o dobro? > > Compare o preço da sua ligação à Internet > > http://acesso.portugalmail.pt/maisbarato > > ___ > > 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] Gtk# not found
Hi, thanks for the debug output. >From what it looks like, /lib needs to be added to LD_LIBRARY_PATH. This is a known issue when the installer is run as the root user. (Which it looks like you did since it's installed in /opt). I've updated the faq to explain this better. http://www.mono-project.com/InstallerInstructions You'll need to add this to your environment: LD_LIBRARY_PATH=/opt/mono-1.1.13.4/lib:$LD_LIBRARY_PATH I know this is a sub-optimal solution, but I need to figure out why the Bitrock installer software we use doesn't set up the environment for root. Wade On Mon, 2006-04-10 at 23:21 +0100, [EMAIL PROTECTED] wrote: > Ok, i also remembered to try with my older version. That one had been compiled > in Linux with mono 1.1.13.2 . I remembered of it complaining, also, of not > finding Gtk but it isn't true, it complains of something else. > Attached, i send the file "erro.txt" with the console result. > > One other dude who tried that older 1.1.13.2 version on Linux in mono 1.1.13.4 > said that the program runs well. He didn't installed with the Linux universal > installer, like i did. > > Hope this helps. > > > > [EMAIL PROTECTED] escreveu: > >Attached goes the file "erro.txt" with the output. But, yes, my program uses > >Gtk# 2.8. > > > >And, > >"The Linux installer comes with gtk# 2.4, while the windows installer > > comes with gtk# 2.8." > >Am i very stupid or does this not makes any sense at all? > > > > > > > >Citando Wade Berrier <[EMAIL PROTECTED]>: > > > > On Sat, 2006-04-08 at 00:06 +0100, [EMAIL PROTECTED] wrote: > > > It was good to know that it was a bug, as a first thing, because i > > > actually > > > ended up suspecting that it might have not been a bug. > > > And it is good to know that you are still paying attention to it. > > > And even better to know that you may be seeing a solution. > > > > > > I ended up compiling the program with mono 1.1.13.4, to be sure my users > > could > > > run it without having to install another mono. This time in Windows. > > > Yet another funny thing. Tried it in mono 1.1.13.4 (same) in Linux and it > > > complained again about not finding Gtk... I had used the .bin installer > > (the > > > click and run installer). So you may want to check that one too, if that > > wasn't > > > in the plans already. > > > > Could you post some details about the error using the Linux installer? > > The Linux installer comes with gtk# 2.4, while the windows installer > > comes with gtk# 2.8. Maybe that was the issue? > > > > Please run you app with with setting this first: > > > > export MONO_LOG_LEVEL=debug > > > > and post the output so we can debug this. > > > > Thanks! > > > > Wade > > > > > > > > > > > Citando Mike Kestner <[EMAIL PROTECTED]>: > > > > > > On Fri, 2006-03-31 at 16:04 +0100, [EMAIL PROTECTED] wrote: > > > > That instalation of mono worked. My program seemed to run fine. > > > > In the mean time, i noticed that there is another version of mono, > > 1.1.13.6, > > > and > > > > went to try that one. It still gives the same problem. > > > > > > > > For watever reason, your experimental installer for Windows runs my > > > Gtk# > > > 2.4 > > > > application while the official mono one does not (neither in Windows > > > nor > > in > > > > Linux)... > > > > > > Talked to Wade about this today and we think we figured out why the > > > mono-project installers policy stuff wasn't working. He's working on > > > the issue. > > > > > > -- > > > Mike Kestner <[EMAIL PROTECTED]> > > > > > > ___ > > > Mono-devel-list mailing list > > > Mono-devel-list@lists.ximian.com > > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > > > > > > > > > > > __ > > > Porque insiste em pagar o dobro? > > > Compare o preço da sua ligação à Internet > > > http://acesso.portugalmail.pt/maisbarato > > > ___ > > > 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 > > __ > Email gratuito com 2 000 MB > Espaço para guardar 1 milhão de mensagens > http://www.portugalmail.pt/2000mb ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Win32 build is broken - r59306 - threads.c
This is also happening on macos. Wade On Tue, 2006-04-11 at 14:30 +0200, Kornél Pál wrote: > Hi, > > The error I get: > > /.libs/libmonoruntime.a(threads.o): In function > `mono_debugger_init_threads': > /mono/mono/mono/metadata/threads.c:2902: undefined reference to > `_gc_thread_vtable' > > Please have a look at the problem. > > Kornél > > ___ > 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] MonoDevelop 0.10 in Mono 1.1.4 Linux Installer
1.1.14_1 does come with MD 0.10. 1.1.14_0 does not. The _release revision is only for linux installer updates. Wade On Thu, 2006-04-06 at 18:54 -0400, Daniel Morgan wrote: > Does MonoDevelop 0.10 come in the latest Mono 1.1.14 Linux Installer? > > If not, can it be updated to include it? > > ___ > 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] Mono on the x86 Intel Macs
The plan is to have one out the next couple of weeks. Wade On Wed, 2006-06-14 at 18:40 -0500, Colt D. Majkrzak wrote: > Is there any projected time line on when an Intel Mono installer will > be available for the Intel Mac’s? If not, are there any notes some > where on how to properly build mono for the Intel’s? > > > > Thanks! > > > > - > "[EMAIL PROTECTED]" is a NetIBA validated email address. Certificate > #604044E. Protect yourself against Internet fraud by getting the > Consumer Protection Tool at www.netiba.com/?2764. > > > > > ___ > 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] Preview of the release notes.
Hi, I've created the 10.1 jail for i586 yesterday, and will do x86_64 today. After I get buildbuddy installed and configured I can build some rpms. Wade On Fri, 2006-06-30 at 08:05 -0400, Miguel de Icaza wrote: > Hello, > > > A question: will this release be available in RPMs for SUSE 10.1? Thanks! > > Ah, we should set this up. I will ask Wade. > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Packaging NAnt
Hi, In trying to build and package nant, I've found that nant has some internal libraries that reference the 1.0 profile of .NET: berrier:/usr/src/packages/SPECS # rpm -i ../RPMS/noarch/nant-0.85_rc4-1.noarch.rpm error: Failed dependencies: mono(System) = 1.0.3300.0 is needed by nant-0.85_rc4-1.noarch mono(System.Data) = 1.0.3300.0 is needed by nant-0.85_rc4-1.noarch mono(System.Web) = 1.0.3300.0 is needed by nant-0.85_rc4-1.noarch mono(System.Windows.Forms) = 1.0.3300.0 is needed by nant-0.85_rc4-1.noarch mono(System.Xml) = 1.0.3300.0 is needed by nant-0.85_rc4-1.noarch mono(mscorlib) = 1.0.3300.0 is needed by nant-0.85_rc4-1.noarch Even though the rpm won't install, nant appears to function (by installing it with --nodeps). My question is, why doesn't the runtime croak when trying to load the above missing assemblies? And my next question is, since the runtime doesn't croak, shouldn't monodis be reporting the above versions? This would help for the rpm scripts, otherwise I'll have to use a manual rpm provides for the above assembly versions. Suggestions? Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Packaging NAnt
Hi, On Fri, 2006-07-14 at 11:39 -0300, Rafael Teixeira wrote: > Mono nowadays packs the .NET 1.1 libraries (Version=1.0.5000.0) that > are compatible with the .NET 1.0 libraries (Version=1.0.3300.0). So > adapt your script to add a rpm provides for each 1.1 library you pack. > A better, but more complex solution, is to look at the version policy > files being packed to be sure what manual provides should be issued. > > The ultimate solution would be Nant to be packaged asking for version > >= 1.0.3300.0 of Mono Libraries, as the runtime already knows what to > do as instructed by the version policy files. > Thanks for the explanation and suggestions. I've done just as your last suggestion says: if 1.0.3300.0 version is found to be required, I use the >= rpm op instead of =. This works out great, thanks! Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Packaging NAnt
Hi Gert, On Fri, 2006-07-14 at 18:33 +0200, Gert Driesen wrote: > I really appreciate the work you're doing, but wouldn't it be best if we > (the NAnt team) would release the RPM's ? > > (same goes for NUnit, ...) I think that would be fine. I have an interest in posting and building rpms anyway, simply because I also submit mono packages to SuSE, where they would want to build from source anyway. > > Wouldn't it be better to have the Mono team would share knowledge > (instructions, best practices, ...) and perhaps coordinate the efforts of > other projects. Here's a wiki page about some app guidelines: http://www.mono-project.com/Guidelines:Application_Deployment In this case it comes down to filesystem layout and wrapper scripts. Boo does a good job at this while using nant, and is a good example to look at. I've built a nant rpm and you can see some shell stuff I do here inside the install tag: http://svn.myrealbox.com/viewcvs/trunk/release/conf/nant/ximian-build.conf?view=markup I hope that doesn't break something, but boo and ikvm build fine using the resultant nant rpm. Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Packaging NAnt
Hi, On Sat, 2006-07-15 at 14:32 +0200, Mirco Bauer wrote: > To me this sounds like you try to package binaries, which is bad for > different reasons. One reason you just found, you can't predict the > references that will be used. > If you compile nant correctly from source, you will have the expected > 1.0.5000.0 refs and your RPM scripts will be happy. The issue is that the nant source ships binaries that are compiled against 1.0.3300.0, which is fine because it's important that a program be able to ship a binary that it has been tested and developed against. > I discovered the same problem with MonoDevelop, because it ships a > binary stetic library that was compiled against Gtk# 2.4 but Debian uses > Gtk# 2.8, so the dependency tracker script cries about references that > can't be found in the Debian system. > Mike Kestner got around this by using policy assemblies. He also updated mono-find-provides for rpm to provide gtk# 2.4 and 2.6 assembly versions from the gtk# 2.8 rpm. I ended up having the rpms require >= 1.0.3300.0 as Rafael suggested. I'm not familiar with debian packaging, but this is how it's been sorted out with rpm. Wade signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Class Status updates
Hi, I've recently finished adding the class status webpage generation to the same cron job that produces the dailies (monolite, monocharger, etc). I copied scripts and files from trunk/release/buildbot/scripts to trunk/release/scripts/class_status. mono-snapshot.sh, which produces the dailies, now calls update-status.sh for 1.1 and 2.0. One remaining problem is concerning Microsoft.VisualBasic. Maybe this needs to be removed from $SECTIONS since the source is not in the mcs tree any longer. The error message is at the end of this mail. Enjoy! Wade Error loading infos/Microsoft.VisualBasic.xml: Argument cannot be null. Parameter name: node System.ArgumentNullException: Argument cannot be null. Parameter name: node at Mono.AssemblyCompare.XMLAssembly.LoadData (System.Xml.XmlNode node) [0x0] at Mono.AssemblyCompare.Driver.CreateXMLAssembly (System.String file) [0x0] Unhandled Exception: System.IO.FileNotFoundException: Could not find file "/home/builder/daily/scripts/daily_build/src/build/mono/web/web/src/Microsoft.VisualBasic.xml". : /home/builder/daily/scripts/daily_build/src/build/mono/web/web/src/Microsoft.VisualBasic.xml at System.IO.FileStream..ctor (System.String name, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x0] at System.IO.FileStream..ctor (System.String name, FileMode mode, FileAccess access, FileShare share) [0x0] at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare) at System.Xml.XmlUrlResolver.GetEntity (System.Uri absoluteUri, System.String role, System.Type ofObjectToReturn) [0x0] at System.Xml.XmlTextReader.GetStreamFromUrl (System.String url, System.String& absoluteUriString) [0x0] at System.Xml.XmlTextReader..ctor (System.String url, System.Xml.XmlNameTable nt) [0x0] at System.Xml.XmlDocument.Load (System.String filename) [0x0] at Transform.Transform.Main (System.String[] rgstrArgs) [0x0] Can't open src/Microsoft.VisualBasic.html.in: No such file or directory at htmlify line 4. signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] 1.2 Release Candidate Sources / Call for Testing
Hi, The source tree has been tagged for 1.2. The release candidate tarballs are available here: http://mono.ximian.com/monobuild/rc/sources-rc/ I'll post some packages and repos later, as well as installers. Please try your apps, especially winform apps, and keep the bug reports rolling! Thanks! Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] 1.2 Release Candidate Sources / Call for Testing
I've posted packages and installers. Enjoy! http://mono.ximian.com/monobuild/rc/download-rc/ Wade On Thu, 2006-11-02 at 19:44 -0700, Wade Berrier wrote: > Hi, > > The source tree has been tagged for 1.2. The release candidate tarballs > are available here: > > http://mono.ximian.com/monobuild/rc/sources-rc/ > > I'll post some packages and repos later, as well as installers. > > Please try your apps, especially winform apps, and keep the bug reports > rolling! > > Thanks! > > Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono Daily Downloads
Hi, Several have reported that the tarballs available from mono.ximian.com/daily are not buildable. This is caused by some limitations of the tar format we're using. We must use this limited format to support some older distros. To alleviate this I've begun to use the zip file format for the source distribution instead. (This is created by running make dist-zip instead of make dist). monolite and monocharger will remain in tar.gz format, but the source download is in .zip format. Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono Daily Downloads
Hi, Yes, it is much worse... 20MB to 32MB :( Wade On Sat, 2006-11-11 at 06:24 +0900, Atsushi Eno wrote: > Hi, > > I think zip archive for text files is much worse than tgz at > compression. How was the difference? > > Atsushi Eno > > Wade Berrier wrote: > > Hi, > > > > Several have reported that the tarballs available from > > mono.ximian.com/daily are not buildable. > > > > This is caused by some limitations of the tar format we're using. We > > must use this limited format to support some older distros. > > > > To alleviate this I've begun to use the zip file format for the source > > distribution instead. (This is created by running make dist-zip instead > > of make dist). > > > > monolite and monocharger will remain in tar.gz format, but the source > > download is in .zip format. > > > > Wade > > > > ___ > > 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] Mono Daily Downloads
Raja has fixed the files that were causing the issues with 'make dist', so I've reverted back to using 'make dist' instead of 'make dist-zip'. Wade On Fri, 2006-11-10 at 13:06 -0700, Wade Berrier wrote: > Hi, > > Several have reported that the tarballs available from > mono.ximian.com/daily are not buildable. > > This is caused by some limitations of the tar format we're using. We > must use this limited format to support some older distros. > > To alleviate this I've begun to use the zip file format for the source > distribution instead. (This is created by running make dist-zip instead > of make dist). > > monolite and monocharger will remain in tar.gz format, but the source > download is in .zip format. > > Wade -- Wade Berrier Mono Team [EMAIL PROTECTED] 801-861-5132 Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] 1.2.1 Preview Release
Hi, 1.2.1 has been tagged and preview sources/packages/installers are posted here: http://mono.ximian.com/monobuild/preview/download-preview/ If no major issues are found, this release will be posted to mono-project.com next week. Mono doesn't currently build on solaris, thence the missing package. I'm in the middle of a universal installer for mac, and will hopefully have it ready early next week. Enjoy! Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] 1.2.2 Preview (Was: Re: Call for release notes in 1.2.2)
Hi, Preview sources, packages, and installers for 1.2.2 are located here: http://mono.ximian.com/monobuild/preview/download-preview/ Enjoy! Wade On Fri, 2006-12-01 at 10:39 -0500, Miguel de Icaza wrote: > Hello Jonathan, Wade, > > > Also, if Wade has a Windows preview package, I can run some Moma stats > > for you, like: > > > > - 1.2.2 removes XX MonoTODOs. > > - 1.2.2 removes XX NotImplementedExceptions. > > - 1.2.2 adds XXX previously missing methods. > > Wade, once you have some Windows packages for Mono, could you email > Jonathan so he could provide us with some statistics about the > differences between 1.2.1 and 1.2.2 based on Moma? > > Miguel. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] VMware Image Update - Mono 1.2.2.1 and openSUSE 10.2
Hi, There's a brand new image based on openSUSE 10.2 on the download page with the latest Mono: 1.2.2.1. The image is mostly similar to the previous image but has the following changes: -All packages from a default suse install are included. This results in a bigger image download but should be more convenient. -Postgres has been installed -Bigger default font size -README Index page update with all accounts on the box -samba share set up to /srv/www/htdocs to easily access from Windows -we can easily upgrade the mono stack to the latest version -phpMyAdmin installed and configured -fixed petshop mysql access permissions when checking out from a transaction (although there are still some other bugs in petshop that prevent a full checkout) -.exe files associated with mono in the nautilus file manager to allow launching them via double click -The readme in the image (http://localhost) now includes all accounts for local uesrs, mysql accounts, etc... Enjoy! Available from: http://mono-project.com/Downloads Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] VMware Image Update - Mono 1.2.2.1 and openSUSE 10.2
Yes, although like Miguel says, sounds like they don't work, even though they are included. Wade On Thu, 2006-12-21 at 09:58 -0800, Daniel Morgan wrote: > When you say default suse install, would this include > open office.org 2.x with mono bindings? > > --- Wade Berrier <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > There's a brand new image based on openSUSE 10.2 on > > the download page > > with the latest Mono: 1.2.2.1. > > > > The image is mostly similar to the previous image > > but has the following > > changes: > > > > -All packages from a default suse install are > > included. This results in > > a bigger image download but should be more > > convenient. > > -Postgres has been installed > > -Bigger default font size > > -README Index page update with all accounts on the > > box > > -samba share set up to /srv/www/htdocs to easily > > access from Windows > > -we can easily upgrade the mono stack to the latest > > version > > -phpMyAdmin installed and configured > > -fixed petshop mysql access permissions when > > checking out from a > > transaction (although there are still some other > > bugs in petshop that > > prevent a full checkout) > > -.exe files associated with mono in the nautilus > > file manager to allow > > launching them via double click > > -The readme in the image (http://localhost) now > > includes all accounts > > for local uesrs, mysql accounts, etc... > > > > Enjoy! Available from: > > > > http://mono-project.com/Downloads > > > > Wade > > > > ___ > > Mono-devel-list mailing list > > Mono-devel-list@lists.ximian.com > > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Build is stuck?
Hi, I've 'unstuck' the arm build, although it is failing... Thanks, Wade On Sun, 2006-12-31 at 12:27 +0100, Thomas Strecker wrote: > Hello, > I'm not sure who to contact, so I'll try this way. > The debian-31-arm build > (http://mono.ximian.com/monobuild/python/monobuild.py) is stuck for a > long time now, it seems (Still building rev. 1.2.69237, while the others > are almost a thousand revisions ahead). It's build log didn't change in > like forever and the monitor says (build inprogress [ Running for > 32615 min(s) ]). > Since I am especially interested in the arm(el) builds, I would like to > see that fixed, if possible. > Thank You! > ciao Thomas > ___ > 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] [Ximian-mono-list] Preparing for the 1.2.3 release: tree and release notes.
Hi, There are currently several build failures. Neale is looking into the s390x failure. Macos is failing for both platforms; looks like shell related build failures which I'll look into. Solaris8 on sparc has been failing for some time, as well as debian on arm and sparc. Out of these, I usually only publish the solaris package, but haven't for a few releases since it hasn't been building. Wade On Mon, 2007-01-22 at 19:00 -0500, Miguel de Icaza wrote: > Hello folks, > > I would like to branch the usual modules on Wednesday afternoon, > Boston time so we can start the packaging and get some testing before we > officially release Mono 1.2.3 > > This means two things: lets try to keep the tree stable until then > (no major changes, minimize experimental changes until then); and if > you have any items that are relevant to the release notes, please send > those to me. > > Miguel. > ___ > Ximian-mono-list mailing list > [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/ximian-mono-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Ximian-mono-list] Feedback needed: Preview of release notes for Mono 1.2.3
This is the first release we're shipping IPCE instead of IronPython. Also, it might be worthwhile to mention the sparc speedups. Wade On Tue, 2007-01-23 at 14:02 -0500, Miguel de Icaza wrote: > As usual, the preview for the Mono 1.2.3 release is here: > > http://www.go-mono.com/archive/1.2.3/ > > Please send me feedback if you want me to add/expand/remove/improve the > current text. > > The list of contributors is only those that I manually tracked, I will > later scan the ChangeLogs. > > Miguel. > ___ > Ximian-mono-list mailing list > [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/ximian-mono-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] monologue and RSS.NET.dll
Hi,
If RSS.NET.dll (DateTime.Parse()) can't parse a date it uses
DateTime.MinValue in it's place.
This was happening for lupus' feed, making his old posts always show up
on monologue.
The maintainer of advogato fixed the date format in his rss feeds so
this shouldn't happen anymore.
I'm thinking it's a bad idea that feeds with invalid date formats become
permalinks (monologue's worker):
if (i.PubDate == DateTime.MinValue || i.PubDate >= minPubDate) {
Ok to remove 'i.PubDate == DateTime.MinValue ||' ?
Wade
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] monologue and RSS.NET.dll
Good idea. Patch attached. If no one objects, I'll commit.
Wade
On Fri, 2007-02-09 at 09:02 -0200, Rafael Teixeira wrote:
> I vote yes, but it would be nice to tag the error in the author's list
> to the right, as when the feed can't be read.
>
> :)
>
> On 2/8/07, Wade Berrier <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > If RSS.NET.dll (DateTime.Parse()) can't parse a date it uses
> > DateTime.MinValue in it's place.
> >
> > This was happening for lupus' feed, making his old posts always show up
> > on monologue.
> >
> > The maintainer of advogato fixed the date format in his rss feeds so
> > this shouldn't happen anymore.
> >
> > I'm thinking it's a bad idea that feeds with invalid date formats become
> > permalinks (monologue's worker):
> >
> > if (i.PubDate == DateTime.MinValue || i.PubDate >= minPubDate) {
> >
> > Ok to remove 'i.PubDate == DateTime.MinValue ||' ?
> >
> > Wade
> >
> > ___
> > Mono-devel-list mailing list
> > Mono-devel-list@lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
>
>
Index: monologue-worker.cs
===
--- monologue-worker.cs (revision 72550)
+++ monologue-worker.cs (working copy)
@@ -160,7 +160,9 @@
foreach (Blogger b in bloggers.BloggersByUrl) {
if (b.Channel == null) continue;
foreach (RssItem i in b.Channel.Items) {
-if (i.PubDate == DateTime.MinValue || i.PubDate >= minPubDate) {
+if (i.PubDate == DateTime.MinValue) {
+ b.DateError = true;
+} else if (i.PubDate >= minPubDate) {
i.Title = b.Name + ": " + i.Title;
stories.Add (i);
}
@@ -196,6 +198,7 @@
}
static string error_msg = "Error retrieving/loading feed";
+ static string date_error_msg = "Invalid dates in feed";
static string error_img = "";
static void Render ()
{
@@ -203,8 +206,8 @@
tpl.selectSection ("BLOGGER");
foreach (Blogger b in bloggers.Bloggers) {
- tpl.setField ("BLOGGER_ERROR_MSG", b.Error ? error_msg : "");
- tpl.setField ("BLOGGER_ERROR_IMG", b.Error ? error_img : "");
+ tpl.setField ("BLOGGER_ERROR_MSG", b.Error ? error_msg : b.DateError ? date_error_msg : "");
+ tpl.setField ("BLOGGER_ERROR_IMG", b.Error || b.DateError ? error_img : "");
tpl.setField ("BLOGGER_URL", b.HtmlUrl.ToString ());
tpl.setField ("BLOGGER_NAME", b.Name);
@@ -364,6 +367,7 @@
[XmlAttribute] public string IrcNick;
[XmlAttribute] public string Head;
bool error;
+ bool date_error;
[XmlIgnore]
public string ID {
@@ -406,6 +410,11 @@
}
}
+ public bool DateError {
+ get { return (date_error || feed == null); }
+ set { date_error = value; }
+ }
+
public bool Error {
get { return (error || feed == null); }
set { error = value; }
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [Fwd: Re: [Mono-list] New anonymous subversion hostname]
Notice to all using the anonymous subversion repository: svn.myrealbox.com has been renamed to anonsvn.mono-project.com Wade --- Begin Message --- Wow, the dns name svn.myrealbox.com has been turned off already. That happened much sooner than I expected. Sorry about the short notice, Wade On Tue, 2007-04-10 at 18:35 -0600, Wade Berrier wrote: > On Tue, 2007-04-10 at 20:31 -0400, Joshua Tauberer wrote: > > Wade Berrier wrote: > > > There is a simple way to migrate existing svn repositories to use the > > > new hostname. > > > > Slightly simpler :) is to use: > > Haha, MUCH simpler, thanks :) > > > ___ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list --- End Message --- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Fwd: Re: [Mono-list] New anonymous subversion hostname]
What svn rss feed? Is that something outside of Novell? Wade On Thu, 2007-04-12 at 09:57 +0200, Mark IJbema wrote: > Hoping that the person maintining the svn rss feed is on this list, will > it be updated to reflect this new url? > > Regards, > > Mark > > On Wed, Apr 11, 2007 at 01:31:41PM -0600, Wade Berrier wrote: > > Notice to all using the anonymous subversion repository: > > > > svn.myrealbox.com has been renamed to anonsvn.mono-project.com > > > > Wade > > Content-Description: Forwarded message - Re: [Mono-list] New anonymous > subversion hostname > > Subject: Re: [Mono-list] New anonymous subversion hostname > > From: Wade Berrier <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > > > Wow, the dns name svn.myrealbox.com has been turned off already. That > > happened much sooner than I expected. > > > > Sorry about the short notice, > > > > Wade > > > > On Tue, 2007-04-10 at 18:35 -0600, Wade Berrier wrote: > > > On Tue, 2007-04-10 at 20:31 -0400, Joshua Tauberer wrote: > > > > Wade Berrier wrote: > > > > > There is a simple way to migrate existing svn repositories to use the > > > > > new hostname. > > > > > > > > Slightly simpler :) is to use: > > > > > > Haha, MUCH simpler, thanks :) > > > > > > > > > ___ > > > Mono-list maillist - [EMAIL PROTECTED] > > > http://lists.ximian.com/mailman/listinfo/mono-list > > > ___ > > 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 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Call for testing: Mono 1.2.4 Preview Available
Hi, Mono 1.2.4 preview sources, packages, and installers are available at: http://mono.ximian.com/monobuild/preview/download-preview/ The beginnings of the release notes for 1.2.4 are available at: http://go-mono.com/archive/1.2.4/ If no critical bugs are found after the preview period, these same downloads will be posted on mono-project.com for general consumption. If there are critical bugs found, only those packages/sources will be updated before publishing to mono-project.com. Since this release hasn't been pushed to our main download server, some sources may be retagged if critical bugs are found. Those tags are not final until we publish to mono-project.com. Wade ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
