[oe] Weird behaviour with PPP

[Aeschbacher, Fabrice]

> -----Ursprüngliche Nachricht-----
> Von: openembedded-devel-bounces at lists.openembedded.org 
> [mailto:openembedded-devel-bounces at lists.openembedded.org] Im 
> Auftrag von Mickael Chazaux
> Gesendet: Mittwoch, 23. Februar 2011 10:19
> An: openembedded-devel at lists.openembedded.org
> Betreff: Re: [oe] Weird behaviour with PPP
> 
> Hi,
> 
> 2011/2/22 Martin Jansa <martin.jansa at gmail.com>:
> > On Tue, Feb 22, 2011 at 07:24:28PM +0100, Andreas Oberritter wrote:
> >> Hi,
> >>
> >> On 02/22/2011 06:52 PM, Eric Benard wrote:
> >> > On 22/02/2011 18:22, Mickael Chazaux wrote:
> >> >> I have a hard time figuring out why bitbake seems to 
> mix versions of
> >> >> ppp... Any ideas?
> >> >>
> >> > strange, which distro, git tag, bitbake version are you using ?
> >> >
> >> > Both bitbake ppp-2.4.5 & bitbake -b
> >> > openembedded/recipes/ppp/ppp_2.4.5.bb work fine here 
> (angstrom 2008.1,
> >> > armv5 target, bitbake 1.12.0).
> >>
> >> I don't think this has anything to do with ppp. I faced 
> the same issue
> >> with a local recipe, of which an older version had been 
> built before.
> >> When packaging, the old version was used. A new workdir 
> was created for
> >> the old version during this step and the resulting 
> packages were empty.
> >> No recipe existed for this old version at that time, i.e. 
> PR had already
> >> been increased to 1.0, but 0.0 was used by bitbake.
> >>
> >> In the end, I deleted bitbake's cache and all files matching the
> >> package's name to get rid of the annoying problem. I think 
> there were
> >> pstage packages of the old version lying around.
> >
> > This wrong behavior is quite common ie after changing 
> PACKAGE_ARCH, see:
> > 
> http://www.mail-archive.com/openembedded-devel@lists.openembed
> ded.org/msg04280.html
> >
> As I often switch architectures (arm, x86) to work on different
> boards, should I use a different TMPDIR for each?

I am using one different TMPDIR for each MACHINE:
  build/mach1, build/mach2, ...

I still have to find a way to make two different machines with same arch (hence same cross-toolchain) share the same pstage, so that the toolchain does not get built twice

with kind regards,
Fabrice