[RFC] Fix Zero and Shark builds

[Roman Kennke]

Am Donnerstag, den 21.02.2013, 21:17 +1000 schrieb David Holmes:
> So far I've looked at the hotspot changes - but really this should also 
> go to hotspot-dev - cc'd
> 
> I only see one change that isn't confined to zero/shark specific code 
> and that is in make/linux/makefiles/vm.make:
> 
>    ifeq ($(JVM_VARIANT_ZEROSHARK), true)
>      STATIC_CXX = false
>    else
> !   ifeq ($(OPENJDK_TARGET_CPU), ppc64)
>        STATIC_CXX = false
>      else
>        STATIC_CXX = true
>      endif
>    endif
> 
> this may conflict with the incoming AIX/ppc64 port.

So far, the only supported ppc64 in Hotspot is Zero. At least to my
knowledge. I am not sure why we need to explicitely link libstdc++
dynamically there though. I don't really see how this could affect
anything outside Zero. And yes, it probably does affect the upcoming
PPC64 port, but this needs to be sorted out anyway.


> My other comment on these changes is that you've now made the zero 
> hotspot build dependent on being part of a complete build - ie there 
> must be a spec.gmk/hotspot-spec.gmk for these variables to be defined. 
> You won't be able to build hotspot stand-alone. Is that what you intended?

Probably not. Not sure how a standalone hotspot build works with the new
build-system. (I would be very happy to do this to reduce turnaround
even more.) What would I need to do? Move all Zero/Shark variables to
hotspot-spec.gmk.in ?

Thanks,
Roman