We're looking into this issue. You should never get the "pseudo: You must set
the PSEUDO_PREFIX environment variable to run pseudo." message. This means
something appears to have avoided the wrappers.
I'll let you know once we figure out something.
--Mark
On 2/17/12 9:35 AM, Paul Eggleton wrote:
Hi all,
I'm trying to extend buildhistory to write out the metadata revisions just
before it does the commit to the buildhistory repository, and I'm having some
pseudo-related trouble. The structure is a little unusual, in that the
execution flow is an event handler that calls a shell function (via
bb.build.exec_func()) and during parsing this function an ${@...} reference to
a python function is evaluated, which then calls os.popen(), at which point I
get the error "pseudo: You must set the PSEUDO_PREFIX environment variable to
run pseudo."
I don't need pseudo at this stage. I've tried setting PSEUDO_DISABLED=1 and
even PSEUDO_UNLOAD=1 just prior to the os.popen() call (or within it) and
despite evidence that pseudo is taking notice of these being set in other
contexts (when the function is called from elsewhere) even when doing this I
still get the error above. I could rearrange the structure to avoid this
execution flow however that would bar me from reusing existing code that we
have for getting the metadata revision.
Any suggestions?
Cheers,
Paul
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
