| Summary: | In oe-core built SDK, gcc fails if extracted to another place than /usr/local | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Tasskjapp <tasskjapp> |
| Component: | devtools / tool chain | Assignee: | Nitin Kamble <nitin.a.kamble> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, meta.mr.watcher, meta.watcher, tasskjapp |
| Version: | unspecified | ||
| Target Milestone: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Tasskjapp
2011-12-14 11:12:25 UTC
I am not sure what value is there to allow sdk installing at other places than /usr/local I think the SDK is to be installed at a fixed /usr/local path. For us the value has been the opportunity to have the sdk in our version control system, making it easier to reproduce earlier builds and making sure sdk and rootfs are in sync. BTW you can also fix the issue by creating a permanent link from /usr/local to the version control system. Nitin Tasskjapp, Closing this bug, as it is not a bug. As I mentioned in the comment 3 you should be able to do what you want. If you still need this feature, then reopen this bug. Thanks, Nitin The solution you proposed will work for me. Thanks. |