DEPLOY_DIR / packaged staging / persistent toolchains

DEPLOY_DIR / packaged staging / persistent toolchains

[Michael 'Mickey' Lauer]

Hi folks,

I just stumbled over something that surprises me. I have set DEPLOY_DIR 
outside TMP for a while (which works fine). Now when I remove the TMPDIR to 
start a new build from scratch, I can no longer build anything. Apparantly OE 
thinks I do no longer need a toolchain, since it does not attempt to built 
one. I need to remove the whole DEPLOY_DIR to be able to do any builds again.

Wasn't the idea of packaged staging to be able to keep core packages and the 
toolchain intact when removing TMPDIR? If I understodd this wrong, how can I 
do something like that these days? Would it be sufficient to set CROSS_DIR 
outside TMPDIR?

Cheers,

Mickey.

Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Denys Dmytriyenko]

On Tue, Apr 07, 2009 at 12:12:18PM +0200, Michael 'Mickey' Lauer wrote:
> Hi folks,
> 
> I just stumbled over something that surprises me. I have set DEPLOY_DIR 
> outside TMP for a while (which works fine). Now when I remove the TMPDIR to 
> start a new build from scratch, I can no longer build anything. Apparantly OE 
> thinks I do no longer need a toolchain, since it does not attempt to built 
> one. I need to remove the whole DEPLOY_DIR to be able to do any builds again.
> 
> Wasn't the idea of packaged staging to be able to keep core packages and the 
> toolchain intact when removing TMPDIR? If I understodd this wrong, how can I 
> do something like that these days? Would it be sufficient to set CROSS_DIR 
> outside TMPDIR?

Mickey,

Are you overwriting DEPLOY_DIR_PSTAGE from its default ${DEPLOY_DIR}/pstage?

Otherwise it should work and should populate CROSS_DIR from pstage. There is 
one little quirk - 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...

-- 
Denys

Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Koen Kooi]

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.

regards,

Koen

Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Denys Dmytriyenko]

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...

-- 
Denys

Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Koen Kooi]

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

Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Michael 'Mickey' Lauer]

Hi Denis,

> Are you overwriting DEPLOY_DIR_PSTAGE from its default
> ${DEPLOY_DIR}/pstage?

No, I didn't touch that.

> Otherwise it should work and should populate CROSS_DIR from pstage.

Ok, that simply doesn't happen here.

How can we debug this further.

:M:

Re: DEPLOY_DIR / packaged staging / persistent toolchains

[Denys Dmytriyenko]

On Wed, Apr 08, 2009 at 12:39:27AM +0200, Michael 'Mickey' Lauer wrote:
> Hi Denis,
> 
> > Are you overwriting DEPLOY_DIR_PSTAGE from its default
> > ${DEPLOY_DIR}/pstage?
> 
> No, I didn't touch that.
> 
> > Otherwise it should work and should populate CROSS_DIR from pstage.
> 
> Ok, that simply doesn't happen here.
> 
> How can we debug this further.

Hmm, Andrea has mentioned on irc, that the behavior may depend on whether the 
complete deploy directory is preserved or not... Need to experiment some more.

-- 
Denys