Bug 7950 - gcc-cross-canadian-i586 doesn't work PREFERRED_VERSION
Summary: gcc-cross-canadian-i586 doesn't work PREFERRED_VERSION
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.2 M4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-07-03 08:01 UTC by Robert Yang
Modified: 2016-09-12 11:03 UTC (History)
4 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 Robert Yang 2015-07-03 08:01:21 UTC 
Currently in oe-core, the default GCCVERSION is 4.9, and we also have
gcc 5.1, so when:

MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"


$ bitbake gcc-cross-canadian-i586

Then the 5.1 has been built, though we had set 4.9 in tcmode-default.inc:

PREFERRED_VERSION_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH} ?= "${GCCVERSION}"
Comment 1 Richard Purdie 2015-07-09 14:37:02 UTC 
Curious how you plan to fix this? I agree its an issue but the only way I've found to fix it properly is the noupdate_data changes.
Comment 2 Ross Burton 2015-10-08 15:25:05 UTC 
Robert, did you send patches for this?  I can't see anything in oe-core.
Comment 3 Robert Yang 2015-10-09 01:40:17 UTC 
(In reply to comment #2)
> Robert, did you send patches for this?  I can't see anything in oe-core.

Yes, I had sent the patch:
http://lists.openembedded.org/pipermail/openembedded-core/2015-July/106872.html

RP said that it wasn't a correct fix, I will verify whether this was got fixed or not, maybe RP has fixed it by this patch:

http://lists.openembedded.org/pipermail/openembedded-core/2015-July/108198.html
Comment 4 Richard Purdie 2016-09-12 11:03:08 UTC 
As far as I can tell, this problem was fixed by the data store rework and I can't reproduce against master.