Armin Steinhoff <A-Steinhoff@web_.de> wrote:
Graeme Peterson wrote:
Mario Charest <mcharest@void_zinformatic.com> wrote:
“Armin Steinhoff” <A-Steinhoff@web_.de> wrote in message
news:3A3F5D8D.4C08BA59@web_.de…
Hello,
I just compiled an C extension for Python 2.0 for
QNX RTP.
from ./gtkmodule.c:39:
/usr/local/include/gtk/gtkitemfactory.h:48:
warning: function declaration isn’t a prototype
./gtkmodule.c:6611: VERSION' undeclared here (not in a unction) ./gtkmodule.c:6611: initializer element is not constant ./gtkmodule.c:6611: (near initialization for functions.pygtkVersion') ./gtkmodule.c:6647: warning: function declaration isn't a prototype cc: error 33 make[1]: *** [gtkmodule.o] Error 1 make[1]: Leaving directory /root/Python-2.0/Modules’
→ what means the error message ‘cc: error 33’ ???
( sounds like route 66 > 
I beleive it’s an internal error. I got this one time, but when I remove
the previous error/warning it went away.
‘cc’ is passing along the exit value of gcc,
Only a nitty gritty detail … I was using ‘qcc’
not ‘cc’. Seems so that some error messages should
be cleaned up >
cc is a symlink to qcc:
$ which -laf cc
-rwxrwxr-x 1 root 120 30724 Oct 13 06:28 /usr/bin/qcc
and from the comments above main() in gcc:
" Exit code is 35 if can’t open files, 34 if fatal error,
33 if had non fatal errors, else success."
OK … but why stops ‘qcc’ with the error code 33
??
So we are seeing a non-fatal error that is preventing completion of
the build. As suggested, remove the earlier errors/warnings and
it should go away.
OK … I have to check out the source of that
warnings.
Many thanks so far.
Armin
Regardless of the exact source of the errno 33, there are clear
understandable errors that precede the errno 33, and these need
to be dealt with. Once they are, then the errno 33 will go away.
GP