This looks like Gentoo, correct? We have a Gentoo platform in the PCP QA Farm and builds there are working fine, but we build outside emerge (we have not done that integration yet, 'cause no one in the PCP dev team understands how to do it) ...
I wonder where the options to configure are coming from?
In particular --without-threads is causing this problem. We always enable threads in all PCP builds, and although there is support for this being conditional, as you've seen, that is unfortunately busted in lock.c.
If you want a drop-in replacement for lock.c that fixes this issue, send me email and I'll forward it to you. But I'd strongly recommend the non-emerge build path (unless you'd like to help make the emerge build and packaging work ... nudge, nudge, wink, wink):
# unpack the src tarball $ cd to the root of the unpacked tarball $ ./Makeimages
this will leave a tarball of installable bits that you can extract as root by the following recipe (that can be found buried in qa/admin/pcp-daily) ...
# here=`pwd` # buildversion=4.3.1 # or whatever # tarball=$here/pcp-$buildversion/build/tar/pcp-[0-9]*[0-9].tar.gz # cd pcp-$buildversion/build/tar # ./preinstall # cd / # tar -zxpf $tarball # cd $here # cd pcp-$buildversion/build/tar ./postinstall