Building via mvm scripts results in a VM that segfaults when attempting to load a Pharo 8 image.
The error: — |
I suggest you take this up with the "PharoVM" team who claim the VM as their own and profess to have the expertise to support it. — |
In reply to this post by David T Lewis
Closed #519. — |
In reply to this post by David T Lewis
this is an incredibly rude way to ask if the problem persists with other smalltalk images. — |
In reply to this post by David T Lewis
Hello there and welcome. This might seem very strange to you, but there is a bit of history that leads to this outcome. You report seems to indicate that you used a Pharo-issued VM and a Pharo image. In that case, your inital question might be better answered at https://github.com/pharo-project/opensmalltalk-vm That repo states
For seveal reasons, including a perceivedly low amount of "keep compatibility and contribute back" we cannot offer any support for VMs from that repo. If you have used a VM from this repo and the error pops up with a non-Pharo image, please say so and we can reopen this issue. — |
In reply to this post by David T Lewis
the VM was from this repo, that is why i reported it here. — |
In reply to this post by David T Lewis
Reopened #519. — |
In reply to this post by David T Lewis
Thanks, can you give a few more hints about the primivite failures? Please use the — |
In reply to this post by David T Lewis
> On Sep 3, 2020, at 2:28 AM, IcedQuinn <[hidden email]> wrote: > >  > this is an incredibly rude way to ask if the problem persists with other smalltalk images. > The PharoVM team’s behaviour is far worse than merely rude. Your own assumption that I would support the PharoVM after all they have done and continue to do to steal credit and not contribute back could also be construed as rude, but perhaps it is merely ignorant. If the problem occurs in other images and non-Pharo builds of OpenSmalltalk perhaps you could provide steps to reproduce the problem. Until that time my response to requests for support with a Pharo branded vm with be a firm rejection. > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub, or unsubscribe. — |
In reply to this post by David T Lewis
Closed #519. — |
In reply to this post by David T Lewis
Ok, reopening and awaiting input on the Squeak primitve errors :) — |
In reply to this post by David T Lewis
Reopened #519. — |
In reply to this post by David T Lewis
(this is coordinated with @eliotmiranda , I'm assigning myself here) — |
In reply to this post by David T Lewis
Closed #519. — |
In reply to this post by David T Lewis
i apologize for cloning your repository and attempting to use it. — |
In reply to this post by David T Lewis
:( — |
In reply to this post by David T Lewis
That would be a lie, as new users are welcome here. — |
In reply to this post by David T Lewis
On Thu, Sep 03, 2020 at 03:03:50AM -0700, IcedQuinn wrote: > the VM was from this repo, that is why i reported it here. the cmake > files in this repo default to turning "pharo branding" on. i launched > a squeak 5 image and it did appear to throw out any primitive failures > and the stock code browser was working correctly. the VM also said to > report here how to get it working since it did not recognize where > libc was. Hi, I've built the OpenSmalltalk VM on Alpine Linux for use with Pharo. Entire build process happens within Docker. Take a look: https://github.com/pharo-contributions/Docker-Alpine/tree/master/vm.build The modified source to build on Alpine comes from my fork: https://github.com/PierceNg/opensmalltalk-vm/tree/pierce_alpine_839a5ca The hex string at the end of the branch name is the OpenSmalltalk commitish the branch is based on. This VM runs my blog in an Alpine Linux Docker container. HTH. Pierce |
In reply to this post by David T Lewis
Hi Pierce, thanks for the info, but I don't see how these changes can alleviate the primitive erros. — |
In reply to this post by David T Lewis
Reopened #519. — |
Free forum by Nabble | Edit this page |