Astares

We seem to have the method twice: 

@guillep works for me after patching the one in ExternalAddress. I was able to load the full version of Roassal then

Can we apply a trait?

Part 1 was solved in https://github.com/pharo-project/pharo/commit/ac91c64052781873aabeb73f6c5b9370e2f3303b Part 2 and 3 are open still

The log part is ``` -- Configuring done (0.1s) -- Generating done (0.0s) -- Build files have been written to: /cygdrive/c/projects/pharo/pharo-vm/LibGit2-download [ 11%] Performing update step for 'LibGit2-download' [ 22%]...

What is strange: I've checked out the source code on "C:\projects\pharo\pharo-vm" path. I think it its required to checkout on "C:\pharo-vm" as the build seems to expect it there. Cygwin...

I double checked with the workflow build: https://github.com/pharo-project/pharo-vm/blob/pharo-10/.github/workflows/continuous-integration-workflow.yaml Looks like ".\scripts\runScriptInCygwinBash.ps1" always requires a file argument and can not be run interactively. Otherwise one gets an error with "Path" check.

I started freshly: new git clone on C:\pharo-vm Trying to mock the build from workflow file: 1. created a file **run.ps1** in **C:\pharo-vm** ``` mkdir -p build cd build cmake...

As git gives a warning ``` "fatal: detected dubious ownership in repository at '/cygdrive/c/pharo-vm' To add an exception for this directory, call: git config --global --add safe.directory /cygdrive/c/pharo-vm fatal: detected...

After checking with @tesonep (who suggested to set DPHARO_DEPENDENCIES_PREFER_DOWNLOAD_BINARIES to TRUE) I modified the run.ps1 into ``` git config --global --add safe.directory /cygdrive/c/pharo-vm mkdir -p build cd build cmake -S...