| Summary: | Add ability to use native toolchain inside of the SDK copy of the buildsystem | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Randy Witt <randy.e.witt> |
| Component: | devtools / tool chain | Assignee: | Randy Witt <randy.e.witt> |
| Status: | RESOLVED FIXED | QA Contact: | Yi Zhao <yi.zhao> |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, bluelightning, meta.mr.watcher, meta.watcher |
| Version: | 1.7 | ||
| Target Milestone: | 1.8 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 7467 | ||
| Bug Blocks: | 6435, 6662 | ||
|
Description
Randy Witt
2014-11-06 18:49:04 UTC
Should be in as of: commit 54567379ac7e8dcc1515bd22439cf1f7acf7f761 Author: Randy Witt <randy.e.witt@linux.intel.com> Date: Mon Feb 23 17:00:43 2015 +0000 The way to test this would be to build a sdk using "-c populate_sdk_ext" instead of "-c populate_sdk" and the toolchain should function. Hi Randy, I have this error when trying $ bitbake core-image-sato -c populate_sdk_ext http://pastebin.com/uU02FUuW Is this normal? (In reply to comment #2) > Hi Randy, > I have this error when trying $ bitbake core-image-sato -c populate_sdk_ext > > http://pastebin.com/uU02FUuW > > Is this normal? Hi Alex, nope it's not normal. https://bugzilla.yoctoproject.org/show_bug.cgi?id=7467 I hope to fix that today. Adding Yi as QA Contact. Also, the feature cannot be verified until bug 7467 will be fixed. (In reply to comment #3) > (In reply to comment #2) > > Hi Randy, > > I have this error when trying $ bitbake core-image-sato -c populate_sdk_ext > > > > http://pastebin.com/uU02FUuW > > > > Is this normal? > > Hi Alex, nope it's not normal. > https://bugzilla.yoctoproject.org/show_bug.cgi?id=7467 > > I hope to fix that today. Thanks. I just saw bug 7467 filed by Yi last week, wasn't aware of the issue. Thanks for the update! |