Re: [Mono-dev] Mono Compile Error in Solaris 8
I fixed that error! It seemed to be looking at the glibconfigure.h for glib 1.2, and it was using the glib 2.0 other files. So thats why I was getting the errorrs. I went ahead and installed a new version of glib and removed 1.22, and it went through fine. However, I am still getting the following error now, that has to be with bison and parser.c. I can't seem to find that file anywhere in the directories, so I don't know what it does. Any help is appreciated!! bison ./monoburg.y -o parser.c *** Signal 13 make: Fatal error: Command failed for target `parser.c' Current working directory /export/home/users/niteesh/mono/mono-1.1.8.3/mono/monoburg *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /export/home/users/niteesh/mono/mono-1.1.8.3/mono *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /export/home/users/niteesh/mono/mono-1.1.8.3 *** Error code 1 make: Fatal error: Command failed for target `all' On 8/20/05, Nit Bha [EMAIL PROTECTED] wrote: To: Zoltan Varga [EMAIL PROTECTED] Subject: Re: [Mono-dev] Mono Compile Error in Solaris 8 Cc: [EMAIL PROTECTED] ahh.. worked wonders! found ar and included it in my path. thanks! I have a few more errors now though! :( I have glib 2.6.2 installed from sunfreeware and I am getting the following error log when I compile mono. It goes on longer then I have pasted. I pasted teh beginning, and then I pasted what it has in the end. If anybody can help me I would really really appreciate it! Thanks again for all your help! -- if /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../mono -I../../libgc/include -threads -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -D_XOPEN_SOURCE_EXTENDED=1 -DNO_UNALIGNED_ACCESS -g -O2 -fno-strict-aliasing -Wdeclaration-after-statement -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -Wno-char-subscripts -Wno-cast-align -MT mono-hash.lo -MD -MP -MF .deps/mono-hash.Tpo -c -o mono-hash.lo mono-hash.c; \ then mv -f .deps/mono-hash.Tpo .deps/mono-hash.Plo; else rm -f .deps/mono-hash.Tpo; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../mono -I../../libgc/include -threads -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -D_XOPEN_SOURCE_EXTENDED=1 -DNO_UNALIGNED_ACCESS -g -O2 -fno-strict-aliasing -Wdeclaration-after-statement -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -Wno-char-subscripts -Wno-cast-align -MT mono-hash.lo -MD -MP -MF .deps/mono-hash.Tpo -c mono-hash.c -fPIC -DPIC -o .libs/mono-hash.o In file included from /usr/local/include/glib-2.0/glib/galloca.h:30, from /usr/local/include/glib-2.0/glib.h:30, from mono-hash.c:39: /usr/local/include/glib-2.0/glib/gtypes.h:41: error: syntax error before typedef In file included from /usr/local/include/glib-2.0/glib.h:31, from mono-hash.c:39: /usr/local/include/glib-2.0/glib/garray.h:32: error: parse error before G_BEGIN_DECLS /usr/local/include/glib-2.0/glib/garray.h:34: error: syntax error before typedef In file included from /usr/local/include/glib-2.0/glib/gerror.h:24, from /usr/local/include/glib-2.0/glib/gthread.h:30, from /usr/local/include/glib-2.0/glib/gasyncqueue.h:30, from /usr/local/include/glib-2.0/glib.h:32, from mono-hash.c:39: /usr/local/include/glib-2.0/glib/gquark.h:32: error: parse error before G_BEGIN_DECLS /usr/local/include/glib-2.0/glib/gquark.h:34: error: syntax error before typedef /usr/local/include/glib-2.0/glib/gquark.h:41: error: syntax error before gchar /usr/local/include/glib-2.0/glib/gquark.h:41: error: parse error before G_GNUC_CONST /usr/local/include/glib-2.0/glib/gquark.h:41: warning: type defaults to `int' in declaration of `G_GNUC_CONST' /usr/local/include/glib-2.0/glib/gquark.h:41: warning: data definition has no type or storage class In file included from /usr/local/include/glib-2.0/glib/gthread.h:30, from /usr/local/include/glib-2.0/glib/gasyncqueue.h:30,
Re: [Mono-dev] gtk-sharp bootstrap vs. bootstrap-2.4
Hi, I'm further confused by this information: http://www.all-the-johnsons.co.uk/mono/mono-compiling.html The build process for gtk-sharp is different to the other modules in mono. Instead of ./autogen.sh, there is the choice of ./bootstrap and ./bootstrap-2.4. The only difference is if you're using the bleeding edge version, you should use the 2.4 version. gtk-sharp comes in two flavours. One is designed for the stable mono, the other for those using the developer branch (and now a third for the clinically insane by the looks of it!). bootstrap is for stable, bootstrap-2.4 is for the developers version. At least, that's how I understand it. TTFN Paul -- A lot of football success is in the mind. You must believe you are the best and then make sure that you are. In my time at Liverpool we always said we had the best two teams on Merseyside, Liverpool and Liverpool Reserves. - Bill Shankly ___ Mono-devel-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] error: too few arguments to function `glitz_surface_create'
[NOTE: this was cc'ed to the list, but I did not receive that copy. As a general rule, I much prefer that mailing list replies are sent only to the list. I am on dozens of mailing list, and receiving multiple copies, or messages not containing a List-Id header can cause a lot of trouble for both me and my mail filters.] On Monday 22 August 2005 00:29, Miguel de Icaza wrote: I'm trying to build mono and MonoDevelop on a SuSE 9.3+ box (see below for specs). Though it's probably not the source of my problem, I should mention that, in proper Unix fashion, I am installing to a non-system directory. Any advice would be appreciated. Mhm, sounds like you got some form of Glitz installed, make sure cairo in libgdiplus does not use it I /do/ have glitz and cairo development packages installed. I started to remove these, but the dependency graph was a bit too complicated to justify the effort. ls /usr/include/glitz* /usr/include/glitz-glx.h /usr/include/glitz.h I'm going to attempt what you suggested. I'm a bit surprised the configuration scripts from svn are not handling this. -- Regards, Steven ___ Mono-devel-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] GC segfault on ARM
On Sat, 20 Aug 2005, Paolo Molaro wrote: On 08/18/05 Tomi Valkeinen wrote: Oh, and if you are using an ARM11 based board, you may also want to fix the swp-bug (http://bugzilla.ximian.com/show_bug.cgi?id=75114) Did you test that change? Care to research with the libc guys why they wrote it that way and if your change is really the right fix? Hi, Yes, I did test it. All compilers seem to produce correct code after the change. The interesting part with the bug is that even if the produced code is against ARM reference manual, it works with all the ARM9 processors I have tested, but fails with ARM11. The code in recent libc is actually a bit different. This is from glibc-2.3.5: __asm__ __volatile__(swp %0, %1, [%2] : =r(ret) : 0(1), r(spinlock)); And this is from mono's libgc: __asm__ __volatile__(swp %0, %1, [%2] : =r(oldval) : r(1), r(addr) : memory); The version in glibc produces correct code. The fix that I proposed was suggested in Codesourcery's forums, but I guess the libc version is just as fine. Tomi Valkeinen ___ Mono-devel-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] gtk-sharp: Optional assemblies
I'm confuses as to what is meant by Optional assemblies in the gtk-sharp build. If I install the rpms for the listed assemblies, they will show as yes, but but I'm not sure what that means. Are they being built when I make gtk-sharp, or is something from the rpms being registered in or copied into the final product of the build process? I've had some conflict problems with some of these, and would rather not have anything non-essential installed. Configuration summary * Installation prefix = /home/hattons/opt/org/go-mono * C# compiler: /home/hattons/opt/org/go-mono/bin/mcs -define:GTK_SHARP_2_6 Optional assemblies included in the build: * art-sharp.dll: yes * gnomevfs-sharp.dll: no * gnome-sharp.dll: no * glade-sharp.dll: yes * rsvg-sharp.dll: no * gtkhtml-sharp.dll: no * vte-sharp.dll: no * gtk-dotnet.dll: yes NOTE: if any of the above say 'no' you may install the corresponding development packages for them, rerun autogen.sh to include them in the build. * Documentation build enabled: no Now type `make' to compile -- Regards, Steven ___ Mono-devel-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding
Hi,
I think using 1252 as a fallback is better than UTF-8 as it is a regular
single-byte code page. UTF-8 should be detected (and I think it is detected)
using byte order marks anyway.
I agree that using 28591 as the default encoding is is a bad decission.
What about using Encoding.Default instead of
CultureInfo.CurrentCulture.TextInfo.ANSICodePage as it is really based on
system code page?
Kornél
- Original Message -
From: Atsushi Eno [EMAIL PROTECTED]
To: mono-devel mailing list mono-devel-list@lists.ximian.com
Sent: Monday, August 22, 2005 7:59 AM
Subject: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding
Any comments on this patch? If we leave this problem as is, most
of native-language dependent applications won't compile fine
(as I experienced on many Japanese sources).
Atsushi Eno
Atsushi Eno wrote:
Hello,
I've attached a fix for mcs to not use Latin1 encoding everywhere.
I think it should be default encoding of current culture (for
example the codepage is 932 on my Japanese environment, neither
28591 nor 1252).
But in case we really don't have the corresponding encoding that
CultureInfo.CurrentCulture.TextInfo indicates (it should be
supplied though), we should use culture-independent encoding, so
I think it should be utf-8, instead of iso-8859-1.
Atsushi Eno
Index: driver.cs
===
--- driver.cs (revision 47877)
+++ driver.cs (working copy)
@@ -1374,10 +1374,10 @@
bool parsing_options = true;
try {
- encoding = Encoding.GetEncoding (28591);
+ encoding = Encoding.GetEncoding
(CultureInfo.CurrentCulture.TextInfo.ANSICodePage);
} catch {
Console.WriteLine (Error: could not load encoding 28591, trying 1252);
- encoding = Encoding.GetEncoding (1252);
+ encoding = Encoding.UTF8;
}
references = new ArrayList ();
___
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] Re: [Mono-devel-list] mcs patch for default encoding
Hi Marek, Marek Safar wrote: Hello Eno, Any comments on this patch? If we leave this problem as is, most of native-language dependent applications won't compile fine (as I experienced on many Japanese sources). Probably, we will have to fix this bug first. http://bugzilla.ximian.com/show_bug.cgi?id=73086 Agreed. In fact, I was also fixing bug #75065, maybe duplicate. I have a fix for UTF8Encoding, but it uncovered another mcs bug which does not handle files with BOM with specific encoding. To summarize the situation: - Currently driver.cs does not process source files with default encoding. - UTF8Encoding.cs does not handle U+FEFF correctly. - When we fix UTF8Encoding.cs to handle U+FEFF, it starts to reject some source files which has BOM. (CS8025:Parsing error) - Even if we fix driver.cs to let StreamReader consider BOM (currently we disable it), there are still some files borking. Am digging into this bug in depth. Hopefully I'll post a set of fixes later. Atsushi Eno ___ 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-devel-list] mcs patch for default encoding
Hi, I think using 1252 as a fallback is better than UTF-8 as it is a regular single-byte code page. UTF-8 should be detected (and I think it is detected) using byte order marks anyway. I agree that using 28591 as the default encoding is is a bad decission. This guess is Western centric ;-) Neither 1252 nor 28591 is regular code page. For example, almost all Japanese text editors does not support iso-8859-1 in save as... feature (usually, only shift_jis (932/ANSI), iso-2022-jp (50221) and euc-jp (50932) are supported). I assume this situation is common to other Asian nations. (Thus Japanese hackers were reluctant to edit such files on which someone wrote only-iso-8859-1 letters.) UTF-8 should be detected but cannot be done perfectly (automatic encoding detection is not always possible) and actually we don't support further auto detection than BOM lookup (csc seems to handle them fine). This could be fixed but in reality it's not working. So I think using utf-8 as the default would make better sense. What about using Encoding.Default instead of CultureInfo.CurrentCulture.TextInfo.ANSICodePage as it is really based on system code page? Yeah, I'd change them as such. Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] IA64 port is ready
Hi, The instruction scheduling stuff is basically an attempt to pack more than 1 instruction into each bundle and avoid emitting a ia64 stop after each instruction. It is IA64 only. Zoltan On 8/22/05, Miguel de Icaza [EMAIL PROTECTED] wrote: Hello! The IA64 port of mono is now done and it is in SVN. It has only been tested on debian unstable. Please try it out and report bugs/problems to bugzilla. Congratulations! This is an amazing accomplishment: it took you three months while also fixing numerous other bugs and rolling out the first release of the mono jit for a frightening instruction set. I noticed some goodies in the ia64 port like instruction scheduling, can you tell us a bit about that? And once again, congratulations on finishing the port! ___ 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-devel-list] mcs patch for default encoding
1252 is far from Hungarian as well altough I think not as far as from Japanese.:) But normally Encoding.Default will be used that depends on the hacker. If he likes Japanese code pages he can set them on the system and will be used by mcs. The second case is only a fallback. And I think using a simple SBCS latin code page is better. Kornél - Original Message - From: Atsushi Eno [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel mailing list mono-devel-list@lists.ximian.com Sent: Monday, August 22, 2005 11:13 AM Subject: Re: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding Hi, I think using 1252 as a fallback is better than UTF-8 as it is a regular single-byte code page. UTF-8 should be detected (and I think it is detected) using byte order marks anyway. I agree that using 28591 as the default encoding is is a bad decission. This guess is Western centric ;-) Neither 1252 nor 28591 is regular code page. For example, almost all Japanese text editors does not support iso-8859-1 in save as... feature (usually, only shift_jis (932/ANSI), iso-2022-jp (50221) and euc-jp (50932) are supported). I assume this situation is common to other Asian nations. (Thus Japanese hackers were reluctant to edit such files on which someone wrote only-iso-8859-1 letters.) UTF-8 should be detected but cannot be done perfectly (automatic encoding detection is not always possible) and actually we don't support further auto detection than BOM lookup (csc seems to handle them fine). This could be fixed but in reality it's not working. So I think using utf-8 as the default would make better sense. What about using Encoding.Default instead of CultureInfo.CurrentCulture.TextInfo.ANSICodePage as it is really based on system code page? Yeah, I'd change them as such. Atsushi Eno ___ 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] RE: [Mono-patches] r48646 - in trunk/mcs: build/commonclass/System.DirectoryServices
Hello all I've just noticed that trunk/mcs/build/common/ lacks ChangeLog. Should we add one? -- Boris Kirzner Mono RD team, Mainsoft Corporation. Blogging at http://boriskirzner.blogspot.com/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boris Kirzner [EMAIL PROTECTED] Sent: Monday, August 22, 2005 12:20 To: mono-patches@lists.ximian.com; [EMAIL PROTECTED] Subject: [Mono-patches] r48646 - in trunk/mcs: build/commonclass/System.DirectoryServices Author: borisk Date: 2005-08-22 05:19:48 -0400 (Mon, 22 Aug 2005) New Revision: 48646 Modified: trunk/mcs/build/common/Consts.cs trunk/mcs/class/System.DirectoryServices/ChangeLog trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcs proj Log: Fixed build for TARGET_JVM. Modified: trunk/mcs/build/common/Consts.cs === --- trunk/mcs/build/common/Consts.cs 2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/build/common/Consts.cs 2005-08-22 09:19:48 UTC (rev 48646) @@ -51,7 +51,7 @@ #if NET_2_0 || BOOTSTRAP_NET_2_0 public const string FxVersion = 2.0.0.0; public const string VsVersion = 8.0.0.0; -#elif NET_1_1 +#elif NET_1_1 || TARGET_JVM public const string FxVersion = 1.0.5000.0; public const string VsVersion = 7.0.5000.0; #elif NET_1_0 Modified: trunk/mcs/class/System.DirectoryServices/ChangeLog === --- trunk/mcs/class/System.DirectoryServices/ChangeLog 2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/class/System.DirectoryServices/ChangeLog 2005-08-22 09:19:48 UTC (rev 48646) @@ -1,3 +1,6 @@ +2005-22-08 Boris Kirzner [EMAIL PROTECTED] + * System.DirectoryServices.vmwcsproj: changed reference to Consts.cs. + 2005-14-08 Boris Kirzner [EMAIL PROTECTED] * App.config: added authenticationmech supported key example. Modified: trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcspro j === --- trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcspro j 2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcspro j 2005-08-22 09:19:48 UTC (rev 48646) @@ -13,11 +13,11 @@ /Build Files Include + File RelPath=Consts.cs Link=..\..\build\common\Consts.cs SubType=Code BuildAction=Compile/ File RelPath=Locale.cs Link=..\..\build\common\Locale.cs SubType=Code BuildAction=Compile/ File RelPath=MonoTODOAttribute.cs Link=..\..\build\common\MonoTODOAttribute.cs SubType=Code BuildAction=Compile/ File RelPath=Assembly\AssemblyInfo.cs SubType=Code BuildAction=Compile/ File RelPath=Assembly\ChangeLog BuildAction=None/ - File RelPath=Assembly\Consts.cs SubType=Code BuildAction=Compile/ File RelPath=System.DirectoryServices\AuthenticationTypes.cs SubType=Code BuildAction=Compile/ File RelPath=System.DirectoryServices\ChangeLog BuildAction=None/ File RelPath=System.DirectoryServices\DirectoryEntries.cs SubType=Code BuildAction=Compile/ ___ 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] r48646 - in trunk/mcs:build/commonclass/System.DirectoryServices
Adding a ChangeLog is a good idea as it makes people adding ChangeLog entries as well.:) Kornél - Original Message - From: Boris Kirzner [EMAIL PROTECTED] To: mono-devel mailing list mono-devel-list@lists.ximian.com Sent: Monday, August 22, 2005 11:29 AM Subject: [Mono-dev] RE: [Mono-patches] r48646 - in trunk/mcs:build/commonclass/System.DirectoryServices Hello all I've just noticed that trunk/mcs/build/common/ lacks ChangeLog. Should we add one? -- Boris Kirzner Mono RD team, Mainsoft Corporation. Blogging at http://boriskirzner.blogspot.com/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boris Kirzner [EMAIL PROTECTED] Sent: Monday, August 22, 2005 12:20 To: mono-patches@lists.ximian.com; [EMAIL PROTECTED] Subject: [Mono-patches] r48646 - in trunk/mcs: build/commonclass/System.DirectoryServices Author: borisk Date: 2005-08-22 05:19:48 -0400 (Mon, 22 Aug 2005) New Revision: 48646 Modified: trunk/mcs/build/common/Consts.cs trunk/mcs/class/System.DirectoryServices/ChangeLog trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcs proj Log: Fixed build for TARGET_JVM. Modified: trunk/mcs/build/common/Consts.cs === --- trunk/mcs/build/common/Consts.cs 2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/build/common/Consts.cs 2005-08-22 09:19:48 UTC (rev 48646) @@ -51,7 +51,7 @@ #if NET_2_0 || BOOTSTRAP_NET_2_0 public const string FxVersion = 2.0.0.0; public const string VsVersion = 8.0.0.0; -#elif NET_1_1 +#elif NET_1_1 || TARGET_JVM public const string FxVersion = 1.0.5000.0; public const string VsVersion = 7.0.5000.0; #elif NET_1_0 Modified: trunk/mcs/class/System.DirectoryServices/ChangeLog === --- trunk/mcs/class/System.DirectoryServices/ChangeLog 2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/class/System.DirectoryServices/ChangeLog 2005-08-22 09:19:48 UTC (rev 48646) @@ -1,3 +1,6 @@ +2005-22-08 Boris Kirzner [EMAIL PROTECTED] + * System.DirectoryServices.vmwcsproj: changed reference to Consts.cs. + 2005-14-08 Boris Kirzner [EMAIL PROTECTED] * App.config: added authenticationmech supported key example. Modified: trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcspro j === --- trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcspro j 2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/class/System.DirectoryServices/System.DirectoryServi ces.vmwcspro j 2005-08-22 09:19:48 UTC (rev 48646) @@ -13,11 +13,11 @@ /Build Files Include + File RelPath=Consts.cs Link=..\..\build\common\Consts.cs SubType=Code BuildAction=Compile/ File RelPath=Locale.cs Link=..\..\build\common\Locale.cs SubType=Code BuildAction=Compile/ File RelPath=MonoTODOAttribute.cs Link=..\..\build\common\MonoTODOAttribute.cs SubType=Code BuildAction=Compile/ File RelPath=Assembly\AssemblyInfo.cs SubType=Code BuildAction=Compile/ File RelPath=Assembly\ChangeLog BuildAction=None/ - File RelPath=Assembly\Consts.cs SubType=Code BuildAction=Compile/ File RelPath=System.DirectoryServices\AuthenticationTypes.cs SubType=Code BuildAction=Compile/ File RelPath=System.DirectoryServices\ChangeLog BuildAction=None/ File RelPath=System.DirectoryServices\DirectoryEntries.cs SubType=Code BuildAction=Compile/ ___ 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 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [Fwd: [Mono-patches] r48646 - in trunk/mcs: build/commo n class/System.DirectoryServices]
Hi Boris, Modified: trunk/mcs/build/common/Consts.cs === --- trunk/mcs/build/common/Consts.cs2005-08-22 06:17:11 UTC (rev 48645) +++ trunk/mcs/build/common/Consts.cs2005-08-22 09:19:48 UTC (rev 48646) @@ -51,7 +51,7 @@ #if NET_2_0 || BOOTSTRAP_NET_2_0 public const string FxVersion = 2.0.0.0; public const string VsVersion = 8.0.0.0; -#elif NET_1_1 +#elif NET_1_1 || TARGET_JVM public const string FxVersion = 1.0.5000.0; public const string VsVersion = 7.0.5000.0; #elif NET_1_0 Just curious, aren't you setting NET_1_1 by default? It should be used all around mcs source code and if you actually define NET_1_1 this fix would be extraneous. Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] error: too few arguments to function `glitz_surface_create'
Hi! I came up against this yesterday, building Mono on AMD64 Ubuntu Breezy... Mhm, sounds like you got some form of Glitz installed, make sure cairo in libgdiplus does not use it I /do/ have glitz and cairo development packages installed. I started to remove these, but the dependency graph was a bit too complicated to justify the effort. ls /usr/include/glitz* /usr/include/glitz-glx.h /usr/include/glitz.h I'm going to attempt what you suggested. I'm a bit surprised the configuration scripts from svn are not handling this. I guess the old version of Cairo (0.3.0) included in libgdiplus doesn't interface with the latest version of Glitz. Firstly, it's not necessary to remove Glitz and Cairo dev packages from your system. Just pass --disable-glitz to the libgdiplus configuration script (thanks latexer on #mono!) That fixed it for me; hope it works for you. Regards, Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [PATCH] Monodoc: Add contribution links to home page
Hey,
here is the patch to add links to contributions at the home page.
When there are no contributions a text is shown (please someone revise
it since I'm not english spoken person). To add the links I've added a
new NodeUrl property to Change objects. That means that contributions
made before this patch will not show a link (although the text saying
the number of contributions left to send does include them).
I've added a new GetNiceUrl method to obtain url of the type
T:System.String from a node, since I didn't found a better way to get
the contribution url.
I'm thinking now in a method to delete contributions and I have two ideas:
* a delete link at the home page
* When you are editing a node, a new button called Restore
* A new Menu entry that pops up a dialog showing a table with your
contributions that lets you delete them and select which ones do you
want to upload
Which one do you think is better? All of them?
Mario.
Index: browser/editing.cs
===
--- browser/editing.cs (revision 48386)
+++ browser/editing.cs (working copy)
@@ -80,7 +80,7 @@
}
- public static void SaveChange (string url, RootTree tree, XmlNode node)
+ public static void SaveChange (string url, RootTree tree, XmlNode node, string node_url)
{
string [] uSplit = ParseEditUrl (url);
@@ -91,7 +91,7 @@
int prov = int.Parse (uSplit [0].Substring(monodoc://.Length));
HelpSource hs = tree.GetHelpSourceFromId (prov);
-changes.AddChange (hs.Name, hs.GetRealPath (id), xp, node);
+changes.AddChange (hs.Name, hs.GetRealPath (id), xp, node, node_url);
changes.Save ();
} else if (uSplit[0].StartsWith(file:)) {
uSplit[0] = uSplit[0].Substring(5);
@@ -265,11 +265,12 @@
}
}
- Change NewChange (string xpath, XmlNode new_node)
+ Change NewChange (string xpath, XmlNode new_node, string node_url)
{
Change new_change = new Change ();
new_change.XPath = xpath;
new_change.NewNode = new_node;
+ new_change.NodeUrl = node_url;
Console.WriteLine (New serial: + SettingsHandler.Settings.SerialNumber);
new_change.Serial = SettingsHandler.Settings.SerialNumber;
@@ -277,10 +278,10 @@
return new_change;
}
- public void AddChange (string doc_set, string real_file, string xpath, XmlNode new_node)
+ public void AddChange (string doc_set, string real_file, string xpath, XmlNode new_node, string node_url)
{
FileChangeset new_file_change_set;
- Change new_change = NewChange (xpath, new_node);
+ Change new_change = NewChange (xpath, new_node, node_url);
if (real_file == null)
throw new Exception (Could not find real_file. Please talk to Miguel or Ben about this);
@@ -391,6 +392,7 @@
public class Change {
[XmlAttribute] public string XPath;
[XmlAttribute] public int FromVersion = RootTree.MonodocVersion;
+ [XmlAttribute] public string NodeUrl;
public XmlNode NewNode;
Index: browser/provider.cs
===
--- browser/provider.cs (revision 48618)
+++ browser/provider.cs (working copy)
@@ -1086,6 +1086,7 @@
return (HelpSource) help_sources [id];
}
+ string home_cache;
/// summary
///Allows every HelpSource to try to provide the content for this
///URL.
@@ -1095,12 +1096,69 @@
lastHelpSourceTime = DateTime.MinValue;
if (url == root:) {
match_node = this;
- StringBuilder sb = new StringBuilder (table bgcolor=\#b0c4de\ width=\100%\ cellpadding=\5\trtdh3Mono Documentation Library/h3/td/tr/table);
+
+ // look whether there are contribs
+ GlobalChangeset chgs = GlobalChangeset.Load ();
+ string contrib = chgs.Count == 1?There is {0} contribution:There are {0} contributions;
+ StringBuilder con = new StringBuilder ();
+ con.Append (String.Format (contrib, chgs.Count) + for uploading i(Menu -- Upload Contributions)/i);
+ //add links to the contrib
+ con.Append (ul);
+ foreach (DocSetChangeset dscs in chgs.DocSetChangesets)
+foreach (FileChangeset fcs in dscs.FileChangesets)
+ foreach (Change c in fcs.Changes)
+ if (c.NodeUrl != null)
+ con.Append (String.Format (lia href=\{0}\{0}/a/li, c.NodeUrl));
+
+ con.Append (/ul);
+ if (!HelpSource.use_css) {
+StringBuilder sb = new StringBuilder (table bgcolor=\#b0c4de\ width=\100%\ cellpadding=\5\trtdh3Mono Documentation Library/h3/td/tr/table);
- foreach (Node n in Nodes)
-sb.AppendFormat (a href='{0}'{1}/abr/, n.Element, n.Caption);
+foreach (Node n in Nodes)
+ sb.AppendFormat (a href='{0}'{1}/abr/, n.Element, n.Caption);
- return sb.ToString ();
+//contributions
+sb.Append (brtable bgcolor=\#fff3f3\ width=\100%\ cellpadding=\5\trtd);
+sb.Append (h5Contributions/h5br);
+if (chgs.Count == 0) {
+ sb.Append (pbYou don't have any contribution yet./b/p);
+ sb.Append (pThe Documentation of the libraries is not complete and
Re: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding
Hi, Ok, then now I'll stop pushing shift_jis as the default (well, I didn't ;-) and just use Encoding.Default. BTW if it falls back to unsupported case, then this property returns UTF8. Atsushi Eno Kornél Pál wrote: 1252 is far from Hungarian as well altough I think not as far as from Japanese.:) But normally Encoding.Default will be used that depends on the hacker. If he likes Japanese code pages he can set them on the system and will be used by mcs. The second case is only a fallback. And I think using a simple SBCS latin code page is better. Kornél - Original Message - From: Atsushi Eno [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel mailing list mono-devel-list@lists.ximian.com Sent: Monday, August 22, 2005 11:13 AM Subject: Re: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding Hi, I think using 1252 as a fallback is better than UTF-8 as it is a regular single-byte code page. UTF-8 should be detected (and I think it is detected) using byte order marks anyway. I agree that using 28591 as the default encoding is is a bad decission. This guess is Western centric ;-) Neither 1252 nor 28591 is regular code page. For example, almost all Japanese text editors does not support iso-8859-1 in save as... feature (usually, only shift_jis (932/ANSI), iso-2022-jp (50221) and euc-jp (50932) are supported). I assume this situation is common to other Asian nations. (Thus Japanese hackers were reluctant to edit such files on which someone wrote only-iso-8859-1 letters.) UTF-8 should be detected but cannot be done perfectly (automatic encoding detection is not always possible) and actually we don't support further auto detection than BOM lookup (csc seems to handle them fine). This could be fixed but in reality it's not working. So I think using utf-8 as the default would make better sense. What about using Encoding.Default instead of CultureInfo.CurrentCulture.TextInfo.ANSICodePage as it is really based on system code page? Yeah, I'd change them as such. Atsushi Eno ___ 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] Re: slowdown with USE_MUNMAP
On 8/21/05, Michal Moskal [EMAIL PROTECTED] wrote:
After some investigation I've managed to create a simple C testcase
(as lupus suggested). It seems that -DUSE_MUNMAP makes garbage collection
to be called twice as many times, -DUSE_MMAP
doesn't seem to affect that. The question is: is it normal? How can it
be avoided?
Lupus suggested I test the following patch:
Index: allchblk.c
===
--- allchblk.c (revision 48620)
+++ allchblk.c (working copy)
@@ -589,7 +589,7 @@
USED_HEAP_SIZE = GC_requested_heapsize
!TRUE_INCREMENTAL GC_should_collect()) {
# ifdef USE_MUNMAP
- continue;
+ // continue;
# else
/* If we have enough large blocks left to cover any */
/* previous request for large blocks, we go ahead */
It indeed helped -- the speed is back to normal, but the memory usage
is as without MUNMAP.
The question is now -- is it safe to remove this continue?
--
Michal Moskal,
http://nemerle.org/~malekith/
___
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-devel-list] mcs patch for default encoding
Hi again,
Agreed. In fact, I was also fixing bug #75065, maybe duplicate.
I have a fix for UTF8Encoding, but it uncovered another mcs bug
which does not handle files with BOM with specific encoding.
To summarize the situation:
- Currently driver.cs does not process source files with
default encoding.
- UTF8Encoding.cs does not handle U+FEFF correctly.
- When we fix UTF8Encoding.cs to handle U+FEFF, it starts
to reject some source files which has BOM.
(CS8025:Parsing error)
- Even if we fix driver.cs to let StreamReader consider BOM
(currently we disable it), there are still some files
borking.
Am digging into this bug in depth. Hopefully I'll post a set of
fixes later.
... and now I finished the fixes as was done in the attached patch:
- driver.cs :
a) uses Encoding.Default for the default input.
b) Always use true for detecting BOM at any time.
- support.cs : Handle preamble_size precisely.
- UTF8Encoding.cs : it should not skip U+FEFF. This fixes
bug #73086 and #75065.
They should be applied at a time, except for a).
Atsushi Eno
Index: mcs/driver.cs
===
--- mcs/driver.cs (revision 48630)
+++ mcs/driver.cs (working copy)
@@ -91,16 +91,11 @@
static DateTime last_time, first_time;
//
- // Encoding: ISO-Latin1 is 28591
+ // Encoding.
//
static Encoding encoding;
- //
- // Whether the user has specified a different encoder manually
- //
- static bool using_default_encoder = true;
-
static public void Reset ()
{
want_debugging_support = false;
@@ -114,7 +109,6 @@
defines = null;
output_file = null;
encoding = null;
- using_default_encoder = true;
first_source = null;
}
@@ -158,7 +152,7 @@
}
using (input){
- SeekableStreamReader reader = new
SeekableStreamReader (input, encoding, using_default_encoder);
+ SeekableStreamReader reader = new
SeekableStreamReader (input, encoding, true);
Tokenizer lexer = new Tokenizer (reader, file,
defines);
int token, tokens = 0, errors = 0;
@@ -186,7 +180,7 @@
return;
}
- SeekableStreamReader reader = new SeekableStreamReader
(input, encoding, using_default_encoder);
+ SeekableStreamReader reader = new SeekableStreamReader
(input, encoding, true);
// Check 'MZ' header
if (reader.Read () == 77 reader.Read () == 90) {
@@ -1308,21 +1302,15 @@
if (value == utf8){
encoding = new UTF8Encoding();
- using_default_encoder = false;
return true;
}
if (value == reset){
- //
- // 28591 is the code page for
ISO-8859-1 encoding.
- //
- cp = 28591;
- using_default_encoder = true;
+ cp = Encoding.Default.CodePage;
}
try {
cp = Int32.Parse (value);
encoding = Encoding.GetEncoding (cp);
- using_default_encoder = false;
} catch {
Report.Error (2016, Code page `{0}' is
invalid or not installed, value);
}
@@ -1373,13 +1361,8 @@
int i;
bool parsing_options = true;
- try {
- encoding = Encoding.GetEncoding (28591);
- } catch {
- Console.WriteLine (Error: could not load
encoding 28591, trying 1252);
- encoding = Encoding.GetEncoding (1252);
- }
-
+ encoding = Encoding.Default;
+
references = new ArrayList ();
soft_references = new ArrayList ();
modules = new ArrayList ();
Index:
Re: [Mono-dev] gtk-sharp bootstrap vs. bootstrap-2.4
On Monday 22 August 2005 02:28, Paul F. Johnson wrote: Hi, I'm further confused by this information: http://www.all-the-johnsons.co.uk/mono/mono-compiling.html The build process for gtk-sharp is different to the other modules in mono. Instead of ./autogen.sh, there is the choice of ./bootstrap and ./bootstrap-2.4. The only difference is if you're using the bleeding edge version, you should use the 2.4 version. gtk-sharp comes in two flavours. One is designed for the stable mono, the other for those using the developer branch (and now a third for the clinically insane by the looks of it!). bootstrap is for stable, bootstrap-2.4 is for the developers version. At least, that's how I understand it. After staring at the configure.in.in for a while, I came up with the idea of trying to look at what it's looking at, so I hacked up a bit of bash: GNOME_LIST=libgnomecanvas-2.0 libgnomeui-2.0 gtk+-2.0 libgnomeprintui-2.2 gmodule-2.0 libpanelapplet-2.0 echo gnome-sharp for p in $GNOME_LIST; do echo -n $p=; pkg-config --modversion $p; done echo rsvg-sharp pkg-config --modversion librsvg-2.0 echo vte-sharp pkg-config --modversion vte ## That (and grep) lead me to look at the bootstrap files: ## ./bootstrap #!/bin/sh # Run this to set configure.in up for an API version. GTK_SHARP_VERSION=2.5.90 ASSEMBLY_VERSION=2.6.0.0 GTK_REQUIRED_VERSION=2.6.0 GNOME_REQUIRED_VERSION=2.10.0 VERSIONCSDEFINES=-define:GTK_SHARP_2_6 VERSIONCFLAGS=-DGTK_SHARP_2_6 GTK_API_TAG=2.6 GNOME_API_TAG=2.10 . ./bootstrap-generic $@ ## ./bootstrap-2,4 #!/bin/sh # Run this to set configure.in up for an API version. GTK_SHARP_VERSION=2.3.90 ASSEMBLY_VERSION=2.4.0.0 GTK_REQUIRED_VERSION=2.4.0 GNOME_REQUIRED_VERSION=2.6.0 VERSIONCSDEFINES= VERSIONCFLAGS= GTK_API_TAG=2.4 GNOME_API_TAG=2.6 . ./bootstrap-generic $@ It would appear you were given some bad info at some point, or things have changed. -- Regards, Steven ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] cannot create regular file `/.../vbnet.lang': Permission [correctly] denied
When I ./autogen.sh --prefix=$MONO_HOME \ make make install for gtksourceview-sharp I get an error message saying: test -z /opt/gnome/share/gtksourceview-1.0/language-specs || mkdir -p -- /opt/gnome/share/gtksourceview-1.0/language-specs /usr/bin/install -c -m 644 'nemerle.lang' '/opt/gnome/share/gtksourceview-1.0/language-specs/nemerle.lang' /usr/bin/install: cannot create regular file `/opt/gnome/share/gtksourceview-1.0/language-specs/nemerle.lang': Permission denied /usr/bin/install -c -m 644 'vbnet.lang' '/opt/gnome/share/gtksourceview-1.0/language-specs/vbnet.lang' /usr/bin/install: cannot create regular file `/opt/gnome/share/gtksourceview-1.0/language-specs/vbnet.lang': Permission denied make[2]: *** [install-extra_langDATA] Error 1 make[2]: Leaving directory `/download/org/go-mono/gtksourceview-sharp' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/download/org/go-mono/gtksourceview-sharp' make: *** [install-recursive] Error 1 And that is exactly what should happen when an install script tries to write to a system directory! $MONO_HOME is where I said to put the results of the build process. How do I report this bug? -- Regards, Steven ___ 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-devel-list] mcs patch for default encoding
In this case there is no need to provide a fallback case in mcs as well.:) Kornél - Original Message - From: Atsushi Eno [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel mailing list mono-devel-list@lists.ximian.com Sent: Monday, August 22, 2005 12:15 PM Subject: Re: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding Hi, Ok, then now I'll stop pushing shift_jis as the default (well, I didn't ;-) and just use Encoding.Default. BTW if it falls back to unsupported case, then this property returns UTF8. Atsushi Eno Kornél Pál wrote: 1252 is far from Hungarian as well altough I think not as far as from Japanese.:) But normally Encoding.Default will be used that depends on the hacker. If he likes Japanese code pages he can set them on the system and will be used by mcs. The second case is only a fallback. And I think using a simple SBCS latin code page is better. Kornél - Original Message - From: Atsushi Eno [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel mailing list mono-devel-list@lists.ximian.com Sent: Monday, August 22, 2005 11:13 AM Subject: Re: [Mono-dev] Re: [Mono-devel-list] mcs patch for default encoding Hi, I think using 1252 as a fallback is better than UTF-8 as it is a regular single-byte code page. UTF-8 should be detected (and I think it is detected) using byte order marks anyway. I agree that using 28591 as the default encoding is is a bad decission. This guess is Western centric ;-) Neither 1252 nor 28591 is regular code page. For example, almost all Japanese text editors does not support iso-8859-1 in save as... feature (usually, only shift_jis (932/ANSI), iso-2022-jp (50221) and euc-jp (50932) are supported). I assume this situation is common to other Asian nations. (Thus Japanese hackers were reluctant to edit such files on which someone wrote only-iso-8859-1 letters.) UTF-8 should be detected but cannot be done perfectly (automatic encoding detection is not always possible) and actually we don't support further auto detection than BOM lookup (csc seems to handle them fine). This could be fixed but in reality it's not working. So I think using utf-8 as the default would make better sense. What about using Encoding.Default instead of CultureInfo.CurrentCulture.TextInfo.ANSICodePage as it is really based on system code page? Yeah, I'd change them as such. Atsushi Eno ___ 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] patches for RegionInfo support
Hi,
You are misinterpreting CurrentRegion.
CurrentRegion is no way related to CurrentCulture.
Well, I didn't think CurrentRegion is not in sync with CurrentCulture
(as I explicitly commented in RegionInfo.cs), but yeah the previous
code was still incorrect that treated possibly different region
than CultureInfo.BootstrapCultureID.
RegionInfo.CurrentRegion:
http://msdn2.microsoft.com/library/7kcxkdc9(en-us,vs.80).aspx
The documentation describes the actual behaviour of CurrentRegion (I have
done some tests):
The value is AppDomain scoped (in other words stored in a static filed). A
single instance is constructed at the first call to CurrentRegion then a
Hrm, it sounds true:
using System;
using System.Globalization;
using System.Threading;
public class Test
{
static RegionInfo staticRegion;
public static void Main ()
{
RegionInfo r = RegionInfo.CurrentRegion;
Console.WriteLine (r);
Thread.CurrentThread.CurrentCulture = new CultureInfo
(en-US);
r = RegionInfo.CurrentRegion;
Console.WriteLine (r);
staticRegion = RegionInfo.CurrentRegion;
Console.WriteLine (staticRegion ==
RegionInfo.CurrentRegion);
Thread t = new Thread (new ThreadStart (Another));
t.Start ();
}
static void Another ()
{
Console.WriteLine (staticRegion ==
RegionInfo.CurrentRegion);
}
}
cached value is retruned. On Windows this is based on the value selected in
Regional and Language Options. This is per-user setting on Windows and
can
be retrieved using GetUserDefaultLCID. You can change however this setting
(on Windows) without rebooting so the value may change. But it will have no
effect to CurrentRegion if it's already cached unless you call
CultureInfo.ClearCachedData.
OK. actually ClearCachedData() seems not working fine, so it should be
fixed anyways.
And CurrentRegion is read-only.
Yes, as there is no setter.
At the beginning I said that CurrentRegion is no way related to
CurrentCulture.. This is true but I don't know other OS' internals
regarding RegionInfo so using CultureInfo may be required but CurrentRegion
is an AppDomain scope cached value that will be refreshed only when calling
ClearCachedData. So CurrentCulture should not be used as it can be changed
but the default value for CurrentCulture can be used if it's required.
I think it would be OK just to be equal to what things are done on
Windows since no one uses it ;-)
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] gtk-sharp: Optional assemblies
Hi Steven, Configure is finding what parts of gtk# CAN be built. When doing 'make' after that, the ones it said 'yes' will be built into managed libraries that will DEPEND on the native libraries, so if you don't have them (the native ones) properly installed you WON'T be able to use the corresponding managed libraries anyway, so unless you intend to use applications that need them (like MonoDevelop) no prob leaving then out. Rephrasing it: it all depends on the applications you are planning to use or develop, with gtk#. They dictate what optional parts are needed. From the looks of it you seem not to support for some commonly used/usable pieces, like gtkhtml-sharp (needs an specific version of it, what complicates things a bit) that is used by the monodoc documentation browser (a version using mozilla's gecko is in the works) and therefore by the monodevelop IDE. Also gnome-sharp is commonly used... Monodevelop, from the top of my mind, also needs vte-sharp to be able to have an embedded console window. Hope it helps clarify things, On 8/22/05, Steven T. Hatton [EMAIL PROTECTED] wrote: I'm confuses as to what is meant by Optional assemblies in the gtk-sharp build. If I install the rpms for the listed assemblies, they will show as yes, but but I'm not sure what that means. Are they being built when I make gtk-sharp, or is something from the rpms being registered in or copied into the final product of the build process? I've had some conflict problems with some of these, and would rather not have anything non-essential installed. Configuration summary * Installation prefix = /home/hattons/opt/org/go-mono * C# compiler: /home/hattons/opt/org/go-mono/bin/mcs -define:GTK_SHARP_2_6 Optional assemblies included in the build: * art-sharp.dll: yes * gnomevfs-sharp.dll: no * gnome-sharp.dll: no * glade-sharp.dll: yes * rsvg-sharp.dll: no * gtkhtml-sharp.dll: no * vte-sharp.dll: no * gtk-dotnet.dll: yes NOTE: if any of the above say 'no' you may install the corresponding development packages for them, rerun autogen.sh to include them in the build. * Documentation build enabled: no Now type `make' to compile -- Regards, Steven ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Rafael Monoman Teixeira --- I'm trying to become a Rosh Gadol before my own eyes. See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment. It hurts! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Monodoc: Add contribution links to home page
Hi Mario, On 8/22/05, Mario Sopena [EMAIL PROTECTED] wrote: I'm thinking now in a method to delete contributions and I have two ideas: * a delete link at the home page * When you are editing a node, a new button called Restore * A new Menu entry that pops up a dialog showing a table with your contributions that lets you delete them and select which ones do you want to upload Which one do you think is better? All of them? I would like to have the last two. Rationales: Restore is less frightening than Delete, but it works better for changes than for additions so I feel the The dialog helps filter unintended or not ready contributions (either changes and additions). I the dialog you'd need to have a way to Restore/Delete unintended contributions and other to Select those to be uploaded, as they may yeld different sets. This dialog, or some other derived from it, may help also in navigating through the pending contributions (the ones not yet ready to be uploaded) as the work on them may span many sessions inside the documentation browser. Thanks for your hard work, -- Rafael Monoman Teixeira --- I'm trying to become a Rosh Gadol before my own eyes. See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment. It hurts! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] symlinks to lib/mono/gac/*/*/*.config all broken?
After building and installing mono to a non-system directory I find many broken symlinks. For example, from the root of the installation directory I find: for f in $(find . -type l); do test -e $f || ls $f; done ./lib/mono/1.0/System.Messaging.dll.config ./lib/mono/1.0/ByteFX.Data.dll.config ./lib/mono/1.0/Microsoft.VisualBasic.dll.mdb ./lib/mono/1.0/System.Data.OracleClient.dll.config ./lib/mono/1.0/System.Runtime.Remoting.dll.config ./lib/mono/1.0/I18N.Other.dll.config ./lib/mono/1.0/Mono.Data.Tds.dll.config ./lib/mono/1.0/System.Data.dll.config ./lib/mono/1.0/Mono.Data.dll.config ./lib/mono/1.0/Accessibility.dll.config ./lib/mono/1.0/Commons.Xml.Relaxng.dll.config ./lib/mono/1.0/Mono.Data.SybaseClient.dll.config ./lib/mono/1.0/Microsoft.JScript.dll.config ./lib/mono/1.0/PEAPI.dll.config ./lib/mono/1.0/System.ServiceProcess.dll.config ./lib/mono/1.0/System.Design.dll.config ./lib/mono/1.0/System.Windows.Forms.dll.config ... all of these are of the form: ./lib/mono/1.0/System.Messaging.dll.config - ../gac/System.Messaging/1.0.5000.0__b03f5f7f11d50a3a/System.Messaging.dll.config ./lib/mono/1.0/ByteFX.Data.dll.config - ../gac/ByteFX.Data/0.7.6.1__0738eb9f132ed756/ByteFX.Data.dll.config ./lib/mono/1.0/Microsoft.VisualBasic.dll.mdb - ../gac/Microsoft.VisualBasic/7.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.mdb ./lib/mono/1.0/System.Data.OracleClient.dll.config - ../gac/System.Data.OracleClient/1.0.5000.0__b77a5c561934e089/System.Data.OracleClient.dll.config ./lib/mono/1.0/System.Runtime.Remoting.dll.config - ../gac/System.Runtime.Remoting/1.0.5000.0__b77a5c561934e089/System.Runtime.Remoting.dll.config ./lib/mono/1.0/I18N.Other.dll.config - ../gac/I18N.Other/1.0.5000.0__0738eb9f132ed756/I18N.Other.dll.config ./lib/mono/1.0/Mono.Data.Tds.dll.config - ../gac/Mono.Data.Tds/1.0.5000.0__0738eb9f132ed756/Mono.Data.Tds.dll.config ./lib/mono/1.0/System.Data.dll.config - ../gac/System.Data/1.0.5000.0__b77a5c561934e089/System.Data.dll.config ./lib/mono/1.0/Mono.Data.dll.config - ../gac/Mono.Data/1.0.5000.0__0738eb9f132ed756/Mono.Data.dll.config ./lib/mono/1.0/Accessibility.dll.config - ../gac/Accessibility/1.0.5000.0__b03f5f7f11d50a3a/Accessibility.dll.config ./lib/mono/1.0/Commons.Xml.Relaxng.dll.config - ../gac/Commons.Xml.Relaxng/1.0.5000.0__0738eb9f132ed756/Commons.Xml.Relaxng.dll.config ./lib/mono/1.0/Mono.Data.SybaseClient.dll.config - ../gac/Mono.Data.SybaseClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SybaseClient.dll.config ./lib/mono/1.0/Microsoft.JScript.dll.config - ../gac/Microsoft.JScript/7.0.5000.0__b03f5f7f11d50a3a/Microsoft.JScript.dll.config ./lib/mono/1.0/PEAPI.dll.config - ../gac/PEAPI/1.0.5000.0__0738eb9f132ed756/PEAPI.dll.config ./lib/mono/1.0/System.ServiceProcess.dll.config - ../gac/System.ServiceProcess/1.0.5000.0__b03f5f7f11d50a3a/System.ServiceProcess.dll.config ./lib/mono/1.0/System.Design.dll.config - ../gac/System.Design/1.0.5000.0__b03f5f7f11d50a3a/System.Design.dll.config ./lib/mono/1.0/System.Windows.Forms.dll.config - ../gac/System.Windows.Forms/1.0.5000.0__b77a5c561934e089/System.Windows.Forms.dll.config ./lib/mono/1.0/System.Web.Services.dll.config - ../gac/System.Web.Services/1.0.5000.0__b03f5f7f11d50a3a/System.Web.Services.dll.config ./lib/mono/1.0/nunit.util.dll.config - ../gac/nunit.util/2.2.0.0__96d09a1eb7f44a77/nunit.util.dll.config ./lib/mono/1.0/System.EnterpriseServices.dll.config - ../gac/System.EnterpriseServices/1.0.5000.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll.config What does this signify? How do I fix it? -- Regards, Steven ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] cannot create regular file `/.../vbnet.lang': Permission [correctly] denied
On Mon, 2005-08-22 at 06:32 -0400, Steven T. Hatton wrote: /usr/bin/install: cannot create regular file `/opt/gnome/share/gtksourceview-1.0/language-specs/vbnet.lang': Permission denied make[2]: *** [install-extra_langDATA] Error 1 make[2]: Leaving directory `/download/org/go-mono/gtksourceview-sharp' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/download/org/go-mono/gtksourceview-sharp' make: *** [install-recursive] Error 1 IMHO, we should not install these files. Any modern gtksourceview-sharp package will have them (post GNOME 2.6 maybe, though I think nld has a patch). Or maybe we should not make this issue cause the build to fail. Luckily, the newer gtksourceview packages are going to use XDG_DATA_DIRS or something similar so that we don't have to deal with this issue. Sadly though, that is for the GNOME 2.12 timeframe. -- Ben ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Default value fixes for WebControl, + UnitConverter infinite loop fix
On Fri, 2005-08-19 at 15:08 +0100, Michael Hutchinson wrote:
Some corrected default values for the properties of
System.Web.UI.WebControls.WebControl.
There's also a fix for a potential infinite loop in UnitConverter that
occurs when converting to/from non-string types.
Could someone review this, and if ther are no objections I'll commit it.
Please, do.
On a related note, I am uncomfortable with the constructor for
System.ComponentModel.DefaultValueAttribute.cs
public DefaultValueAttribute (Type type, string value)
{
try {
TypeConverter converter = TypeDescriptor.GetConverter (type);
DefaultValue = converter.ConvertFromString (null,
CultureInfo.InvariantCulture, value);
} catch { }
}
It should not be swallowing exceptions; if there are any, then the
dveloper has given the DefaultValueAttribute a bad value. However, I'm
reluctant to suggest changing this right now in case it breaks
anything.
That code fixed a bug report. I don't remember if we added a test case
for it or not...
-Gonzalo
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Jit for ARM
The ARM port is underway, but only lupus (Paolo Molaro) can tell you the status of it. :) On 8/22/05, Jose Pascual [EMAIL PROTECTED] wrote: Hi there, How to compiling mono/mini, mcs, et all from the scratch for ARM? I'd like to test mini for ARM I have a debian woking in my ARM920T based board . good job!!! best regards ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Rafael Monoman Teixeira --- I'm trying to become a Rosh Gadol before my own eyes. See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment. It hurts! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] ** ERROR **: pending init System.Net.DnsPermission
Hi all. This is first time to post my question on this mailing list. I'm very excited to learn .NET implementation other than Windows. I'm now testing CAS on Mono. I tried to apply policy to AppDomain. But When 'PolicyLevel policy = PolicyLevel.CreateAppDomainLevel();' is called, it always generate following error. ** ERROR **: pending init System.Net.DnsPermission It seems there is an error in the initialization process of policy. Anyone know why this happens? Sang-Min Park Department of Computer Science Schol of Engineering and Applied Sciences University of Virginia, Charlottesville, VA 235 Olsson Hall 434-825-7295 (Private cell phone) [EMAIL PROTECTED] www.cs.virginia.edu/~sp2kn * ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] ANOTHER ERROR :( Mono Compile Error in Solaris 8
Hey guys, I luckily have gotten most the errors worked out thanks to Zoltan on this mailing list. Anybody have any idea why I am getting this error. I would really appreciate an email if you did. Thanks so much! if test -w ../mcs; then :; else chmod -R +w ../mcs; fi d=`pwd`; cd ../mcs make PROFILES='default net_2_0' all-profiles make: Fatal error in reader: Makefile, line 2: Unexpected end of line seen Current working directory /export/home/users/niteesh/mono/mono-1.1.8.3/mcs *** Error code 1 make: Fatal error: Command failed for target `all-local' Current working directory /export/home/users/niteesh/mono/mono-1.1.8.3/runtime *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /export/home/users/niteesh/mono/mono-1.1.8.3 *** Error code 1 make: Fatal error: Command failed for target `all' ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] System.DirectoryServices text encoding
I've been working with Novell.Directory and System.DirectoryServices quite a bit recently. I was wondering about the seemingly arbitrary UTF-8 encoding that is going on in there. Is UTF-8 the only Unicode text encoding used by LDAP text based attributes in the spec? -JD Conley ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] symlinks to lib/mono/gac/*/*/*.config all broken?
On Monday 22 August 2005 09:21, Steven T. Hatton wrote: After building and installing mono to a non-system directory I find many broken symlinks. For example, from the root of the installation directory I find: for f in $(find . -type l); do test -e $f || ls $f; done ./lib/mono/1.0/System.Messaging.dll.config [...] ... all of these are of the form: ./lib/mono/1.0/System.Messaging.dll.config - ../gac/System.Messaging/1.0.5000.0__b03f5f7f11d50a3a/System.Messaging.dll.c onfig ./lib/mono/1.0/ByteFX.Data.dll.config - ../gac/ByteFX.Data/0.7.6.1__0738eb9f132ed756/ByteFX.Data.dll.config ./lib/mono/1.0/Microsoft.VisualBasic.dll.mdb - [...] The same thing happened when I used the default installation location and su -c 'make install'. BTW, make uninstall doesn't. -- Regards, Steven ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Patch] AssemblyName ctor
Hey Paolo, We have mono_assembly_name_parse, which receives a MonoString* and a MonoAssemblyName*. The problem I find is that every time a System.Reflection.AssemblyName were created using the described ctor, we should also create a MonoAssemblyName (not needed). With the managed ctor, we also avoid calling the internal call. What do you think? Carlos. El sáb, 20-08-2005 a las 12:27 +0200, Paolo Molaro escribió: On 08/19/05 Carlos Alberto Cortez wrote: The patch attached implements the new AssemblyName ctor without using internal calls. Could anybody review it? And the advantage of this is? The runtime needs and does have a function to do the parsing of the string, so just use an icall to use that. lupus ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: HOPEFULLY LAST ERROR: [Mono-dev] Mono Compile Error in Solaris 8
hey guys! I got past that error by installing a new version of gmake on solaris 8. I am still getting this error, and it seems like the makefile i using bad arguments for mcs. If anybody can tell me where the error is, I would greatley appreciate it!! make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' usage: mcs [-cdpVz] [-a string] [-n name] file ... make[6]: *** [build/deps/basic-profile-check.exe] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' *** The compiler 'mcs' doesn't appear to be usable. *** Falling back to using pre-compiled binaries. Be warned, this may not work. make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local//share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' Creating ../build/deps/basic_mcs.exe.makefrag ... make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ../jay/jay -ctv ../jay/skeleton.cs cs-parser.jay jay-tmp.out mv jay-tmp.out cs-parser.cs /bin/sh: ../jay/jay: not found make[6]: *** [cs-parser.cs] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ./mcs/cs-parser.cs: No such file or directory make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local//share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3' *** Error code 2 make: Fatal error: Command failed for target `all' On 8/20/05, Niteesh Bharara [EMAIL PROTECTED] wrote: ahh.. worked wonders! found ar and included it in my path. thanks! I have a few more errors now though! :( I have glib 2.6.2 installed from sunfreeware and I am getting the following error log when I compile mono. It goes on longer then I have pasted. I pasted teh beginning, and then I pasted what it has in the end. If anybody can help me I would really really appreciate it! Thanks again for all your help! -- if /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../mono -I../../libgc/include -threads -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__
Re: HOPEFULLY LAST ERROR: [Mono-dev] Mono Compile Error in Solaris 8
Hi, You have some program on your system which has the same name as mcs, our C# compiler. Remove it from the system, or at least from your PATH. Zoltan On 8/22/05, Nit Bha [EMAIL PROTECTED] wrote: hey guys! I got past that error by installing a new version of gmake on solaris 8. I am still getting this error, and it seems like the makefile i using bad arguments for mcs. If anybody can tell me where the error is, I would greatley appreciate it!! make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' usage: mcs [-cdpVz] [-a string] [-n name] file ... make[6]: *** [build/deps/basic-profile-check.exe] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' *** The compiler 'mcs' doesn't appear to be usable. *** Falling back to using pre-compiled binaries. Be warned, this may not work. make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local//share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' Creating ../build/deps/basic_mcs.exe.makefrag ... make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ../jay/jay -ctv ../jay/skeleton.cs cs-parser.jay jay-tmp.out mv jay-tmp.out cs-parser.cs /bin/sh: ../jay/jay: not found make[6]: *** [cs-parser.cs] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ./mcs/cs-parser.cs: No such file or directory make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local//share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3' *** Error code 2 make: Fatal error: Command failed for target `all' On 8/20/05, Niteesh Bharara [EMAIL PROTECTED] wrote: ahh.. worked wonders! found ar and included it in my path. thanks! I have a few more errors now though! :( I have glib 2.6.2 installed from sunfreeware and I am getting the following error log when I compile mono. It goes on longer then I have pasted. I pasted teh beginning, and then I pasted what it has in the end. If anybody can help me I would really really appreciate it! Thanks again for all your help! -- if /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
Re: [Mono-dev] ThreadAbortException during compilation path
On Tue, 2005-08-16 at 20:04 +0400, Vorobiev Maksim wrote: Vorobiev Maksim Your patch is in svn HEAD now. Thanks. -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Error building mono from SVN
Hello: I'm having the same problem when building the latest mono from svn as described here: http://lists.ximian.com/pipermail/mono-devel-list/2005-August/013928.html http://lists.ximian.com/pipermail/mono-devel-list/2005-August/013646.html (I'm using ubuntu hoary, it's a fresh install) Any way to solve it and get mono build ok ??? -- Best regards Carlos Guzmán Álvarez Vigo-Spain ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
RE: [Mono-dev] Error building mono from SVN
I installed mono via binaries (in place of monolite). Everything built ok after that. - Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Guzmán Álvarez Sent: Monday, August 22, 2005 4:37 PM To: mono-devel-list@lists.ximian.com Subject: [Mono-dev] Error building mono from SVN Hello: I'm having the same problem when building the latest mono from svn as described here: http://lists.ximian.com/pipermail/mono-devel-list/2005-August/013928.html http://lists.ximian.com/pipermail/mono-devel-list/2005-August/013646.html (I'm using ubuntu hoary, it's a fresh install) Any way to solve it and get mono build ok ??? -- Best regards Carlos Guzmán Álvarez Vigo-Spain ___ 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] Error building mono from SVN
Hello: I installed mono via binaries (in place of monolite). Everything built ok after that. That is what i was trying to avoid , but, if there are no other way i will do that as well, thanks very much. -- Best regards Carlos Guzmán Álvarez Vigo-Spain ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] The Bleeding Edge of SuSE is not Mono-friendly
Hello, I've discovered that many of my problems with building and running Mono were related to having the SuSE bleeding edge bits for Gnome installed. After the lattest rpms were uploaded to the ftp server (and installed here) things really fell apart due to inconsistent Cairo version dependencies. I rolled back to the stock SuSE 9.3 bits and things are going much better. This is probably caused by a non-perfect configure script and our own copy of Cairo. We are working on a solution, but it might take a few weeks. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: HOPEFULLY LAST ERROR: [Mono-dev] Mono Compile Error in Solaris 8
Hey!! Thanks for your help! I have another error though.. :( I took that out of my path and removed the binary mcs (some other file), and reran the make, and now I am getting the line to change to the following: make[6]: execvp: mcs: Permission denied The whole error log is at the bottom of this email. I removed mcs, and it is no longer in my path. I see something similar: http://bugzilla.ximian.com/show_bug.cgi?id=74280 but I don't know how to fix it. I have . in myat PATH. Thanks for your help! Please email me if you have any thoughts, I really appreciate all your help! hopefully this is the last error msg I get.. Thanks again!! make[2]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' if test -w ../mcs; then :; else chmod -R +w ../mcs; fi d=`pwd`; cd ../mcs make PROFILES='default net_2_0' all-profiles make[3]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make profile-do--default--all profile-do--net_2_0--all make[4]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make PROFILE=basic all make[5]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[6]: execvp: mcs: Permission denied make[6]: *** [build/deps/basic-profile-check.exe] Error 127 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' *** The compiler 'mcs' doesn't appear to be usable. *** Falling back to using pre-compiled binaries. Be warned, this may not work. make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local/share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ../jay/jay -ctv ../jay/skeleton.cs cs-parser.jay jay-tmp.out mv jay-tmp.out cs-parser.cs /bin/sh: ../jay/jay: not found make[6]: *** [cs-parser.cs] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ./mcs/cs-parser.cs: No such file or directory make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local/share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3' *** Error code 2 make: Fatal error: Command failed for target `all' ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: HOPEFULLY LAST ERROR: [Mono-dev] Mono Compile Error in Solaris 8
Besides the whole mcs issue, it looks like your C compiler is messed up. As the error message says, Installation problem, cannot exec 'cc1'. I'd make sure your compiler is set up correctly. Maybe see if you can use GCC to compile Mono. Peter On Mon, 2005-08-22 at 17:06 -0500, Nit Bha wrote: Hey!! Thanks for your help! I have another error though.. :( I took that out of my path and removed the binary mcs (some other file), and reran the make, and now I am getting the line to change to the following: make[6]: execvp: mcs: Permission denied The whole error log is at the bottom of this email. I removed mcs, and it is no longer in my path. I see something similar: http://bugzilla.ximian.com/show_bug.cgi?id=74280 but I don't know how to fix it. I have . in myat PATH. Thanks for your help! Please email me if you have any thoughts, I really appreciate all your help! hopefully this is the last error msg I get.. Thanks again!! make[2]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' if test -w ../mcs; then :; else chmod -R +w ../mcs; fi d=`pwd`; cd ../mcs make PROFILES='default net_2_0' all-profiles make[3]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make profile-do--default--all profile-do--net_2_0--all make[4]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make PROFILE=basic all make[5]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[6]: execvp: mcs: Permission denied make[6]: *** [build/deps/basic-profile-check.exe] Error 127 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' *** The compiler 'mcs' doesn't appear to be usable. *** Falling back to using pre-compiled binaries. Be warned, this may not work. make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local/share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ../jay/jay -ctv ../jay/skeleton.cs cs-parser.jay jay-tmp.out mv jay-tmp.out cs-parser.cs /bin/sh: ../jay/jay: not found make[6]: *** [cs-parser.cs] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/mcs' ./mcs/cs-parser.cs: No such file or directory make[6]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make all-local make[7]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' cc -DSKEL_DIRECTORY=\/usr/local/share/jay\ -g -O2 -c -o closure.o closure.c command line:1:1: warning: __GNUC__ redefined built-in:2:1: warning: this is the location of the previous definition command line:2:1: warning: __GNUC_MINOR__ redefined built-in:3:1: warning: this is the location of the previous definition command line:16:12: warning: system re-asserted command line:17:12: warning: system re-asserted command line:20:10: warning: cpu re-asserted command line:21:14: warning: machine re-asserted cpp: -lang-c: linker input file unused because linking not done cc: installation problem, cannot exec `cc1': No such file or directory make[7]: *** [closure.o] Error 1 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[6]: *** [do-all] Error 2 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/jay' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory
Re: ERROR AGAIN :(: [Mono-dev] Mono Compile Error in Solaris 8
Hey Peter! Yep, that was the error. I just reupdated cc to 3.4.2 instead of 2.9.5, and now its going again. But just got another error, care to take a look. I had gcc installed that was 3.4.2 earlier, but for soem reason 2.9.5 cc was still there.. Anyway this is the new error, and I have no clue what its doing here. make[8]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' ../../jay/jay -ct ../../jay/skeleton.cs System.Xml.XPath/Parser.jay System.Xml.XPath/Parser.cs ../../jay/jay: 21 rules never reduced ../../jay/jay: 1 shift/reduce conflict, 42 reduce/reduce conflicts. sed s/\%start Expr/\%start Pattern/ System.Xml.XPath/Parser.jay Mono.Xml.Xsl/PatternParser.jay echo #define XSLT_PATTERN Mono.Xml.Xsl/PatternParser.cs ../../jay/jay -ct Mono.Xml.Xsl/PatternParser.jay ../../jay/skeleton.cs Mono.Xml.Xsl/PatternParser. cs ../../jay/jay: 3 rules never reduced ../../jay/jay: 1 shift/reduce conflict, 46 reduce/reduce conflicts. echo #define XSLT_PATTERN Mono.Xml.Xsl/PatternTokenizer.cs cat System.Xml.XPath/Tokenizer.cs Mono.Xml.Xsl/PatternTokenizer.cs MONO_PATH=../../class/lib/basic:$MONO_PATH /export/home/users/niteesh/mono/mono-1.1.8.3/runtime/mono -wrapper ../../class/lib/basic/mcs.exe -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB -debug /noco nfig /lib:/usr/local/lib /noconfig /unsafe /r:mscorlib.dll /r:System.dll /nowarn:0162 /nowarn:0618 /no warn:0612 /target:library /out:System.Xml.dll System.Xml.XPath/Parser.cs Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs @System.Xml.dll.sources Unhandled Exception: System.Security.Cryptography.CryptographicException: Couldn't access random sourc e. in 0x00060 System.Security.Cryptography.RNGCryptoServiceProvider:Check () in 0x00034 System.Security.Cryptography.RNGCryptoServiceProvider:.ctor () in 0x000b0 System.Guid:FastNewGuidArray () in 0x0008c System.Reflection.Emit.ModuleBuilder:.ctor (System.Reflection.Emit.AssemblyBuilder assb, System.String name, System.String fullyqname, Boolean emitSymbolInfo, Boolean transient) in 0x000d8 System.Reflection.Emit.AssemblyBuilder:DefineDynamicModule (System.String name, System.St ring fileName, Boolean emitSymbolInfo, Boolean transient) in 0x00020 System.Reflection.Emit.AssemblyBuilder:DefineDynamicModule (System.String name, System.St ring fileName, Boolean emitSymbolInfo) in 0x00450 Mono.CSharp.CodeGen:Init (System.String name, System.String output, Boolean want_debuggin g_support) in 0x00a5c Mono.CSharp.Driver:MainDriver (System.String[] args) in 0xc Mono.CSharp.Driver:Main (System.String[] args) make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 1 make[8]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' make[7]: *** [do-all] Error 2 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3' make: *** [all] Error 2 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: ERROR AGAIN :(: [Mono-dev] Mono Compile Error in Solaris 8
This means that the Mono runtime couldn't set up the random number generator. On Linux systems, I believe this works by reading from the special device files /dev/random or /dev/urandom; maybe on Solaris they aren't readable by nonprivileged users. Probably the runtime needs to be taught how to get random bytes from Solaris. Peter On Mon, 2005-08-22 at 17:42 -0500, Nit Bha wrote: Hey Peter! Yep, that was the error. I just reupdated cc to 3.4.2 instead of 2.9.5, and now its going again. But just got another error, care to take a look. I had gcc installed that was 3.4.2 earlier, but for soem reason 2.9.5 cc was still there.. Anyway this is the new error, and I have no clue what its doing here. make[8]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' ../../jay/jay -ct ../../jay/skeleton.cs System.Xml.XPath/Parser.jay System.Xml.XPath/Parser.cs ../../jay/jay: 21 rules never reduced ../../jay/jay: 1 shift/reduce conflict, 42 reduce/reduce conflicts. sed s/\%start Expr/\%start Pattern/ System.Xml.XPath/Parser.jay Mono.Xml.Xsl/PatternParser.jay echo #define XSLT_PATTERN Mono.Xml.Xsl/PatternParser.cs ../../jay/jay -ct Mono.Xml.Xsl/PatternParser.jay ../../jay/skeleton.cs Mono.Xml.Xsl/PatternParser. cs ../../jay/jay: 3 rules never reduced ../../jay/jay: 1 shift/reduce conflict, 46 reduce/reduce conflicts. echo #define XSLT_PATTERN Mono.Xml.Xsl/PatternTokenizer.cs cat System.Xml.XPath/Tokenizer.cs Mono.Xml.Xsl/PatternTokenizer.cs MONO_PATH=../../class/lib/basic:$MONO_PATH /export/home/users/niteesh/mono/mono-1.1.8.3/runtime/mono -wrapper ../../class/lib/basic/mcs.exe -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB -debug /noco nfig /lib:/usr/local/lib /noconfig /unsafe /r:mscorlib.dll /r:System.dll /nowarn:0162 /nowarn:0618 /no warn:0612 /target:library /out:System.Xml.dll System.Xml.XPath/Parser.cs Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs @System.Xml.dll.sources Unhandled Exception: System.Security.Cryptography.CryptographicException: Couldn't access random sourc e. in 0x00060 System.Security.Cryptography.RNGCryptoServiceProvider:Check () in 0x00034 System.Security.Cryptography.RNGCryptoServiceProvider:.ctor () in 0x000b0 System.Guid:FastNewGuidArray () in 0x0008c System.Reflection.Emit.ModuleBuilder:.ctor (System.Reflection.Emit.AssemblyBuilder assb, System.String name, System.String fullyqname, Boolean emitSymbolInfo, Boolean transient) in 0x000d8 System.Reflection.Emit.AssemblyBuilder:DefineDynamicModule (System.String name, System.St ring fileName, Boolean emitSymbolInfo, Boolean transient) in 0x00020 System.Reflection.Emit.AssemblyBuilder:DefineDynamicModule (System.String name, System.St ring fileName, Boolean emitSymbolInfo) in 0x00450 Mono.CSharp.CodeGen:Init (System.String name, System.String output, Boolean want_debuggin g_support) in 0x00a5c Mono.CSharp.Driver:MainDriver (System.String[] args) in 0xc Mono.CSharp.Driver:Main (System.String[] args) make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 1 make[8]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' make[7]: *** [do-all] Error 2 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3' make: *** [all] Error 2 -- Peter Williams [EMAIL PROTECTED] [Ninjas] are cool; and by cool, I mean totally sweet. -- REAL Ultimate Power ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: ERROR AGAIN :(: [Mono-dev] Mono Compile Error in Solaris 8
ahh! I bet I have to install egd or prngd for solaris. I don't think we have /dev/ranom or /dev/urandom here. Let me try it out! I bet thats it. Do you know how much is left in the compile? sigh.. :) hopefully i'll get through this.. :) hehe. On 8/22/05, Peter Williams [EMAIL PROTECTED] wrote: This means that the Mono runtime couldn't set up the random number generator. On Linux systems, I believe this works by reading from the special device files /dev/random or /dev/urandom; maybe on Solaris they aren't readable by nonprivileged users. Probably the runtime needs to be taught how to get random bytes from Solaris. Peter On Mon, 2005-08-22 at 17:42 -0500, Nit Bha wrote: Hey Peter! Yep, that was the error. I just reupdated cc to 3.4.2 instead of 2.9.5, and now its going again. But just got another error, care to take a look. I had gcc installed that was 3.4.2 earlier, but for soem reason 2.9.5 cc was still there.. Anyway this is the new error, and I have no clue what its doing here. make[8]: Entering directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' ../../jay/jay -ct ../../jay/skeleton.cs System.Xml.XPath/Parser.jay System.Xml.XPath/Parser.cs ../../jay/jay: 21 rules never reduced ../../jay/jay: 1 shift/reduce conflict, 42 reduce/reduce conflicts. sed s/\%start Expr/\%start Pattern/ System.Xml.XPath/Parser.jay Mono.Xml.Xsl/PatternParser.jay echo #define XSLT_PATTERN Mono.Xml.Xsl/PatternParser.cs ../../jay/jay -ct Mono.Xml.Xsl/PatternParser.jay ../../jay/skeleton.cs Mono.Xml.Xsl/PatternParser. cs ../../jay/jay: 3 rules never reduced ../../jay/jay: 1 shift/reduce conflict, 46 reduce/reduce conflicts. echo #define XSLT_PATTERN Mono.Xml.Xsl/PatternTokenizer.cs cat System.Xml.XPath/Tokenizer.cs Mono.Xml.Xsl/PatternTokenizer.cs MONO_PATH=../../class/lib/basic:$MONO_PATH /export/home/users/niteesh/mono/mono-1.1.8.3/runtime/mono -wrapper ../../class/lib/basic/mcs.exe -d:NET_1_1 -d:ONLY_1_1 -d:BOOTSTRAP_WITH_OLDLIB -debug /noco nfig /lib:/usr/local/lib /noconfig /unsafe /r:mscorlib.dll /r:System.dll /nowarn:0162 /nowarn:0618 /no warn:0612 /target:library /out:System.Xml.dll System.Xml.XPath/Parser.cs Mono.Xml.Xsl/PatternParser.cs Mono.Xml.Xsl/PatternTokenizer.cs @System.Xml.dll.sources Unhandled Exception: System.Security.Cryptography.CryptographicException: Couldn't access random sourc e. in 0x00060 System.Security.Cryptography.RNGCryptoServiceProvider:Check () in 0x00034 System.Security.Cryptography.RNGCryptoServiceProvider:.ctor () in 0x000b0 System.Guid:FastNewGuidArray () in 0x0008c System.Reflection.Emit.ModuleBuilder:.ctor (System.Reflection.Emit.AssemblyBuilder assb, System.String name, System.String fullyqname, Boolean emitSymbolInfo, Boolean transient) in 0x000d8 System.Reflection.Emit.AssemblyBuilder:DefineDynamicModule (System.String name, System.St ring fileName, Boolean emitSymbolInfo, Boolean transient) in 0x00020 System.Reflection.Emit.AssemblyBuilder:DefineDynamicModule (System.String name, System.St ring fileName, Boolean emitSymbolInfo) in 0x00450 Mono.CSharp.CodeGen:Init (System.String name, System.String output, Boolean want_debuggin g_support) in 0x00a5c Mono.CSharp.Driver:MainDriver (System.String[] args) in 0xc Mono.CSharp.Driver:Main (System.String[] args) make[8]: *** [../../class/lib/basic/System.Xml.dll] Error 1 make[8]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' make[7]: *** [do-all] Error 2 make[7]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class/System.XML' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs/class' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[4]: *** [profile-do--basic--all] Error 2 make[4]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/users/niteesh/mono/mono-1.1.8.3' make: *** [all] Error 2 -- Peter Williams [EMAIL PROTECTED] [Ninjas] are cool; and by cool, I mean totally sweet. -- REAL Ultimate Power ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Unhandled Exceptions in Novell.Directory.Ldap and other Synchronization Issues
Novell.Directory.Ldap spawns threads for various queued operations. However, it appears as though there is no catch all exception handler in Connection+ReaderThread:Run() (or other spawned threads either). If anything other than an IO exception is thrown the thread will exit without notifying the consumer, and in Beta 2 this causes the application to terminate. In my current application it causes a search timeout. One such example is as follows (this is received some time during connecting, binding, or doing a search -- I'm not exactly sure): Unhandled Exception: System.ArgumentException: length in 0x004a3 System.Array:Copy (System.Array sourceArray, Int32 sourceIndex, System.Array destinationArray, Int32 destinationIndex, Int32 length) in 0x0004f System.Array:Copy (System.Array sourceArray, System.Array destinationArray, Int32 length) in 0x00016 System.Collections.ArrayList:CopyTo (System.Array array) in 0x0002a System.Collections.ArrayList:ToArray () in 0x0004a Novell.Directory.Ldap.MessageVector:findMessageById (Int32 msgId) in 0x001b7 Novell.Directory.Ldap.Connection+ReaderThread:Run () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () This exception looks very strange at first glance. An invalid length on an ArrayList:ToArray() just doesn't compute. After further investigation I have found that the MessageVector class is only partially synchronized. Synchronization happens on the findMessageById() and some other functions that do iteration, but the atomic Add, Remove, and Contains operations are not protected. It appears as though the findMessageById is being called while messages are being added to or removed from the MessageVector in another thread. It is possible that I am the first to notice this since I am currently doing LDAP queries through a VPN tunnel over an internet connection. Messages coming back from the server have a tendency to trickle in relatively slowly. So, do I submit patches to this group, or through a different Novell forum? Is anybody actively working on this subsystem in such a way that we might have to merge a lot of work? -JD Conley ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] gtk-sharp bootstrap vs. bootstrap-2.4
Hi, Things have changed and documentation hasn't been updated. I'll need to update my website then - can't have duff info on an unoffical board now can we? ;-p I've updated the monoupdater script to take these changes into account automagically if anyone is interested... TTFN Paul -- A lot of football success is in the mind. You must believe you are the best and then make sure that you are. In my time at Liverpool we always said we had the best two teams on Merseyside, Liverpool and Liverpool Reserves. - Bill Shankly ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Unhandled Exceptions in Novell.Directory.Ldap and other Synchronization Issues
I don't know ?? On 8/22/05, JD Conley [EMAIL PROTECTED] wrote: Please submit any bug reports for the LdapCsharp library to Novell Forge at: http://forge.novell.com/modules/xfmod/tracker/?group_id=1318atid=1362 No problem. Does this library regularly get replicated into the Mono SVN repository? I'd obviously like to see any fixes put in the Mono tree. -JD -- Robbie the Nanobot says: Only YOU can prevent gray goo (NEVER release nanobot assemblers without replication limiting code) http://lizardslounge.org ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Make install on Solaris 8
Hey guys, I am running make install after a successful compile, but the problem is it keeps failing, and saying install-sh not found. I keep having to copy install-sh to every directory, and then continuing, and it'll run through. Is there a reason for this? I have install-sh in my root mono dir and thats all (before I have copied it to a few other places). Anybody know whats going on? Thanks again for ALL the help you guys have provided me!!! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
