Well, I don't need both.
I installed OLPC for the problems, and I uninstalled.
Now, I can't run squeak hehehe
If I do "squeak" or "squeak -plugins /usr/local/lib/squeak/3.10-4" I get always: could not find display driver vm-display-X11; either: - check that /usr/local/lib/squeak/3.10-4/vm-display-X11.so exists, or - use the '-plugins <path>' option to tell me where it is, or - remove DISPLAY from your environment.
Must be something on OLPC rpm, thath is not in tar.gz from squeakvm.org
El lun, 25-05-2009 a las 19:59 +0530, K. K. Subramaniam escribió:
On Monday 25 May 2009 07:31:55 pm Giuseppe Luigi Punzi wrote:
Investigating, seems that I have 2 libs directories for squeak. "/usr/local/lib/squeak/3.10-4" and "/usr/lib/squeak/3.10-3".
Squeak by default, is searching on "/usr/local/lib/squeak/3.10-4" and trying to running with -plugins /usr/local/lib/squeak/3.10-4 doesn't works.
But, if I do -plugins /usr/lib/squeak/3.10-3 it works. This directory comes from the OLPC VM.
/usr/bin/squeak is usually a symlink. In your case, I suspect it is linked to the 3.10-3/ path while the search order could have 3.10-4 before this path. To fix a) Remove the unneeded version. b) If you need both, create launcher scripts with the right PATH and SQUEAK_PLUGIN env variables or use explicit path, e.g /usr/lib/squeak/3.10-3/squeak -plugins /usr/lib/squeak/3.10-3 Check if your squeak binaries support SQUEAK_PLUGINS env variable $ strings `which squeak` | grep SQUEAK_
HTH .. Subbu