| Summary: | please mark =dev-libs/STLport-5.1.5 stable | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Peter Alfredsen (RETIRED) <loki_val> |
| Component: | Current packages | Assignee: | C++ Team [disbanded] <cpp+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | esigra, fauli |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | 2008.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 245160 | ||
| Attachments: | ppc64 build failure | ||
|
Description
Peter Alfredsen (RETIRED)
2008-10-08 22:42:22 UTC
Should STLport-5.1.2 be masked on ppc because it doesn't build, at least on my system as I reported in bug 240604? (In reply to comment #1) > Should STLport-5.1.2 be masked on ppc because it doesn't build, at least on my > system as I reported in bug 240604? > Nope. That bug was due to you using gcc-4.3.1 which is still ~arch(unstable) on all arches with STLport-5.1.2 which is arch(stable). But it is the reason I'm asking for 5.1.5 to be stabled, so we don't have this problem when gcc-4.3.x goes stable. *** Bug 245194 has been marked as a duplicate of this bug. *** No response from cpp team. Arches, please mark stable on my say-so. amd64/x86 stable ppc stable sparc stable Created attachment 177711 [details]
ppc64 build failure
Anyone else seeing test failures? WFM What is the status here. fails on only ppc64? What should be done? still fails here on ppc64 in exact same way (In reply to comment #12) > still fails here on ppc64 in exact same way Does 5.1.2 fail in the same way? If yes, mark stable and file a bug. If no, we'll have to think of something. Marking STLport-5.1.5 ppc64 for bug 240608; fails same tests as current stable No arches left. Fixed. |
