Douglas Simon
Douglas Simon
When you execute `MX_BINARY_SUITES='' mx build` isn't the jvmci source suite resolved (and downloaded if necessary) bypassing the jvmci binary suite altogether?
Sorry, I got confused and interpreted `MX_BINARY_SUITES=‘’` to mean don’t use binary suites. Also, I didn’t see any failure with graal-core as the primary suite. Obviously, it has to be...
That seems reasonable to me - I don't know where else could we get version info from a binary suite?
@peblpebl thanks for submitting. @pejovica does that fix look right?
@peblpebl we are now considering to remove cygwin environment support altogether: https://github.com/graalvm/mx/issues/189 Can you please confirm that mx works for you when run with a standard Windows python executable.
How is this resolved for JDKs installed under `/Library/Java/JavaVirtualMachines`? It would be best to adopt an existing solution to this problem.
Given that fetch-jdk will use the [native platform](https://github.com/graalvm/mx/blob/master/mx_fetchjdk.py#L450) in deciding which binary to download, this is more than just about disambiguating on the installation directory name. That is, I don't...
@zapster, I think it would be best if someone who uses `sforceimport` takes on this issue.
@soufianenassih can you please look into this.