Thanks for sharing that with us. Can you do a pull resquest for the changes you suggest? I think that for the bootstrap we have to recreate the source each time so we should recreate because it is depend on what is in the boostrap. Now this bootstrap is slow and you can reuse the result of our builds. Stef On Thu, Mar 8, 2018 at 11:34 AM, Hilaire <hilaire@drgeo.eu> wrote:

I give again a try to bootstrap (after my last summer fail). Here how far I went:

1. Fetched the repo https://github.com/pharo-project/pharo. I have to fetch a fresh one as updating my repo failed with the git command pull/fetch/merge/reset hard does not work. Incredible how simple thinks does not work simply with git. Do people really like git or pretend to because everyone is using it.

2. Followed instructions to build a bootstrap.

BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh

The resulting image bootstrap-cache/bootstrap.image is built after 1 or 2 hours. Its size is 3,4MB, when started there is only blank screen, I guess it is the expected outcome.

3. Followed instructions to load pharo environment:

BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 ./bootstrap/scripts/build.sh

Several attempts were needed and the build.sh script is fragile and fail when at the repeated attempts, some cleaning were needed.

I suggest two things :

1. you add -p to your mkdir commands (in build.sh and get-vm.sh scripts) as it make your script less fragile ! 2. Also checking for the existence of the Pharo.source will avoid to have duplicted uncessary downloaded source file version. (Pharo.source1, Pharo.source2):

if test ! -e PharoV60.sources then wget http://files.pharo.org/sources/PharoV60.sources fi

Now the image is building, will see next.

Hilaire

-- Dr. Geo http://drgeo.eu

Le 08/03/2018 à 11:34, Hilaire a écrit :

Now the image is building, will see next.

The build process ended with this output, don't know if it is right: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: [ self     handleArgument:         (self arguments             ifEmpty: [ '' ]             ifNotEmpty: [ :arguments | arguments first ]) ] in [ [ self     handleArgument:         (self arguments             ifEmpty: [ '' ]             ifNotEmpty: [ :arguments | arguments first ]) ]     on: Exit     do: [ :exit |         "If the command line is protected by password, we just exit the image because in non-headless mode the handleExit will let the image open. If the password protection is enabled, it is to avoid to let the access to the image."         self class commandLinePasswordManager hasPasswordSet             ifTrue: [ Smalltalk snapshot: false andQuit: true ].         ^ self handleExit: exit ] ] in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self... BlockClosure>>on:do: [ [ self     handleArgument:         (self arguments             ifEmpty: [ '' ]             ifNotEmpty: [ :arguments | arguments first ]) ]     on: Exit     do: [ :exit |         "If the command line is protected by password, we just exit the image because in non-headless mode the handleExit will let the image open. If the password protection is enabled, it is to avoid to let the access to the image."         self class commandLinePasswordManager hasPasswordSet             ifTrue: [ Smalltalk snapshot: false andQuit: true ].         ^ self handleExit: exit ] ] in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ [ self... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... -- Dr. Geo http://drgeo.eu