harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Tanzer <stru...@guglhupf.net>
Subject Re: Small problems building under cygwin
Date Fri, 21 Oct 2005 15:00:58 GMT
Maybe we could collect all portability issues on a page in the harmony -
wiki, so if others have to deal with the same problems they can find
them quickly...

Regards,
David.

On Thu, 2005-10-20 at 09:29 -0500, Apache Harmony Bootstrap JVM wrote:
> Rodrigo,
> 
> Thanks for your help with these items.  I think that
> it should be a simple matter to have 'config.sh' set
> a 'win32' path.  In fact, there should probably be
> a map function for that include path so that each
> configuration can set that subdirectory name to
> whatever Sun declares it to be for that platform
> instead of depending on the OS platform name.
> 
> The '__int64' issue is an interesting one!  That's
> why we're trying out all these porting things.  To
> me, the solution depends partly on a matter of
> build policy, namely, which compilers do we use?
> I think that there is a case to be made for supporting
> MSVC in addition to GCC since it has a large installed
> base, and a Windows version of the build scripts
> should be able to support both.  I suggest that we
> could have the compiler as one of the configuration
> options in 'config.sh' for Windows and CygWin, also
> for the Windows .BAT file equivalent.  What do you
> think?
> 
> 
> Dan Lydick
> 
> 
> -----Original Message-----
> From: Rodrigo Kumpera <kumpera@gmail.com>
> Sent: Oct 19, 2005 5:42 PM
> To: harmony-dev <harmony-dev@incubator.apache.org>
> 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
-- 
David Tanzer, Haghofstr. 29, A-3352 St. Peter/Au, Austria/Europe
http://deltalabs.at -- http://dev.guglhupf.net -- http://guglhupf.net
My PGP Public Key: http://guglhupf.net/david/david.asc
--
Pinky, Are You Pondering What I'm Pondering?
Umm, I think so Big Brainy Fish Face Stove Pipe Wiggle Room Eileen. 
But if you get a long little doggie, wouldn't you just call it 
a dachshund?

Mime
View raw message