Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Koen Kooi <k.kooi@student.utwente.nl>]

On 07-04-09 20:49, Denys Dmytriyenko wrote:
> On Tue, Apr 07, 2009 at 08:16:16PM +0200, Koen Kooi wrote:
>> On 07-04-09 19:43, Denys Dmytriyenko wrote:
>>> if you don't have opkg in your system PATH, you may need to
>>> remove opkg packages from pstage to force rebuilding and installing it.
>>> Its a
>>> chicken and egg problem - opkg-native binary is in .ipk and in order to
>>> install and use it you need opkg-native...
>>
>> That's not true:
>>
>> PSTAGE_PKGMANAGER = "stage-manager-ipkg"
>>
>> [..]
>>
>>      pkgmanager = bb.which(path, 'opkg-cl')
>>      if pkgmanager == "":
>>          pkgmanager = bb.which(path, 'ipkg-cl')
>>      if pkgmanager != "":
>>          bb.data.setVar("PSTAGE_PKGMANAGER", pkgmanager, d)
>>
>>
>> stage-manager-ipkg is a shell script (flashback to the original ipkg
>> implementation), which will get used till opkg-cl is found in $PATH.
>
> Hmm, good to know - thanks! I wonder why it doesn't always work, as reported
> on irc? The workaround so far was to delete the opkg package from pstage...

The script doesn't work too well, but it gets the job done. Maybe try 
'bitbake opkg-native' before trying a build from 'scratch'. It would be 
good to debug this.

regards,

Koen