Bug 4629 - Change of DISTRO_VERSION breaks nativesdk recipes
Summary: Change of DISTRO_VERSION breaks nativesdk recipes
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.4
Hardware: x86 x86_64
: Medium normal
Target Milestone: 1.4.2
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-06-07 22:32 UTC by Felipe Ferreri Tonello
Modified: 2013-10-18 16:28 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Felipe Ferreri Tonello 2013-06-07 22:32:53 UTC 
I already had built a meta-toolchain which works fine. Later when I change the DISTRO_VERSION value and try to build the same meta-toolchain, most of the nativesdk recipes breaks at the install step. It tries to install into the previous DISTRO_VERSION value.

One output example:
...
| /bin/grep: /home/buildbot/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux/opt/poky/0.5/sysroots/x86_64-pokysdk-linux/usr/lib/libXau.la: No such file or directory
| /home/buildbot/build/tmp/sysroots/x86_64-linux//bin/sed: can't read /home/buildbot/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux/opt/poky/0.5/sysroots/x86_64-pokysdk-linux/usr/lib/libXau.la: No such file or directory
| x86_64-pokysdk-linux-libtool: link: `/home/buildbot/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux/opt/poky/0.5/sysroots/x86_64-pokysdk-linux/usr/lib/libXau.la' is not a valid libtool archive
...

old DISTRO_VERSION = "0.5"
new DISTRO_VERSION = "0.5.2"
Comment 1 Robert Yang 2013-08-29 06:37:50 UTC 
I can't reproduce it on current master branch (1.5), it is not applicable of 1.5, maybe 1.4 ?
Comment 2 Felipe Ferreri Tonello 2013-08-29 18:06:54 UTC 
(In reply to comment #1)
> I can't reproduce it on current master branch (1.5), it is not applicable of
> 1.5, maybe 1.4 ?

On yocto 1.4 that happens. I didn't test master branch (1.5) tough.
Comment 3 Jessica 2013-09-03 20:29:29 UTC 
since not sure whether we'll have 1.4.3, mark this as 1.4.2 as it can't be reproduced for 1.5
Comment 4 Paul Eggleton 2013-10-18 16:28:16 UTC 
According to Richard it's the separate build directory changes that fix this, and these aren't really appropriate to be backported to 1.4, so I'm marking this as WONTFIX for 1.4.