This seems like a compiler bug to me. When we compile with a later gcc
we do not see this, but neither the constant's value nor the size of
long has changed. Not that it is at all clear what "integer constant" is
being referred to.
David
On 22/12/2015 6:21 AM, Erik Joelsson wrote:
I have seen the same error in other parts of the code when building on
older versions of Linux and am not surprised it pops up again. At
Oracle, we don't support this old version of Redhat anymore for JDK 9 so
it's not a regularly tested build configuration. I would recommend
trying a newer version of GCC to get a working build. Internally we use
GCC 4.9.2 built from source.
If that is not an option, you will need to fix the types. I remember
wrapping 64 bit constants in CONST64() did the trick before, but this
isn't really my area of expertise.
/Erik
On 2015-12-21 21:03, Vidaurre, Silvia L wrote:
Hello,
I just downloaded OpenJDK9, and am trying to build it on 32bit RHEL
5.11 with g++ 4.2.1, and I am getting this error from
commandLineFlagRangeList.cpp:
hotspot/src/share/vm/runtime/commandLineFlagRangeList.cpp:293: error:
integer constant is too large for 'long' type
commandLineFlagRangeList.cpp:293 points to:
emit_range_no(NULL RUNTIME_FLAGS(EMIT_RANGE_DEVELOPER_FLAG,
EMIT_RANGE_PD_DEVELOPER_FLAG,
EMIT_RANGE_PRODUCT_FLAG,
EMIT_RANGE_PD_PRODUCT_FLAG,
EMIT_RANGE_DIAGNOSTIC_FLAG,
EMIT_RANGE_EXPERIMENTAL_FLAG,
EMIT_RANGE_NOTPRODUCT_FLAG,
EMIT_RANGE_MANAGEABLE_FLAG,
EMIT_RANGE_PRODUCT_RW_FLAG,
EMIT_RANGE_LP64_PRODUCT_FLAG,
EMIT_RANGE_CHECK,
IGNORE_CONSTRAINT) );
These are my configuration and build commands:
bash ./configure --enable-debug --disable-warnings-as-errors
--with-target-bits=32 --with-boot-jdk=/usr/java/jdk1.8.0_60
make LOG=debug all
Has anyone seen this error before? How do I go about fixing this
error? Any help is greatly appreciated.
Thanks,
Silvia Vidaurre
