Re: bzip2-full-native_1.0.5.bb problem and possible fix

[Vitus Jensen <vjensen@gmx.de>]

Am Mon, 16 Feb 2009 16:59:09 +0300 schrieb Roman I Khimov:

> GNUtoo:
>> I've:
>> >| cp: will not overwrite just-created
>>
>> `/home/embedded/oetmp_openmoko/work/i686-linux/bzip2-full-native-1.0.5-
r0
>>/bzip2-1.0.5/install-sh' with
>> `/home/embedded/oetmp_openmoko/staging/i686-linux/usr/share/
automake-1.9/
>>install-sh'
> 
> Most probably you've worked with automake 1.9, then switched to automake
> 1.10 (or reverse way) and got two automakes in staging directory, then
> this:
> 
>> cp ${STAGING_DATADIR_NATIVE}/automake*/install-sh ${S}/
> 
> which should expand as (for example)
> 
> cp ${STAGING_DATADIR_NATIVE}/automake-1.10/install-sh ${S}/
> 
> expands as
> 
> cp ${STAGING_DATADIR_NATIVE}/automake-1.10/install-sh \
> 	${STAGING_DATADIR_NATIVE}/automake-1.9/install-sh ${S}/
> 
> Boom.
> 
> Had this on automake switch too, not sure how to fix it better, but it's
> not a problem when you only use one automake (and you can clean up stale
> version manually if you switched from one version to another).

http://bugs.openembedded.net/show_bug.cgi?id=4911

It's the issue described there, right?  I had this problem once but it 
mysteriously went away.  Probably after wiping TMPDIR but "bitbake bzip2 -
c clean" would have been enough?

Vitus

-- 
Vitus Jensen, Hannover, Germany, Earth, Milky Way, Universe (current)