Le Lundi, 17 Mars 2003, � 02:32 Australia/Melbourne, Jean Richelle a �crit :
Hi all,
I'm trying to compile kdevelop but it fails ( cf end of compilation msgs).
Any idea of what to do to solve that ?
Regards,
Jean
scriptingpart.cpp:131: syntax error before `<<' token
scriptingpart.cpp:133: `guiDocument' was not declared in this scope
scriptingpart.cpp:133: warning: ISO C++ forbids declaration of `setDOMDocument'
with no type
scriptingpart.cpp:135: `Py_None' was not declared in this scope
scriptingpart.cpp:135: warning: ISO C++ forbids declaration of `Py_INCREF' with
no type
scriptingpart.cpp:136: parse error before `return'
scriptingpart.cpp:141: syntax error before `*' token
scriptingpart.cpp: In member function `void ScriptingPart::slotScriptAction()':
scriptingpart.cpp:153: `kdDebug' cannot be used as a function
scriptingpart.cpp:155: `PyObject' undeclared (first use this function)
scriptingpart.cpp:155: `arglist' undeclared (first use this function)
scriptingpart.cpp:155: `Py_BuildValue' undeclared (first use this function)
scriptingpart.cpp:156: `actions' undeclared (first use this function)
scriptingpart.cpp:156: `PyEval_CallObject' undeclared (first use this function)
scriptingpart.cpp: At global scope:
scriptingpart.cpp:162: syntax error before `*' token
scriptingpart.cpp:166: syntax error before `*' token
scriptingpart.cpp:172: `kdevelopc_appId' was not declared in this scope
scriptingpart.cpp:172: `METH_VARARGS' was not declared in this scope
scriptingpart.cpp:173: `kdevelopc_addMenuItem' was not declared in this scope
scriptingpart.cpp:173: `METH_VARARGS' was not declared in this scope
scriptingpart.cpp:175: array size missing in `kdevelopc_methods'
scriptingpart.cpp:175: storage size of `kdevelopc_methods' isn't known
scriptingpart.cpp:171: storage size of `kdevelopc_methods' isn't known
scriptingpart.cpp: In function `void initkdevelopc()':
scriptingpart.cpp:179: `Py_InitModule' undeclared (first use this function)
scriptingpart.cpp: At global scope:
scriptingpart.cpp:181: parse error before `}' token
make[3]: *** [scriptingpart.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
### execution of /var/tmp/tmp.0.e4OCVQ failed, exit code 2
Failed: compiling kdevelop-3.0a3-2 failed
My knowledge of makefiles is almost non-existent. My familiarity with compile errors like these ones, is great however, I get them all the time in my own programs. Some syntactic element ( probably one that begins or ends a block, like a brace or semicolon ) is missing ( around line 130 I would guess ) and so thrown the parser off, giving rise to errors on lines which are themselves correct.
In my case, the cause of this is usually an error in the file itself, less often, it's an error in an included file, an incorrectly expanded macro, or an error in the application of a patch. With the complicated magic that surrounds the patching and configuration of source files in Fink, it's cause is probably something less obvious than any of these things, but if you email the file, and the headers that it includes, I'd happily look over them.
I'm still very new to fink, so I'm not too hopeful that this will yield a constructive solution, but I'd be happy to try. Send the source file and appropriate headers from ${prefix}/src/kdevelop-3.0a3-2/... as these are the ones which have been patched, the versions in the source tar ball haven't been, and thus wouldn't tell us much.
Yours,
Daniel Wyeth.
------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
