Re: [Muine] can't compile latest cvs / 0.6.0
- From: Matthias Debus <psic4t netbands de>
- To: muine-list gnome org
- Subject: Re: [Muine] can't compile latest cvs / 0.6.0
- Date: Wed, 5 May 2004 18:58:39 +0200 (CEST)
On Wed, 05 May 2004 17:41:36 +0100, Lee Willis wrote:
> Have you also upgraded mono? The Gtk# update shouldn't have any impact
> on building the wsdl file?
Yup, I've done so:
[psic4t c0re - ~/grafik+sound/muine]$ rpm -qa | grep -e mono -e gtk-sharp
mono-0.91-1mdk
libmono0-0.91-1mdk
libmono0-devel-0.91-1mdk
mono-config-0.31-1mdk
gtk-sharp-0.91.1-1mdk
libmono-runtime-0.91-1mdk
> You might like to check Pete Johanson's earlier mail today "Fix for
> pinvoke ..." and see if that helps.
I tried this but with no luck:
make[2]: Entering directory `/home/psic4t/grafik+sound/muine/src'
wsdl ./AmazonSearchService.wsdl
Mono Web Services Description Language Utility
Writing file 'AmazonSearchService.cs'
System.InvalidOperationException: Process has not been started.
in <0x0003b> System.Diagnostics.Process:get_ExitCode ()
in <0x00050> (wrapper remoting-invoke-with-check)
System.Diagnostics.Process:get_ExitCode ()
in <0x00239> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFileBatch
(System.CodeDom.Compiler.CompilerParameters,string[],bool)
in <0x00055> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFile
(System.CodeDom.Compiler.CompilerParameters,string)
in <0x0051c>
System.Xml.Serialization.XmlSerializer:RunSerializerGenerationAux (object)
in <0x0001b>
System.Xml.Serialization.XmlSerializer:RunSerializerGeneration (object)
make[2]: *** [AmazonSearchService.cs] Segmentation fault
make[2]: *** Datei »AmazonSearchService.cs« wird gelöscht
make[2]: Leaving directory `/home/psic4t/grafik+sound/muine/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/psic4t/grafik+sound/muine'
make: *** [all] Fehler 2
> I don't have an upgraded system handy so can't dig further at this
> point, but it *looks* like either:
>
> a) A trashed wapi is causing problems, try removing ~/.wapi and trying
> again
Have done so, same result as in my first post.
> b) There's a mono bug in the most recent release
Don't know this.
> c) We have a bug somewhere
Don't know this either. :)
> Can you confirm that doing (a) doesn't help, and what mono version
> you're running so we can see if (b) is a possibility
Seems, that b) is the problem.
> Thanks
Greets, Matthias.
--
Public Key ID: 0x8078B10C
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]