I was thinking that would be the case. I just didn't even know how to
build it to test the code. It seemed that I was caught in the Chicken
or the Egg problem. I am going to try this RiscOS project as I tries
to translate from Linux calls to RiscOS calls. I am not holding my
breath or anything. Can
On Thu, 2007-08-16 at 21:33 -0500, Robert Pangrazio wrote:
> Well I will look into that. I think that some more detail maybe
> necessary. I am thinking of building for RiscOS. There is a really
> nice project that allows you to compile programs written for linux, on
> a linux machine, to run on a R
There's a lot of platform-specific stuff that will still need
adding. Look in hotspot/src/cpu and hotspot/src/os_cpu -- you
basically need to write everything in their for your platform.
Cheers,
Gary
Robert Pangrazio wrote:
> Well I will look into that. I think that some more detail maybe
> nece
Well I will look into that. I think that some more detail maybe
necessary. I am thinking of building for RiscOS. There is a really
nice project that allows you to compile programs written for linux, on
a linux machine, to run on a RiscOS machine. I would like to try to
use this to build Java. I was
Hi Robert,
I use IcedTea's bootstrap VM and plug replacements. Build them with:
hg clone http://icedtea.classpath.org/hg/icedtea
cd icedtea
./configure
make boot plugs
Then build the JDK with:
export ALT_BOOTDIR=/path/to/icedtea/bootstrap/jdk1.6.0
export ALT_CLOSED_JDK_IMPORT_PATH=
I noticed that to build JDK 6 or higher you need an existing Java
setup. I was wondering how you go about building the JDK for a new
platform. If i have a cross compilation setup for my new platform, can
I use the build machines native JDK, or do I have to have a JDK that
is native to my new platfo
