Hi Stan,
----- Original Message -----
> From: "Nathan Scott" <nathans@xxxxxxxxxx>
> To: "Stan Cox" <scox@xxxxxxxxxx>
> Cc: pcp@xxxxxxxxxxx
> Sent: Friday, August 17, 2012 4:06:11 PM
> Subject: Re: python bindings
>
> ...
> setup and test scripts:
Just came across another issuee here - the setup script appears
to be making use of the pcp headers and libraries from the root.
This will have to (somehow? not clear from looking at it - maybe
that "ext_modules" Extension macro allows this?) make use of the
libraries and headers from the build if we're to have the python
code live within pcp. At build time, there may not be a local
root install of pcp, in which case the build will fail atm.
I came across this while I was helping someone with a fairly old
(patched) pcp build, which *did* have pcp in the root, but that
really old version was missing some macros...
pmapi.c: In function ‘initpmapi’:
pmapi.c:169:46: error: ‘PM_TYPE_EVENT’ undeclared (first use in this function)
pmapi.c:169:46: note: each undeclared identifier is reported only once for each
function it appears in
pmapi.c:197:52: error: ‘PM_EVENT_FLAG_POINT’ undeclared (first use in this
function)
pmapi.c:198:52: error: ‘PM_EVENT_FLAG_START’ undeclared (first use in this
function)
pmapi.c:199:52: error: ‘PM_EVENT_FLAG_END’ undeclared (first use in this
function)
pmapi.c:200:52: error: ‘PM_EVENT_FLAG_ID’ undeclared (first use in this
function)
pmapi.c:201:52: error: ‘PM_EVENT_FLAG_PARENT’ undeclared (first use in this
function)
pmapi.c:202:52: error: ‘PM_EVENT_FLAG_MISSED’ undeclared (first use in this
function)
pmapi.c:332:22: error: ‘PM_ERR_TYPE’ undeclared (first use in this function)
pmapi.c:334:22: error: ‘PM_ERR_THREAD’ undeclared (first use in this function)
pmapi.c:340:22: error: ‘PM_ERR_FAULT’ undeclared (first use in this function)
error: command 'gcc' failed with exit status 1
make[3]: *** [s-setup] Error 1
make[2]: *** [default_pcp] Error 2
make[1]: *** [default_pcp] Error 2
make: *** [built] Error 2
cheers.
--
Nathan
|