Bug 44871

Bug: 44871

Impact:

Product:

GemStone/S 64 Bit

Versions:

3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.8, 2.4.4.7, 2.4.4.6, 2.4.4.5, 2.4.4x, 2.3.1.6, 2.3.1, 2.2.6.5, 2.2.5.4, 2.2.x, 2.x, 2.4x, 1.x

Platform:

All

Fixed In:

3.3

The gemsetup.sh and gemsetup.csh scripts append at end of path

Gemsetup.sh and gemsetup.csh are scripts that can be used to setup the environment for your version of GemStone.  However, when you use these scripts, they add the GemStone version at the end of the current path. If you have an installation for a different version of GemStone already on your path, when you attempt to execute e.g. startstone, startnetldi, or topaz, you will get the old version instead of the new version.

Workaround

Make sure there are no other GemStone installations in your path when you use gemsetup, or manually add the GemStone installation at the beginning of the path.