On Thu, 22 Nov 2018 at 23:22, horrido <horrido.hobbies@gmail.com> wrote:
I'm running 64-bit Debian in a VirtualBox image on my Mac.
When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I get the error message below. What's the difference??? Why can one find the display driver and the other can't? This makes no sense.
Apart from the much larger images possible, a big driver to produce 64-bit Pharo is that Linux installations were becoming predominantly 64-bit and by default don't pre-install all the 32 bit libraries. e.g... https://www.maketecheasier.com/run-32-bit-apps-in-64-bit-linux/ When Pharo was *only* 32-bit, there were instructions on which 32-libs were required. I'm not sure were they are now. (Maybe its worth keeping them around for such cases, although it seems a backward step.) You might find something at forum.world.st. Ah, I see Sven has some good info.
Earlier, people have been telling me to use './pharo-ui Pharo.image &'. Is this no longer kosher? What am I doing wrong?
It depends on whether you download the standalone or using zero-conf. This inconsistency has bitten me a few times, but I was familiar enough to quickly determine what was going. Consistency would be good, but we'd need to break the long standing pattern of one or the other. cheers -ben