[aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port (original) (raw)
David Holmes david.holmes at oracle.com
Fri Mar 24 01:42:31 UTC 2017
- Previous message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Next message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This issue seems to be fragmenting, given that Mario has put out a RFR on jdk9-dev based on the VENDOR_URL!
We can easily change -Xinternalversion output, which would also affect hs-err log file.
David
On 24/03/2017 5:27 AM, Bob Vandette wrote:
I’m not sure of the exact meaning of these variables but the logic that generates this file is in jdk9/make/ReleaseFile.gmk. I’ll look into the intended purpose.
Perhaps the fact that you have N/A and our build is Oracle might be good enough. Bob.
On Mar 23, 2017, at 3:05 PM, Andrew Haley <aph at redhat.com> wrote: On 23/03/17 18:58, Bob Vandette wrote: What does your aarch64 build have as IMPLEMENTOR in it’s “release” file. I wonder if we can use this difference for now?
IMPLEMENTOR="Oracle Corporation” At the moment, SOURCE=".:d660c00d91bf corba:ff8cb43c07c0 hotspot:9bfa2cceba90+ jaxp:8c9a2a24752b jaxws:92aa05eff5d1 jdk:a2d3b7f65c95 langtools:69e2e4d7136c nashorn:4a07ebdf8b45" IMPLEMENTOR="N/A" I don't know where that file comes from or even what it means. It would be OK, but what would we put there? "OpenJDK"? They're both supposed to be OpenJDK projects. Andrew.
- Previous message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Next message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]