> On 23-05-2017, at 5:08 AM, David T. Lewis <lewis at mail.msen.com> wrote:
> 
> On Tue, May 23, 2017 at 12:27:42PM +0200, Bert Freudenberg wrote:
>> Does anyone have access to a Debian testing/unstable system? Could you
>> check if Etoys really gets stuck, and maybe figure out why?
>> 
>> I suspect it might be because they're running on x86_64. The VM is
>> 4.10.2-2614.
>> 
>> - Bert -
> 
> I don't have a Debian system, but you are probably right. I did a quick
> check of running an Etoys-To-Go-5.0 image on a 64-bit interpreter VM,
> compiled locally, version level 4.16.3-3748. It seems to run fine on my
> 64-bit Ubuntu. But the 4.10.2-2614 VM is really quite old now and probably
> does have some issues on a 64-bit system.
> 
> Being Debian, I suspect that the VM needs to be compiled from source, is
> that right? Or would a pre-compiled VM be sufficient?

My experience suggests being *very* careful with the way Debian mangles our code. Last time I had to dig into it there was an override of our jpeg reading code that quite blatantly broke reading the files. Worse, it appeared that no one there had even bothered to contact any of us to ask why we needed that particular code.


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Debugger: A tool that substitutes afterthought for forethought.