Hi Ulf.
The links below point to variables that contain info on what jvm we're
building. Volker's questions was about the bootstrap vm.
Using file-like util seems a better option because it simply parses the ELF header of the execulable (or COFF in case of windows) and we don't want
to start jvm an extra time to find this bit of information.
Thanks,
Ivan
On 2011-10-30 13:14, Ulf Zibis wrote:
Am 29.10.2011 21:41, schrieb Ulf Zibis:
Hi,
I still don't understand, why you can't use the OS_ARCH information from the new
"release" file. See:
- 6989472 <http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472931> -
Provide simple jdk identification information in the install image
-
http://markmail.org/search/?q=list%3Anet.java.openjdk#query:list%3Anet.java.openjdk.build-dev%20from%3A%22Ulf%20Zibis%22+page:2+mid:al5nss7e5lh676me+state:results
- http://thread.gmane.org/gmane.comp.java.openjdk.build.devel/3603/focus=3757
- http://www.mail-archive.com/build-dev@openjdk.java.net/msg03706.html
-Ulf
Oops, wrong ID behind link, correction:
- 6989472 <http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6989472> -
Provide simple jdk identification information in the install image
-Ulf
Am 28.10.2011 19:22, schrieb Volker Simonis:
I think 'file' is a good idea because we're in a Cygwin bash anyway.
The output for 64 and 32 bit executables is:
PE32+ executable (console) x86-64, for MS Windows
PE32 executable (console) Intel 80386, for MS Windows
That should be easy enough to parse.
I'll be on holiday and on the EclipsCon next week but after that I can
submit a patch if you want.
On the other side I'll be not offended if you fix it:)
Regards,
Volker
