[Vm-dev] [squeak-dev] managing the transition to 64-bit

David T. Lewis lewis at mail.msen.com
Tue Dec 13 02:04:03 UTC 2016


On Mon, Dec 12, 2016 at 05:25:53PM -0800, Eliot Miranda wrote:
>  
> > On Dec 12, 2016, at 3:43 PM, Ben Coman <btc at openinworld.com> wrote:
> > 
> >> On Tue, Dec 13, 2016 at 3:34 AM, Chris Muller <asqueaker at gmail.com> wrote:
> >> I'm saying that the traditional way of installing a global VM, by installing under /usr/local, cannot support dual 32 and 64-bit installation because the directory name under "lib" is exactly the same for both platforms.
> >> 
> >> Installing from cog_linux32x86_squeak.cog.spur_201608171728.tar.gz:
> >> 
> >>    /./products/cogspurlinuxht/lib/squeak/5.0-201608171728/squeak  "32-bit"
> >> 
> >> and from cog_linux64x64_squeak.cog.spur_201608171728.tar.gz:
> >> 
> >>   /./products/cogspur64linuxht/lib/squeak/5.0-201608171728/squeak  "64-bit!"
> >> 
> >> copying from the highlighted, down, to the traditional /usr/local location makes that conflict.
> 
> I like any of the following:
>     /usr/local/squeak/{lib,lib64}/squeak/5.x-20yymmddhhmm/
> 
>     /usr/local/squeak/{lib32,lib}/squeak/5.x-20yymmddhhmm/
> 
>     /usr/local/squeak/{lib32,lib64}/squeak/5.x-20yymmddhhmm/
> 
> and then have /usr/local/squeak/squeak & /usr/local/squeak/bin/squeak determine which lib dir to use based on e.g. the od program, or possibly hexdump.
> 
> Does this make sense?

The fundamental requirement is that the run script (/usr/local/bin/[squeak|cog|spur|spur64])
needs to be able to select a folder in /usr/local/lib/squeak/ that contains something runnable.

That folder needs to be distinct by (at least) 32/64 bit host, 32/64 bit image, and Spur versus V3.

The fundamental constraint is that VM plugins cannot be mixed between those combinations, so
at the present time organizing them in distinct folders under /usr/local/lib/squeak provides
a practical solution.

Dave



More information about the Vm-dev mailing list