Getting pseudo from yocto/poky toolchain working with my build

Getting pseudo from yocto/poky toolchain working with my build

[O'donoghue, Bryan]

Greetings list.

Having a bit of an issue getting pseudo working when building poky-image-minimal @ poky-bernard-5.0.1

I'm running Debian 6.0.1. I've attempted to set up as many of the native packages as possible, to reduce compile time and I'm also using the yocto supplied gcc toolchain.

http://yoctoproject.org/downloads/yocto-1.0/toolchain/

root@wintermute# apt-get install sed wget cvs subversion git-core coreutils unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff git-core automake autoconf psyco quilt libtool gettext tcl sqlite3 libsqlite3-dev

I've installed /opt/poky/1.0/environment-setup-i586-poky-linux.
I've downloaded poky-bernard-5.0.1.tar.bz2 and extracted it to ~/Development/yocto

I do the following

1.

source poky-bernard-5.0.1/poky-init-build-env poky-5.0.1-build

2.

vim conf/local.conf

------------------------

INHERIT += rm_work

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"

CVS_PROXY_HOST = "http://aaa.bbb.com"
CVS_PROXY_PORT = "1984"


3.

deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ source /opt/poky/1.0/environment-setup-i586-poky-linux
deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ $CC -v
Using built-in specs.
COLLECT_GCC=i586-poky-linux-gcc
COLLECT_LTO_WRAPPER=/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.5.1/lto-wrapper
Target: i586-poky-linux

<snip>
Thread model: posix
gcc version 4.5.1 (GCC) 


4.

bitbake -v -k poky-image-minimal

5.

I'm having a bit of difficulty with pseudo in the build though. I've tried building pseudo - which chokes on sqlite3 - and then I thought it might be an idea to use the pseudo that comes with the toolchain provided on the website.

5a.

deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ which pseudo
/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin/pseudo


bitbake doesn't pick it up though

deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ bitbake -v -k poky-image-minimal
Pseudo is not present but is required, building this first before the main build

<snip>

NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and 0 failed.
/home/deckard/Development/yocto/poky-bernard-5.0.1/scripts/bitbake: line 55: /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/i686-linux/usr/bin/pseudo: No such file or directory


5b.

I try to set that explicitly by setting PSEUDOBINDIR

export PSEUDOBINDIR=/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin

Same error.


deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ export PSEUDOBINDIR=/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin
deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ bitbake -v -k poky-image-minimal
Pseudo is not present but is required, building this first before the main build
<snip>

/home/deckard/Development/yocto/poky-bernard-5.0.1/scripts/bitbake: line 55: /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/i686-linux/usr/bin/pseudo: No such file or directory

Is there a way to get bitbake to recognize the pseudo in /opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin/pseudo without modifying the bitbake script - or am I taking the wrong approach here ?

6.

I've tried building pseudo but, get errors with using sqlite3-native == /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/ as opposed to /usr/include/sqlite3.h - and errors with building sqlite3 of a different sort.


Is there a solution that's evading me here ?

My preference obviously is to use as many native packages as possible to reduce disk space, and cycles.

Any pointers appreciated.


Bryan
-------------------------------------------------------------
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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

[Richard Purdie]

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.

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

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

[Mark Hatle]

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

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

[Saul Wold]

Bryan,

Honestly this is not something we have tried, since we use the tools 
built during the bitbake process itself.  The tools generated for the
SDK are configured differently. I understand what you are trying to do here.

Have you tried a clean generic build, ie not using the 
environment-setup-i586* script or ASSUME_PROVIDED.

Did you look at the www.yoctoproject.org Quickstart Doc?  It looks like 
you might have.

Some additional comments below.

Sau!

On 06/28/2011 10:29 AM, O'donoghue, Bryan wrote:
> Greetings list.
>
> Having a bit of an issue getting pseudo working when building poky-image-minimal @ poky-bernard-5.0.1
>
> I'm running Debian 6.0.1. I've attempted to set up as many of the native packages as possible, to reduce compile time and I'm also using the yocto supplied gcc toolchain.
>
> http://yoctoproject.org/downloads/yocto-1.0/toolchain/
>
> root@wintermute# apt-get install sed wget cvs subversion git-core coreutils unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff git-core automake autoconf psyco quilt libtool gettext tcl sqlite3 libsqlite3-dev
>
> I've installed /opt/poky/1.0/environment-setup-i586-poky-linux.
> I've downloaded poky-bernard-5.0.1.tar.bz2 and extracted it to ~/Development/yocto
>
> I do the following
>
> 1.
>
> source poky-bernard-5.0.1/poky-init-build-env poky-5.0.1-build
>
> 2.
>
> vim conf/local.conf
>
> ------------------------
>
> INHERIT += rm_work
>
> 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"
>
> CVS_PROXY_HOST = "http://aaa.bbb.com"
> CVS_PROXY_PORT = "1984"
>
>
> 3.
>
> deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ source /opt/poky/1.0/environment-setup-i586-poky-linux
> deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ $CC -v
> Using built-in specs.
> COLLECT_GCC=i586-poky-linux-gcc
> COLLECT_LTO_WRAPPER=/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.5.1/lto-wrapper
> Target: i586-poky-linux
>
> <snip>
> Thread model: posix
> gcc version 4.5.1 (GCC)
>
>
> 4.
>
> bitbake -v -k poky-image-minimal
>
> 5.
>
> I'm having a bit of difficulty with pseudo in the build though. I've tried building pseudo - which chokes on sqlite3 - and then I thought it might be an idea to use the pseudo that comes with the toolchain provided on the website.
>

I would be good to get the failure information, my guess is that the 
host version of sqlite3 is not what psuedo needs, so it's failing
> 5a.
>
> deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ which pseudo
> /opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin/pseudo
>
>
> bitbake doesn't pick it up though
>
> deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ bitbake -v -k poky-image-minimal
> Pseudo is not present but is required, building this first before the main build
>
> <snip>
>
> NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and 0 failed.
> /home/deckard/Development/yocto/poky-bernard-5.0.1/scripts/bitbake: line 55: /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/i686-linux/usr/bin/pseudo: No such file or directory
>
There are some tests in bitbake for pseudo, I would be good to see your 
full log, to understand what tasks ran and did not run,
>
> 5b.
>
> I try to set that explicitly by setting PSEUDOBINDIR
>
> export PSEUDOBINDIR=/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin
>
> Same error.
>
>
> deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ export PSEUDOBINDIR=/opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin
> deckard@wintermute:~/Development/yocto/poky-5.0.1-build$ bitbake -v -k poky-image-minimal
> Pseudo is not present but is required, building this first before the main build
> <snip>
>
> /home/deckard/Development/yocto/poky-bernard-5.0.1/scripts/bitbake: line 55: /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/i686-linux/usr/bin/pseudo: No such file or directory
>
> Is there a way to get bitbake to recognize the pseudo in /opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin/pseudo without modifying the bitbake script - or am I taking the wrong approach here ?
>
> 6.
>
> I've tried building pseudo but, get errors with using sqlite3-native == /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/ as opposed to /usr/include/sqlite3.h - and errors with building sqlite3 of a different sort.
>
>
> Is there a solution that's evading me here ?
>
> My preference obviously is to use as many native packages as possible to reduce disk space, and cycles.
>
This is probably not possible, given the potential differences in 
configuration for what Yocto needs. This may have been possible with 
past releases, but as you discovered not at this point.


Sau!

> Any pointers appreciated.
>
>
> Bryan
> -------------------------------------------------------------
> Intel Ireland Limited (Branch)
> Collinstown Industrial Park, Leixlip, County Kildare, Ireland
> Registered Number: E902934
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

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

[O'donoghue, Bryan]

Saul, Richard.

Thanks for the suggestions re: building the whole thing from scratch.

In a previous life using openembedded our solutions for slow builds were an array of ASSUME_PROVIDEDs. I'll try the build the world approach instead !

Saul I'll send you along the logfiles off-list, one thing is that the build process looks for 

ASSUME_PROVIDED += "sqlite3-native"
/home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/i686-linux/usr/include/sqlite3.h
Instead of /usr/include/sqlite3.h !


Bryan

-------------------------------------------------------------
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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

[Richard Purdie]

On Wed, 2011-06-29 at 08:17 +0100, O'donoghue, Bryan wrote:
> Saul, Richard.
> 
> Thanks for the suggestions re: building the whole thing from scratch.
> 
> In a previous life using openembedded our solutions for slow builds
> were an array of ASSUME_PROVIDEDs. I'll try the build the world
> approach instead !

There is now sstate which is intended to try and assist this problem by
providing a cache of prebuilt entities that get reused if they're
compatible. Try giving that a try and I'm suspect you'll become a
convert! If you do run into problems let us know as its still one of the
newer features and we're interested in user feedback.

Cheers,

Richard

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

[Mark Hatle]

On 6/29/11 2:17 AM, O'donoghue, Bryan wrote:
> Saul, Richard.
> 
> Thanks for the suggestions re: building the whole thing from scratch.
> 
> In a previous life using openembedded our solutions for slow builds were an array of ASSUME_PROVIDEDs. I'll try the build the world approach instead !
> 
> Saul I'll send you along the logfiles off-list, one thing is that the build process looks for 
> 
> ASSUME_PROVIDED += "sqlite3-native"
> /home/deckard/Development/yocto/poky-5.0.1-build/tmp/sysroots/i686-linux/usr/include/sqlite3.h
> Instead of /usr/include/sqlite3.h !

I don't have time to implement/try this right now.. but one suggestion would be
to change the meta/recipes-devtools/pseudo/pseudo.inc so that the configure
calls pass the location of sqlite conditionally.  Currently it's using:

--with-sqlite=${STAGING_DIR_TARGET}${exec_prefix}

Simply checking for the existance of
${STAGING_DIR_TARGET}${include_prefix}/sqlite3.h and only passing --with-sqlite=
should be enough.  (it will fall back to the host otherwise.. and if the host
version is not sufficient it will error.)

--Mark

> 
> Bryan
> 
> -------------------------------------------------------------
> Intel Ireland Limited (Branch)
> Collinstown Industrial Park, Leixlip, County Kildare, Ireland
> Registered Number: E902934
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto