[Mono-list] Mono 0.19 has been released

[John Duncan]

--Apple-Mail-1-391772789
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed

From: John Duncan <jddst19@mac.com>
Date: Mon Jan 20, 2003  11:30:22 PM US/Eastern
To: Benjamin Reed <ranger@befunk.com>
Subject: Re: [Mono-list] Mono 0.19 has been released

I'm not sure. Without a debugger you have to use a divide-and-conquer 
approach to find the cause of a problem. If the problem exists because 
of something funny going on in mcs, then identifying the build phase 
that causes it and what the data are is an approach to use. 
Unfortunately, I worry that some problems are caused by exceeding 
certain limits, and then accessing parts of the runtime that haven't 
been accessed before. These problems are much harder to find.

I suppose I should start working on this again. Is everyone using 
Jaguar? I'm still using 10.1. I'll let you all know about my experiences 
soon.

John
On Monday, January 20, 2003, at 11:07 PM, Benjamin Reed wrote:

> On Monday, January 20, 2003, at 09:42 PM, Miguel de Icaza wrote:
>
>> 	* MacOS patches:
>>
>> 		Paolo integrated John Duncan's and Benjamin Reed
>> 		patches to make Mono run on MacOS X out of the box.
>
> Well, i definitely get further this time around.  Mono builds and 
> appears to even run some.  Mint appears to still have problems building 
> mcs for me though:
>
> ---(snip!)---
> mcs /target:exe  -o mcs.exe AssemblyInfo.cs assign.cs attribute.cs 
> driver.cs cs-parser.cs cs-tokenizer.cs tree.cs location.cs cfold.cs 
> class.cs codegen.cs const.cs constant.cs decl.cs delegate.cs enum.cs 
> ecore.cs expression.cs genericparser.cs interface.cs literal.cs 
> modifiers.cs namespace.cs parameter.cs pending.cs report.cs 
> rootcontext.cs statement.cs support.cs typemanager.cs
>
> ** (/sw/bin/mcs.exe:10276): WARNING **: Using non-atomic functions!
> Illegal instruction
> make[1]: *** [mcs.exe] Error 132
> make: *** [all] Error 1
> ---(snip!)---
>
> How would I go about trying to find out what's actually going on here?
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list

--Apple-Mail-1-391772789
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
	charset=US-ASCII

<bold>From: </bold>John Duncan <<jddst19@mac.com>

<bold>Date: </bold>Mon Jan 20, 2003  11:30:22 PM US/Eastern

<bold>To: </bold>Benjamin Reed <<ranger@befunk.com>

<bold>Subject: </bold>Re: [Mono-list] Mono 0.19 has been released


I'm not sure. Without a debugger you have to use a divide-and-conquer
approach to find the cause of a problem. If the problem exists because
of something funny going on in mcs, then identifying the build phase
that causes it and what the data are is an approach to use.
Unfortunately, I worry that some problems are caused by exceeding
certain limits, and then accessing parts of the runtime that haven't
been accessed before. These problems are much harder to find.


I suppose I should start working on this again. Is everyone using
Jaguar? I'm still using 10.1. I'll let you all know about my
experiences soon.


John

On Monday, January 20, 2003, at 11:07 PM, Benjamin Reed wrote:


<excerpt>On Monday, January 20, 2003, at 09:42 PM, Miguel de Icaza
wrote:


<excerpt>	* MacOS patches:


		Paolo integrated John Duncan's and Benjamin Reed

		patches to make Mono run on MacOS X out of the box.

</excerpt>

Well, i definitely get further this time around.  Mono builds and
appears to even run some.  Mint appears to still have problems
building mcs for me though:


---(snip!)---

mcs /target:exe  -o mcs.exe AssemblyInfo.cs assign.cs attribute.cs
driver.cs cs-parser.cs cs-tokenizer.cs tree.cs location.cs cfold.cs
class.cs codegen.cs const.cs constant.cs decl.cs delegate.cs enum.cs
ecore.cs expression.cs genericparser.cs interface.cs literal.cs
modifiers.cs namespace.cs parameter.cs pending.cs report.cs
rootcontext.cs statement.cs support.cs typemanager.cs


** (/sw/bin/mcs.exe:10276): WARNING **: Using non-atomic functions!

Illegal instruction

make[1]: *** [mcs.exe] Error 132

make: *** [all] Error 1

---(snip!)---


How would I go about trying to find out what's actually going on here?



_______________________________________________

Mono-list maillist  -  Mono-list@ximian.com

http://lists.ximian.com/mailman/listinfo/mono-list

</excerpt>
--Apple-Mail-1-391772789--