| Summary: | Add ptest for gcc | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | devtools / tool chain | Assignee: | Armin Kuster <akuster> |
| Status: | CLOSED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | akuster, meta.mr.watcher, meta.watcher, raj.khem, randy.macleod, richard.purdie, sgw |
| Version: | 1.5 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2013-04-29 15:50:53 UTC
While nothing technically prevents making a gcc-ptest, do people typically build and install gcc on their targets? My team is working on gcc-runtime-ptest (the libstdc++ test suite) but we currently have no plans for the compiler test suite. If anyone else wants to have a go at it, feel free. Khem did add some work this could be based off in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2480cc6a169f7d34d82d9e22c52f700e772ab45d I have a resource that can look at this. are the patches fron Nathan addressing this ? I guess yes in 3.0 done by Nathan. . |