Skip to main content

management.cpp", line 1466: Error: Cannot use int to initialize Handle.

6 replies [Last post]
edburns
Offline
Joined: 2004-02-11

I tried this from a fresh build with the snapshot from 11 August and 18 August and both times I get the same result.

Can someone please help me get a clean build?

I'm building on Solaris 10 X86.

Here is the compilation command that fails:

ompiling /home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/services/management.cpp
rm -f management.o
CC -DSOLARIS -DSPARC_WORKS -DIA32 -DUSE_PRAGMA_IDENT_HDR -DUSE_PRAGMA_IDENT_SRC -DASSERT -DFASTDEBUG -DCHECK_UNHANDLED_OOPS -I../generated/adfiles -I../generated/jvmtifiles -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/asm -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/ci -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/code -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/compiler -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/gc_implementation -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/gc_implementation/concurrentMarkSweep -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/gc_implementation/parallelScavenge -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/gc_implementation/shared -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/gc_interface -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/interpreter -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/libadt -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/memory -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/oops -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/opto -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/prims -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/runtime -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/services -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/utilities -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/cpu/i486/vm -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/os/solaris/vm -I/home/edburns/Projects/SE/workareas/mustang/hotspot/src/os_cpu/solaris_i486/vm -I../generated -DHOTSPOT_BUILD_VERSION="\"1.6.0-internal-fastdebug-edburns_23_aug_2005_15_17-b00\"" -DHOTSPOT_BUILD_USER="edburns" -DHOTSPOT_RELEASE_VERSION="\"1.6.0\"" -DCOMPILER2 -DSOLARIS_7_OR_LATER /home/edburns/Projects/SE/workareas/mustang/hotspot/src/os_cpu/solaris_i486/vm/solaris_i486.il -features=no%split_init -library=%none -KPIC -mt -xtarget=pentium -xO3 -g0 -DVM_LITTLE_ENDIAN -features=no%except -DDTRACE_ENABLED -c -o management.o /home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/services/management.cpp
"/home/edburns/Projects/SE/workareas/mustang/hotspot/src/share/vm/services/management.cpp", line 1466: Error: Cannot use int to initialize Handle.
1 Error(s) detected.
make[8]: *** [management.o] Error 1

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
vijayj
Offline
Joined: 2004-10-26

Hi Edburns

I am still not sure what is the cause of your build failure. But you don't have to really build hotspot workspace.

Here is how you can skip building hotspot workspace build.

1 gnumake scsl BUILD_HOTSPOT=false

2 Just simply remove or rename the hotspot workspace.

o cd
o mv hotspot hotspot.old or rm -rf hotspot

If you prefer to skip hotspot build from the control workspace then you need set ALT_HOTSPOT_IMPORT_PATH only.

You shouldn't set ALT_HOTSPOT_SERVER_PATH ALT_HOTSPOT_CLIENT_PATH and ALT_HOTSPOT_LIB_PATH variables when you do the build from the control workspace.

For Eg:-

If you have installed jdk build b48 binaries into /usr/jdk1.6.0 then your variable ALT_HOTSPOT_IMPORT_PATH should be

setenv ALT_HOTSPOT_IMPORT_PATH /usr/jdk1.6.0 (in csh shell)

Also if you are using build b48 source then you need to use build b48 binaries to import the HOTSPOT VM.

Hope this solves your problem.

Let us know if you have any questions or issues.

Thanks,
-Vijayan.

mandychung
Offline
Joined: 2005-04-13

Hi Ed,

We're not able to reproduce this build failure in our environment. Based on the compilation error, we identify the fix for it (see 6315595).

If you want to fix it in your downloaded source, you can make the following change:
in management.cpp line 1466, change CHECK_0 to CHECK_NH.

Thanks
Mandy

sbohne
Offline
Joined: 2005-04-26

Hi Ed -

Are you using Sun Studio 10 compilers (CC -V should report version 5.7)? Sun Studio 10 is required to build Mustang on Solaris.

Steve

xiaobinlu
Offline
Joined: 2005-07-29

Usually, you don't have to build hotspot vm by yourself. You just need to set ALT_HOTSPOT_SERVER_PATH, ALT_HOTSPOT_LIB_PATH & ALT_HOTSPOT_CLIENT_PATH properly so that when you build j2se, it could find out where to pick up the libjvm.so and etc. For example, if you install the latest JDK 6.0 build to /foo/jdk6.0, set
ALT_HOTSPOT_SERVER_PATH to /foo/jdk6.0/jre/lib/i386/server
& ALT_HOTSPOT_CLIENT_PATH to /foo/jdk6.0/jre/lib/i386/client &
ALT_HOTSPOT_LIB_PATH to /foo/jdk6.0/jre/lib/.

I don't know the exact cause of your build failure, but I wish some VM folks would provide you some useful information on that.

edburns
Offline
Joined: 2004-02-11

Thanks, I tried this but got the following errors when doing make scsl in control/make

ERROR: Your build environment has the variable
ALT_HOTSPOT_SERVER_PATH defined. When building
using the control workspace this variable should
not be set. Please unset it and restart your build.

ERROR: Your build environment has the variable
ALT_HOTSPOT_CLIENT_PATH defined. When building
using the control workspace this variable should
not be set. Please unset it and restart your build.

ERROR: Your build environment has the variable
ALT_HOTSPOT_LIB_PATH defined. When building
using the control workspace this variable should
not be set. Please unset it and restart your build.

Exiting because of the above error(s).

Any other ideas?

Ed

kellyohair
Offline
Joined: 2004-09-03

If you are building from the control/make directory, try using 'gnumake BUILD_HOTSPOT=false' to avoid building hotspot. These ALT_HOTSPOT variables seem to be explicitly dis-allowed during a control/make build, not sure why. They probably would work if you built from the j2se/make directory.

I've never seen this hotspot build error before.
You might scan your log file for any WARNINGS, the C++ compiler does need to be 5.7, but in any case I'll look into the source and see what the complaint is about.

-kto