@Martin Dorey: No problem.
When I build jdk8u as suggested, encountered the below error:
Compiling
/export/home/preethi/openjdk8u/hotspot/src/share/vm/compiler/abstractCompiler.cpp
Compiling
/export/home/preethi/openjdk8u/hotspot/src/share/vm/utilities/accessFlags.cpp
Compiling ../generated/adfiles/ad_x86_32.cpp
"/export/home/preethi/openjdk8u/hotspot/src/share/vm/runtime/thread.hpp", line
202: Warning: Identifier expected instead of "}".
1 Warning(s) detected.
gmake[6]: ***
[/export/home/preethi/openjdk8u/hotspot/make/solaris/makefiles/rules.make:148:
accessFlags.o] Error 2
gmake[6]: *** Waiting for unfinished jobs....
"/export/home/preethi/openjdk8u/hotspot/src/share/vm/runtime/thread.hpp", line
202: Warning: Identifier expected instead of "}".
1 Warning(s) detected.
gmake[6]: ***
[/export/home/preethi/openjdk8u/hotspot/make/solaris/makefiles/rules.make:148:
abstractCompiler.o] Error 2
"/export/home/preethi/openjdk8u/hotspot/src/share/vm/runtime/thread.hpp", line
202: Warning: Identifier expected instead of "}".
1 Warning(s) detected.
gmake[6]: ***
[/export/home/preethi/openjdk8u/hotspot/make/solaris/makefiles/rules.make:148:
ad_x86_32.o] Error 2
gmake[5]: ***
[/export/home/preethi/openjdk8u/hotspot/make/solaris/makefiles/top.make:112:
the_vm] Error 2
gmake[4]: ***
[/export/home/preethi/openjdk8u/hotspot/make/solaris/Makefile:226: product]
Error 2
gmake[3]: *** [Makefile:231: generic_build2] Error 2
gmake[2]: *** [Makefile:177: product] Error 2
gmake[1]: *** [HotspotWrapper.gmk:45:
/export/home/preethi/openjdk8u/build/solaris-x86-normal-server-release/hotspot/_hotspot.timestamp]
Error 2
gmake: *** [/export/home/preethi/openjdk8u//make/Main.gmk:110: hotspot-only]
Error 2
/export/home/preethi/openjdk8u/hotspot/make/solaris/makefiles/rules.make:
# Sun compiler for 64 bit Solaris does not support building non-PIC object
files.
ifdef LP64
%.o: %.cpp
@echo Compiling $<
$(QUIETLY) $(REMOVE_TARGET)
$(QUIETLY) $(COMPILE.CXX) $(DEPFLAGS) -o $@ $< $(COMPILE_DONE)
else
%.o: %.cpp
@echo Compiling $<
$(QUIETLY) $(REMOVE_TARGET)
$(QUIETLY) $(if $(findstring $@, $(NONPIC_OBJ_FILES)), \
$(subst $(VM_PICFLAG), ,$(COMPILE.CXX)) $(DEPFLAGS) -o $@ $<
$(COMPILE_DONE), \
$(COMPILE.CXX) $(DEPFLAGS) -o $@ $< $(COMPILE_DONE))
Endif
"/export/home/preethi/openjdk8u/hotspot/src/share/vm/runtime/thread.hpp":
enum SuspendFlags {
// NOTE: avoid using the sign-bit as cc generates different test code
// when the sign-bit is used, and sometimes incorrectly - see CR
6398077
_external_suspend = 0x20000000U, // thread is asked to self suspend
_ext_suspended = 0x40000000U, // thread has self-suspended
_deopt_suspend = 0x10000000U, // thread needs to self suspend for
deopt
_has_async_exception = 0x00000001U, // there is a pending async exception
_critical_native_unlock = 0x00000002U, // Must call back to unlock JNI
critical lock
JFR_ONLY(_trace_flag = 0x00000004U) // call jfr tracing
};
Kindly ignore if it has nothing to do with gmake.
Regards,
Preethi
From: Martin Dorey <[email protected]>
Sent: Monday, June 29, 2020 8:31 PM
To: Preethi Selvaraju <[email protected]>; [email protected]; [email protected]
Subject: Re: make4.3/make4.2.1 - solaris 11 x86 issues
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don't click links or open attachments as it may be a Phishing email,
which can steal your Information and compromise your Computer.]
I'm pleasantly surprised, as it looked like there were a bunch of later issues
possibly not fixed in jdk8u, including
https://savannah.gnu.org/bugs/index.php?57676<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsavannah.gnu.org%2Fbugs%2Findex.php%3F57676&data=02%7C01%7Cpreethi.s%40hcl.com%7C6874bfcd32d548c0dac308d81c3d3607%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637290397214791283&sdata=Prsv3e%2F6z4um5dQKRCipPkm7SVvltHQXBN%2BosZhKrq0%3D&reserved=0>,
which is still waiting for Paul to visibly take a stance on, after Dmitry's
kind patch.
Sorry, Preethi, for my (likely) misgendering. I must not assume.
________________________________
From: Preethi Selvaraju <[email protected]<mailto:[email protected]>>
Sent: Monday, June 29, 2020 07:53
To: [email protected]<mailto:[email protected]>; Martin Dorey;
[email protected]<mailto:[email protected]>
Subject: RE: make4.3/make4.2.1 - solaris 11 x86 issues
***** EXTERNAL EMAIL *****
Thank you Team. I tried jdk8u and it works fine. I don't see that issue.
Thanks for pointing it out.
~Preethi
-----Original Message-----
From: Paul Smith <[email protected]<mailto:[email protected]>>
Sent: Monday, June 29, 2020 8:22 PM
To: Martin Dorey
<[email protected]<mailto:[email protected]>>;
Preethi Selvaraju <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: make4.3/make4.2.1 - solaris 11 x86 issues
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don't click links or open attachments as it may be a Phishing email,
which can steal your Information and compromise your Computer.]
On Mon, 2020-06-29 at 14:17 +0000, Martin Dorey wrote:
> Looks a likely match for:
>
> https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.
> openjdk.java.net%2Fpipermail%2Fbuild-dev%2F2014-November%2F013597.html
> &data=02%7C01%7Cpreethi.s%40hcl.com%7C5780e124ac11417cb4ce08d81c3b
> ef8d%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637290391044631321&a
> mp;sdata=XIfpUkC2VzCOkCjIvmWJziv9vNHn%2F1P0HaycsbpPAEU%3D&reserved
> =0
>
> Fixed in jdk8u in 2014. Surely our OP is using that already... but he
> does say jdk8 rather than jdk8u, so maybe not.
Why do they do this super-bizarre hacking of flags?
Anyway, they should be using MAKEFLAGS not MFLAGS if they want to be portable.
MFLAGS is not POSIX.
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only. E-mail transmission is not guaranteed to be
secure or error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or may contain viruses in transmission.
The e mail and its contents (with or without referred errors) shall therefore
not attach any liability on the originator or HCL or its affiliates. Views or
opinions, if any, presented in this email are solely those of the author and
may not necessarily reflect the views or opinions of HCL or its affiliates. Any
form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written
consent of authorized representative of HCL is strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. Before opening any email and/or attachments, please check them for
viruses and other defects.
________________________________
