qtiplot failed to build

[Anatuss at gmx.net]

After cleaning qtiplot it started working without further errors.
But when I changed the scripting language from muparser (I reckon) to python qtiplot broke. ...
Fatal Python error: Interpreter not initialized (version mismatch?)
As mentioned before "which python -> epd" ... is there any way to change the language back (I've reinstalled qtiplot without success) ... or rather to make it work ...


-------- Original-Nachricht --------
> Datum: Sun, 17 May 2009 19:28:31 -0500
> Von: Ryan Schmidt <ryandesign at macports.org>
> An: Anatuss at gmx.net
> CC: MacPorts Users <macports-users at lists.macosforge.org>
> Betreff: Re: qtiplot failed to build

> On May 17, 2009, at 13:30, Anatuss at gmx.net wrote:
> 
> > I've read this thread. Yesterday I've upgraded macports with the  
> > result that the error has changed
> >
> > --->  Building qtiplot
> > Error: Target org.macports.build returned: shell command " cd "/opt/ 
> > local/var/macports/build/ 
> > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ 
> > qtiplot/work/qtiplot-0.9.7.6" && make all " returned error 2
> > Command output:       _release_Convolution in sipqtiConvolution.o
> >       _init_Convolution in sipqtiConvolution.o
> >       _meth_Deconvolution_timerEvent in sipqtiDeconvolution.o
> >       _meth_Deconvolution_childEvent in sipqtiDeconvolution.o
> >       _meth_Deconvolution_customEvent in sipqtiDeconvolution.o
> >       _meth_Deconvolution_connectNotify in sipqtiDeconvolution.o
> >       _meth_Deconvolution_disconnectNotify in sipqtiDeconvolution.o
> >       _meth_Deconvolution_setDataFromTable in sipqtiDeconvolution.o
> >       _meth_Deconvolution_run in sipqtiDeconvolution.o
> >       _release_Deconvolution in sipqtiDeconvolution.o
> >       _init_Deconvolution in sipqtiDeconvolution.o
> >   "_Py_CompileStringFlags", referenced from:
> >       PythonScript::compile(bool)  in PythonScript.o
> >       PythonScript::compile(bool)  in PythonScript.o
> >       PythonScript::compile(bool)  in PythonScript.o
> >       PythonScripting::exec(QString const&, _object*, char const*) 
> > in PythonScripting.o
> >       PythonScripting::eval(QString const&, _object*, char const*) 
> > in PythonScripting.o
> >   "_PyCObject_AsVoidPtr", referenced from:
> >       _initqti in sipqticmodule.o
> >   "_PyErr_ExceptionMatches", referenced from:
> >       PythonScript::eval()      in PythonScript.o
> >       PythonScript::eval()      in PythonScript.o
> >       PythonScript::eval()      in PythonScript.o
> >       PythonScript::eval()      in PythonScript.o
> >   "_PyCObject_Type", referenced from:
> >       _PyCObject_Type$non_lazy_ptr in sipqticmodule.o
> > ld: symbol(s) not found
> > collect2: ld returned 1 exit status
> > make[1]: *** [qtiplot.app/Contents/MacOS/qtiplot] Error 1
> > make: *** [sub-qtiplot-all] Error 2
> >
> > Error: Status 1 encountered during processing.
> 
> 
> You should clean qtiplot and try again with the debug switch, as it  
> doesn't look like we're seeing the first error below. (MacPorts only  
> outputs the last 30 lines or so of error messages, and here it looks  
> like the first error is farther back than that.)
> 
> sudo port clean qtiplot
> sudo port -d install qtiplat
> 
> 
> P.S: Use Reply All so your reply goes to the list too, not just to me.
> 
> 
> 

-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a