On 01/28/07 R. Tyler Ballance wrote: > >>But that gets me building. I'm working through why my Dumbarton- > >>based $PROJECT[ no longer...runs on 1.2.3, but here's the error: > >> > >>2007-01-26 15:29:56.811 $PROJECT[14970] Compress Assembly Path: / > >>Software/Perforce/user/tyler/$PROJECT[_(Network)/build/Debug/ > >>$PROJECT[.app/Contents/Libraries/Compress.dll > >> > >>** ERROR **: runtime invoke called on uninitialized runtime > >>aborting... > >>Stacktrace: [...] > After rebuilding my Dumbarton.framework against the 1.2.3 preview I > had installed, the SIGABRT went away. I'm somewhat curious as to if > there is an issue with the embedded API in 1.2.2 being incompatible > with 1.2.3, and if that was causing the issue.
There is no incompatibility between the 1.2.2 and 1.2.3 embedded API. Since you mentioned you messed with your installation of mono, I wouldn't be surprised if you broke your compilation environment: you likely linked to two different versions of mono at the same time. > It is certainly not an issue to switch development to using 1.2.3 > instead of the 1.2.2 release, but something seems awry in the > Dumbarton linked against 1.2.2 would break completely for 1.2.3; did > some API change deep in the runtime, or are all embedded projects > subject to breakage on point releases? Just curious so I don't hit > this issue again. The fact that you're the only one having messed up his system and having compilation issues should be telling you that this is not a problem in mono, but on your box. The embedded API has remained compatible since the 1.0 mono days. lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
