Summary: | jamvm 1.3.3 can not be emerged | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Gavilan <david> |
Component: | Current packages | Assignee: | Karl Trygve Kalleberg (RETIRED) <karltk> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | betelgeuse |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 116297 | ||
Bug Blocks: |
Description
David Gavilan
2005-11-04 21:37:18 UTC
*** Bug 111527 has been marked as a duplicate of this bug. *** Bug #105893 has a request (and an ebuild) for Jamvm 1.4.0. PPC users may test this version and 1.3.3 may be marked as PPC incompatible. I just committed jamvm-1.4.1. Please test this release. It does not have ~ppc currently. See bug 116297. Thank you! I successfully emerged jamvm 1.4.1 and gnu-classpath 0.19 on PPC (adding ~x86 keyword). ACCEPT_KEYWORDS="~x86" emerge jamvm It works. jamvm-1.3.3 was broken for ppc due to a partially-finished transition in processing the platform-specific assembly file; jamvm 1.3.1 had callNative.s with asm-style '#' comments, and jamvm-1.4.1 has callNative.S with '/**/' cpp-style comments. jamvm-1.3.3 was a transition where the file-ending was switched to .S but the comments were not yet updated to be cpp-friendly. Since the newer version works well and is now keyworded ~ppc, it is probably not worth coming up with a patch to fix this. I'm going to keyword 1.3.3 as -ppc |