Pharo 2.0 does not seem to work on a standard Squeak interpreter VM any more.
Can anyone explain why? I suspect it might be something in the image startup
code, because Pharo 2.0 does work on Cog (from Eliot's site), and AFIK there
should be little functional difference between Cog and interpreter VM aside
from VM parameters that might be getting tested at image startup.
Thanks,
Dave
On Wed, Jan 30, 2013 at 01:04:35PM +0100, Esteban Lorenzano wrote:
> oops!
> another item into the infinite-todo :)
>
> Esteban
>
> On Jan 30, 2013, at 1:00 PM, Pavel Krivanek <
[hidden email]> wrote:
>
> > Hi,
> >
> > it was only a SqueakVM, I had no luck with compilation of StackVM for
> > it but it is a more general problem of VM development. We simply do
> > not have any StackVM for general platform. I suppose that if you take
> > StackVM and you will make it to run on 64bit Linux (without any
> > assembler or additional 32bit libraries), then you will be able to
> > compile it for RPi too.
> >
> >
> > Cheers,
> > -- Pavel
> >
> > On Wed, Jan 30, 2013 at 12:44 PM, Esteban Lorenzano <
[hidden email]> wrote:
> >> Hi,
> >>
> >> It is a vm issue, non a pharo issue.
> >> and AFAIK, Pavel had a StackVM running (probably some missing plugins, thought), with a Pharo 1.4 inside.
> >>
> >> best,
> >> Esteban
> >>
> >> On Jan 30, 2013, at 12:28 PM, "Torsten Bergmann" <
[hidden email]> wrote:
> >>
> >>> Can anyone give an update on the status of
> >>> Pharo for Raspberry pi?
> >>>
> >>>
> >>
> >>
> >
>
Locked
