Re: Getting pseudo from yocto/poky toolchain working with my build

[Mark Hatle <mark.hatle@windriver.com>]

On 6/28/11 5:50 PM, Richard Purdie wrote:
> On Tue, 2011-06-28 at 18:29 +0100, O'donoghue, Bryan wrote:
>> ASSUME_PROVIDED += "m4-native tcl-native gettext-native libtool-native
>> quilt-native autoconf-native automake-native perl-native
>> sqlite3-native tar-replacement-native pseudo-native"
> 
> I don't know about the pseudo issue, the system really wasn't designed
> to allow for a system provided pseudo since few systems would actually
> have that.

pseudo is expected to be built for each build directory and each host system.
It's a VERY small binary so it should be quick... (you may be required to have
sqlite3 from the build though, the problem you have might simply be you can't
use the "host" version for pseudo.... this could be an enhancement request.)

We build pseudo for every host / build directory, because it has to learn the
system capabilities, and specifically the glibc capabilities in order to
determine what functions to intercept.  Unfortunately different versions of
glibc require slightly different intercepting code.

> I'm almost certain you're going to hit issues with the line above from
> perl-native, libtool-native and autoconf-native and automake-native
> though as you won't have key patches applied.
> 
> Cheers,
> 
> Richard
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto