Hi,
Are the files needed to build the RPMS available
for download?
Greets,
Matthijs ter Woord
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hi,
Now the patch is well designed as well. I support it.
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; Marek
Safar [EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 5:16
Hi,
I made a tiny patch for cs0642 warning (attached). It only fixes
if-else statement cases. Will continue to fix #66777.
I noticed that the use of EmptyStatement.Value hides the actual
location to report. Basically using singleton is harmful for
error reporting. Would it be bad idea if I
Hi Eno,
On Wed, Aug 24, 2005 at 3:12 pm, in message
[EMAIL PROTECTED],
Atsushi Eno [EMAIL PROTECTED] wrote:
I made a tiny patch for cs0642 warning (attached). It only fixes
if- else statement cases. Will continue to fix #66777.
I noticed that the use of EmptyStatement.Value hides the
Hi,
On Wed, Aug 24, 2005 at 1:57 pm, in message
[EMAIL PROTECTED], Kornél Pál
[EMAIL PROTECTED] wrote:
Currently a MonoVersion.cs file is generated by configure.in that contains a
AssemblyVersion attribute. I think it's a better solution to put a
MonoVersion contstant to Consts.cs and use
On Tue, 2005-08-23 at 08:32 -0400, Steven T. Hatton wrote:
For example, it's not clear how to
determine or control which libraries and assemblies are visible, or being
used by the currently running Mono or MCS.
Two flags control that: -r and -pkg.
By default, only mscorlib.dll and
We had asked the same answer before when we had fixes for
Novell.Directory.Ldap. What
is the official answer? How do we maintain sync with the Novel
sources?
I submitted a patch to the Novell Forge project last night, as it seems
like the root project. You can view it at:
Hi,
2005-06-24 Marek Safar [EMAIL PROTECTED]
* compiler-tester.cs: Enabled error/warning message checking.
I think we should never do such kind of check. It will mess
localization of compiler messages in the future. Or do we never
provide localized messages?
Atsushi Eno
Hello Eno,
2005-06-24 Marek Safar [EMAIL PROTECTED]
* compiler-tester.cs: Enabled error/warning message checking.
I think we should never do such kind of check. It will mess
localization of compiler messages in the future. Or do we never
provide localized messages?
I think it is
Hi Marek,
Marek Safar wrote:
Hello Eno,
2005-06-24 Marek Safar [EMAIL PROTECTED]
* compiler-tester.cs: Enabled error/warning message checking.
I think we should never do such kind of check. It will mess
localization of compiler messages in the future. Or do we never
provide
Hello,
2005-06-24 Marek Safar [EMAIL PROTECTED]
* compiler-tester.cs: Enabled error/warning message checking.
I think we should never do such kind of check. It will mess
localization of compiler messages in the future. Or do we never
provide localized messages?
I think it is
Fairly simple. Also a trivial fix to CreateComponentsCore to maintain
compatibility with .NET.
I've tested it works with some icons I whipped up for the Web Controls
in System.Web.dll, but I'd like to make them a bit prettier before
offering them too.
Any objections to me committing
Hello,
We had asked the same answer before when we had fixes for
Novell.Directory.Ldap. What
is the official answer? How do we maintain sync with the Novel sources?
This seems to be getting worse.
Novell.Ldap is a namespace that was contributed to us by the EDirectory
group, and since the
Hello,
I was wondering if there was any synchronization between
Novell.Directory.Ldap on Novell forge and Mono. I have noticed that the
trees are currently fairly different. I'm trying to make a decision on
which to patch, but I don't really know. I am leaning toward patching
the one on
I was wondering if there was any synchronization between
Novell.Directory.Ldap on Novell forge and Mono. I have noticed that
the
trees are currently fairly different. I'm trying to make a decision
on
which to patch, but I don't really know. I am leaning toward
patching
the one on Novell
Hi,
This is now fixed in SVN.
Zoltan
On 8/24/05, Gary M. Smithrud [EMAIL PROTECTED] wrote:
I'm attempting to get the 8/23 tarball to compile under Solaris 8 and
the function GC_thread_register_foriegn is undefined. I've checked for
incorrectly defined #if around
Thanks!! Very much appreciated!
Gary M. Smithrud
Haley Systems, Inc.
Phone: 724-934-7853
[EMAIL PROTECTED]
www.haley.com
Moving at the Speed of Change
-Original Message-
From: Zoltan Varga [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 2:15 PM
To: Gary M. Smithrud
Cc:
Hello,
I am starting to prepare the release notes for the upcoming Mono:
please send me privately the highlights of the contributions and changes
that you have done since the 1.1.8 release.
I forgot to mention: the release would happen in 2-3 weeks.
On Wed, 2005-08-24 at 09:12 -0700, Ynon Koralek wrote:
Hello,
This patch enables building (a part of) the framework in the java
profile (called net_1_1_java).
The java profile is using the standard .sources file. If there is a
.net_1_1_java.sources file, it's used instead.
For now, it
Hello,
Tomas is this fixed? Hari mentioned that it should be working now.
Miguel
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
I found a few problems with the linux mono installer preventing
libgdiplus from working.
The first is that $(INSTALL_PATH)/lib needs to be added to
$LD_LIBRARY_PATH. I attached a completly untested guess of a patch (I
dont have bitrock installed) that should hopefully solve this.. but
someone
21 matches
Mail list logo
