Hi Yanni Chiu, Thanks for the reports,
> El 15 jul 2021, a las 20:49, Yanni Chiu <yannix...@gmail.com> escribió: > > First, great work and thanks to all contributors. > > Using macOS Big Sur version 11.4 on MacBook Air 2019... > > 1. In a new sub-directory "pharo9" (I was using a pharo8 directory, so > pharo9 is to keep things separate). In pharo9, I used "curl -L > https://get.pharo.org/64/ | bash" to get the latest release. Then I > ran ./pharo-ui to start Pharo. Very strangely, it was able to present > my pharo8 images to choose for opening. I quit without choosing any > image, then went looking to find out how it was able to find the > settings. In the course of that, I realized the default download had > got me the 8.0 release. Yes, this was due to my updates to zeroconf. There was a missing update at https://get.pharo.org/64/ and https://get.pharo.org/32. I’ve fixed these and wrote an issue to automate this in the future https://github.com/pharo-project/pharo-zeroconf/issues/34 > > 2. Then I used "curl https://get.pharo.org/90+wm | bash". The image > came up with a strange looking dialog across the top that indicated > freetype font lib's could not be loaded. I just proceeded and was able > to navigate somewhat. The Settings for fonts were completely absent. I > kept browsing, but more freetype font problems kept appearing. > > 3. I then compared the dylib's in the pharo-vm (what I had in pharo8) > vs. what I just got in pharo9 - very different lists. I copied the > libfreetype.6.dylib, libfreetype.dylib, and libFT2Plugin.dylib files > to the new vm, and then the Pharo9 image came up nicely. > > 4. I thought I was home free, and continued browsing. I happened to > look at the Pillar-Core code, and I got "Cannot locate > libcairo.2.dylib". Browsing a few other places did not show this > problem. That's it for now. I will try a bit more later, but I'm going > back to Pharo8 for today. Pablo has updated the VMs just some minutes ago, so these issues should be resolved. Thanks again! :) Guille > > Yanni Chiu
