| Summary: | the arm gdb tool name convention is not target-triplet + "-gdb" | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | liping Ke <liping.ke> |
| Component: | devtools / tool chain | Assignee: | Richard Purdie <richard.purdie> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, kevin.tian, liping.ke, meta.mr.watcher, meta.watcher, sgw |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
liping Ke
2010-09-14 02:34:41 UTC
Prefix is correct, but we may need to export TARGET_ARCH also to enable you to find right files. To make things less error prone that we have to figure out exact gdb tools name through code, can we add an entry in the environment script called GDB and spell out the name, we are currently already doing it for CC and CXX. I've added: http://git.pokylinux.org/cgit.cgi/poky/commit/?id=f47ae202afd6ef9aa600fed4c1d096dfb7613286 which should give you the option of using TARGET_PREFIX or the GDB variable directly. I saw the export GDB vars with both arm and i586 arch with tip of code. (d1ff9aa4f, RP, Sep. 16, 2010) It works fine! |