Rodrigo, Another thought about the '__int64' issue. A friend told me a while back that this symbol was typedef'ed in a header file called 'stdint.h' on GCC, but this does not exist on my Solaris box, and I didn't need it anyway. For Linux, I suspect that if you go find this symbol in the /usr/include tree, that it will probably appear in this file (I _think_ this is the correct name, but I am not sure). Perhaps this is the way to solve the problem compiling the JNI code?
Regarding your header path question, I've changed the 'config.sh' script to look as $JAVA_HOME/include and ask you which subdirectory to use for the platform-specific JDK header files. Please do an 'svn update' to pick up this change and run 'config.sh' again. See if this works for you and let me know what happens. Dan Lydick -----Original Message----- From: Rodrigo Kumpera <[EMAIL PROTECTED]> Sent: Oct 19, 2005 5:42 PM To: harmony-dev <[email protected]> Subject: Small problems building under cygwin I've found a small issue while building under cygwin. I'm using j2sdk 1.4 and gcc 3.4.4 (cygwin). The problems are when building the jni stuff. First it included on gcc find patch "j2sdk\include\cygwin", but it should be "j2sdk\include\win32". Second is when building the included file "jni_md.h" breaks everything as it defines jlong as "__int64" and not "long long". Fixing both is pretty easy, either edit config/config_opts_always.gcc or rename the directory from win32 to cygwin. The second you can either edit jni_md.h and change "__int64" to "long long" or include a define directive, or something like this, in config/config_opts_always.gcc. I'm not sure what would be the best way to fix this on build.sh, as the first issue is related to build enviroment and the second about incompatible compilers ("__int64" works on MSVC and ICC but not gcc) []s Rodrigo Dan Lydick
