Looking at the issue tracker, there is a few dozen of open issues
related to Java support, such as
https://github.com/Microsoft/BashOnWindows/issues/541 which seem to
indicate that the Linux subsystem for Windows may still have a few
low-level issues to shake out first. There apparently were some futex
problems, some signal handling issues, etc.
Some of the workarounds for some of the issues I've heard of involve
running the JVM in interpreter mode, but that wouldn't be much fun for
building the JDK, which needs to run javac on the JVM to compile the
class library.
cheers,
dalibor topic
On 24.04.2017 19:35, Ted Neward wrote:
Can you be more specific as to which features it’s lacking? (Having spent a
fair amount of time on Windows in my career, I might be able to suggest some
ways to work with/around it, though I’ll be the first to admit the
Linux-on-Windows subsystem is new to me. The other thing is, I live in Redmond,
and I have several friends who work on DotNetCore, and can maybe ask them for
some ideas on how to work around whatever issues that are coming up.)
Meanwhile, I’ll see if the build works. (I’m not in front of that machine as I
write this.)
Ted Neward
Author, Speaker, Mentor
http://www.newardassociates.com
t: @tedneward | m: (425) 647-4526
On 4/24/17, 5:10 AM, "Erik Joelsson" <[email protected]> wrote:
Hello Ted,
I do not recognize the error, but I suspect that the failing command is
the first time the build is running the newly built jdk to generate
something. Can you try this and see if that works?
$ build/linux-x64/jdk/bin/java
The build should work on Ubuntu 16.04 (it's what I use personally most
of the time). The ubuntu shell on Win10 however is not going to work.
It's certainly something we would like to leverage in the future, but so
far, it's lacking vital features to be feasible.
/Erik
On 2017-04-24 10:41, Ted Neward wrote:
> Tried using Ubuntu 16 (in a Virtual Box image, if that makes a
difference) and the Ubuntu shell in Win10, and keep getting the same error:
>
>
>
> ExplodedImageOptimize.gmk:40: recipe for target
‘…/jdk_packages_attribute.done’ failed
>
>
>
> Happens for any kind of configured build (fastdebug, slowdebug, release,
tried all three). Not sure how to start debugging this. Hoping that somebody has
seen this before and has a quick one-line fix.
>
>
>
> Error messages suggest checking the build log; where is that? (I’m guessing
build/<target>/build.log, but just checking to make sure there isn’t another one I
should be looking at…)
>
>
>
> Ted Neward
>
> Author, Speaker, Mentor
>
> http://www.newardassociates.com
>
> t: @tedneward | m: (425) 647-4526
>
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>
ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment
