getting toolchain to be used

[Xen]

David Holmes schreef op 03-05-2017 6:07:

> For cross compilation you should need to set the following only:

So basically I know have a working HotSpot build for u101 but u131 and 
u121 fail because a single cpp file references a variable that doesn't 
exist anywhere in the source code. I know it means "MutableCallSite" 
because it is referenced in java code but there is no other cpp or hpp 
file that actually uses it.

Not that name of variable at least.

And u101 refuses to create the final executable correctly, I mean the 
final liblvm.so.

So next up is u111b01 :p.

111b01 succeeds in building but again cannot create the liblvm.so

So I had to add "rm -f $@; \" to the vm.make file and then I needed to 
add -Xlinker -rpath=directory to my EXTRA_CFLAGS.

For linking against libffi.so.6

And now the hotspot concluded :p.

Within seconds it ran into another library not found error this time 
libjvm.so that it just created.

Am I doing something wrong with the directories?

In the makefile $@ expanded to libjvm.so and LIBJVM_G also expanded to 
that, when clearly they were intended to be separate

I think I told it only to build a client vm but my target build dir 
/lib/arm/client does not exist; is empty.

That server jvm is 121 MB :O. Is that because of debug information?

Okay, for some reason before it required -Xlinker -rpath and now it 
requires -L...

Now it tries to add a copyright date notice to a small header file and 
then add to it using build/tmp/java/java.nio/nio/genSocketOptionRegistry 
but this program fails, saying:

Syntax error: word unexpected (expecting ")")


The problem is that it is trying to run an ARM executable on my build 
host :).

:P.

This is going to take fundamentally forever, if I keep this up.

So the makefile was not correct, it only used HOST_CC in case of MacOS 
platform.

I am going to apply those IcedTea patches I think....

Now it uses the wrong AS.

My mistake, gcc actually uses the path to find an as that matches it, 
which doesn't work in my case since I have overridden it. Proceeding 
again.

So I fixed the previous thing wrong and got a java compile error because 
the file ended up empty after using the default "CC" CCFLAGS, obviously 
that doesn't work so well when using HOST_CC.

Fixed again, now at last I get a normal error: libasound is not there 
yet :p.

The errors that are supposed to happen.

Thankful errors :p.

Omg I should never have attempted this.

But anyway with libasound compiled I am further ahead again.

Now my biggest question: how can I create a true headless mode?


DO I need X11 headers persé? Can I just skip X11 compilation and awt 
compilation?

Please? :P.



Regards.