What steps did you take to compile it, assuming you cross-compiled it?
The reason I ask is that I recently tried to make a bitbake file for
openembedded (openembedded is an automated compiling tool for creating
embedded linux distros - it's currently being used for the angstrom
distibution - ex. OpenZaurus, the openmoko phone distribution and others)
and I ran into a few problems that kept me from being able to produce an
automated cross-compile for different architectures:
Currently, the common way to tell a configure script about things that it
can't test itself is through a config.site file which contains answers to
questions like the size of int for the target platform however, the
configure script for the squeak vm, for some reason beyond my ken, still
wants to run a test program. A solution that I have stumbled across on the
net involves patching the configure.ac and rerunning autoconf but that is a
solution that would take a different patch for different architectures.
So I am wondering if there's anything that could be added to the current set
of config.sites or if the configure script needs to be altered in some way
to take the info in that file into account.
Cheers,
James Fenn


On 17/3/07 2:32 am, "Ian Piumarta" <piumarta at gmail.com> wrote:

> Hi,
> 
> In case anyone is interested, I've compiled a VM for the Nokia N800
> and put it here:
> 
>      http://squeakvm.org/unix/release/Squeak-3.9-10.arm-linux-gnu.tar.gz
> 
> I've tested it superficially and it runs standard images, the mouse
> works fine, and you can take it in and out of fullscreen from the
> world menu.  However there is no VM support for the N800 buttons (so
> middle- and right-click cannot be generated) nor for the system
> virtual keyboard.
> 
> Cheers,
> Ian
> 
>