Hi Mark,
Any update on this one? I think we may need to track it in bugzilla.
Thanks,
Dongxiao
On Wed, 2012-03-14 at 17:02 +0800, Xu, Dongxiao wrote:
> Hi Mark,
>
> When using the new Hob to build targets, I also observed the pseudo
> output:
>
> "pseudo: You must set the PSEUDO_PREFIX environment variable to run
> pseudo."
>
> Here is the step to reproduce it:
>
> 1) source oe-init-build-env
> 2) hob
> 3) select machine and base image. Here I use qemux86 and
> core-image-minimal.
> 4) click "Just bake". For this first time build, pseudo works OK.
> 5) after the build finishes, return to image configuration page and
> click "Just bake" button again. Then after the build starts, pseudo will
> print out the above logs.
>
> Thanks,
> Dongxiao
>
> On Fri, 2012-02-17 at 10:50 -0800, Mark Hatle wrote:
> > 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
> > [email protected]
> > https://lists.yoctoproject.org/listinfo/yocto
>
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
