Hi guys,
I want to move latest vm to stable (for Pharo 6.0, of course). And I have the idea there are still some blocking issues… can you I have this issues in mind: Freetype2 primitive failed [error 2][unknown file format] -> for this I’m testing the solution pointed here: http://log.smallworks.eu/web/post/289, plus a fix Phil sent me. … but also anything else that I might be missing. cheers, Esteban
|
btw… I’m aware of the OSWindows problems, but that’s not solvable in the short term as is… please do not point to that :)
Esteban
|
In reply to this post by EstebanLM
And what the link? https://dl.bintray.com/pharo-project/pharo-vm/? 2017-01-24 10:57 GMT+01:00 Esteban Lorenzano <[hidden email]>:
|
In reply to this post by EstebanLM
itimer version? 2017-01-24 10:57 GMT+01:00 Esteban Lorenzano <[hidden email]>:
|
In reply to this post by EstebanLM
2017-01-24 10:57 GMT+01:00 Esteban Lorenzano <[hidden email]>:
I can report that the linux 64bits version segfault for me. And that I have a hard time compiling it from source (but at least I could get it to work without segfaults from the command line). Thierry
|
In reply to this post by Pavel Krivanek-3
both :)
|
In reply to this post by EstebanLM
Hi,
To accommodate the need to work with OSWindows, I suggest to create a custom download with the current stable so that we can work on OSWindows until the latest gets fixed. What do you think? Cheers, Doru > On Jan 24, 2017, at 10:58 AM, Esteban Lorenzano <[hidden email]> wrote: > > btw… I’m aware of the OSWindows problems, but that’s not solvable in the short term as is… please do not point to that :) > > Esteban > >> On 24 Jan 2017, at 10:57, Esteban Lorenzano <[hidden email]> wrote: >> >> Hi guys, >> >> I want to move latest vm to stable (for Pharo 6.0, of course). >> >> And I have the idea there are still some blocking issues… can you >> >> I have this issues in mind: >> >> No write right on Windows with the new VM >> Freetype2 primitive failed [error 2][unknown file format] -> for this I’m testing the solution pointed here: http://log.smallworks.eu/web/post/289, plus a fix Phil sent me. >> Image freezes on Linux if it was previously saved on Windows >> >> … but also anything else that I might be missing. >> >> cheers, >> Esteban > -- www.tudorgirba.com www.feenk.com “Live like you mean it." |
In reply to this post by Thierry Goubier
- yes… sadly 64bit still will not reach stable - and without reports, I cannot take action ;) - compiling is not harder than before, just instructions are not updated... and in any case, that’s not a problem with moving latest to stable :P Esteban
|
2017-01-24 11:56 GMT+01:00 Esteban Lorenzano <[hidden email]>:
I did report two months ago, to no effect nor answer.
I'm trying to look through your travis setup to find out how things should be done. Is not working too well yet. The 32bits version looks fine. Regards, Thierry
|
In reply to this post by EstebanLM
HI Esteban,
can you be more specific what the problem with "OSWindows" is? I guess you refer to my project "OSWindows" which is in Catalog and in http://smalltalkhub.com/#!/~OS/
and belongs to my operating system series (OSWindows, OSLinuxUbuntu, OSUnix, OSOSX, OSRaspbian, ...) which is about wrapping native APIs and providing easier Pharo work on the different platforms.
Each aspect of this project is covered by unit tests and it should be possible to find out what the problem is.
If you remember it was a good testbed to find issues in UFFI.
But maybe you refer to another project. Because there is also an "OSWindow" (without "s") project done later by Ronie Salgado which is about accessing a platform window from Pharo. This one is at: http://smalltalkhub.com/#!/~ronsaldo/OSWindow Still I wished that Ronie would have choosen a different name as this is now often very confusing to people to distinguish between "OSWindows" and "OSWindow". "NativeWindow" or something like that would have been better for what it is all about... Thanks Torsten
Gesendet: Dienstag, 24. Januar 2017 um 10:58 Uhr
Von: "Esteban Lorenzano" <[hidden email]> An: "Pharo Development List" <[hidden email]> Betreff: Re: [Pharo-dev] I want to move the latest vm to stable... I need feedback ! btw… I’m aware of the OSWindows problems, but that’s not solvable in the short term as is… please do not point to that :)
Esteban
|
Hi,
Esteban and I are referring to OS-Window (the graphical component). Cheers, Doru > On Jan 24, 2017, at 1:00 PM, Torsten Bergmann <[hidden email]> wrote: > > HI Esteban, > > can you be more specific what the problem with "OSWindows" is? > > I guess you refer to my project "OSWindows" which is in Catalog and in http://smalltalkhub.com/#!/~OS/ > and belongs to my operating system series (OSWindows, OSLinuxUbuntu, OSUnix, OSOSX, OSRaspbian, ...) which > is about wrapping native APIs and providing easier Pharo work on the different platforms. > Each aspect of this project is covered by unit tests and it should be possible to find out what the problem is. > If you remember it was a good testbed to find issues in UFFI. > > But maybe you refer to another project. Because there is also an "OSWindow" (without "s") project done later by Ronie > Salgado which is about accessing a platform window from Pharo. This one is at: http://smalltalkhub.com/#!/~ronsaldo/OSWindow > > Still I wished that Ronie would have choosen a different name as this is now often very confusing > to people to distinguish between "OSWindows" and "OSWindow". "NativeWindow" or something like that > would have been better for what it is all about... > > Thanks > Torsten > > Gesendet: Dienstag, 24. Januar 2017 um 10:58 Uhr > Von: "Esteban Lorenzano" <[hidden email]> > An: "Pharo Development List" <[hidden email]> > Betreff: Re: [Pharo-dev] I want to move the latest vm to stable... I need feedback ! > btw… I’m aware of the OSWindows problems, but that’s not solvable in the short term as is… please do not point to that :) > > Esteban > > On 24 Jan 2017, at 10:57, Esteban Lorenzano <[hidden email]> wrote: > > Hi guys, > > I want to move latest vm to stable (for Pharo 6.0, of course). > > And I have the idea there are still some blocking issues… can you > > I have this issues in mind: > > No write right on Windows with the new VM > Freetype2 primitive failed [error 2][unknown file format] -> for this I’m testing the solution pointed here: http://log.smallworks.eu/web/post/289, plus a fix Phil sent me. > Image freezes on Linux if it was previously saved on Windows > > … but also anything else that I might be missing. > > cheers, > Esteban -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?" |
In reply to this post by EstebanLM
I am going to do some 64 bit in the coming weeks as I need to wrap a 64 bit library using UnifiedFFI. Phil On Tue, Jan 24, 2017 at 11:56 AM, Esteban Lorenzano <[hidden email]> wrote:
|
In reply to this post by Torsten Bergmann
On Tue, Jan 24, 2017 at 1:00 PM, Torsten Bergmann <[hidden email]> wrote:
What about "HostWindow"? Phil
|
In reply to this post by EstebanLM
I also have has issues with FT fonts that were not named the same on various boxes. For example, the Hack font installed a few months ago on one machine had names like "Hack-Oblique.ttf" and are not named like "Hack-Italic.ttf" on the new installs. So, there is a primitive error showing up and blocking the image. Not saying that is the cause of other troubles but there should be a way to switch back to in image fonts if such a case arises. This for sure caused me a few headaches. Phil On Tue, Jan 24, 2017 at 10:57 AM, Esteban Lorenzano <[hidden email]> wrote:
|
In reply to this post by philippeback
I’m working right now on having FFI-Kernel to work (the backend), because there are some problems with it. UFFI *should* be working right after (I already made the parts I think are needed on that side). but VM 64bits + UFFI will need testing phase… maybe your bindings would be a good starting point :) Esteban
|
In reply to this post by philippeback
yep, but this is not a VM issue. In this case is correct that primitive fails… is just that FT2 image side doesn’t know how to manage the problem :( So we need an issue with this, but I wouldn’t say is a blocking point to move latest to stable. Esteban
|
Free forum by Nabble | Edit this page |