- Pharo-vm - lists.pharo.org

Pharo Mailinglist moved to new setup: pharo-vm@lists.pharo.org

by Marcus Denker

We have moved the Pharo Mailinglists to a new setup. WARNING: We sadly could not migrate the settings for the subscribers (e.g. Digest) Please sign up at http://lists.pharo.org/accounts/signup to create an account to configure the lists as you need them. WARNING: one state *not* migrated includes "NO MAIL", this was used e.g. by people to send with different From:, but in addition, it seems that the old system did put subscribers with delivery problems in this state (without anyone getting notified). If you do not want to be in this list, please unsubscribe, see footer or just send a mail to me, I will remove you. Marcus

July 30, 2026

Fwd: IWST deadline extension

by Guillermo Polito

Apologies for multiple receptions! > DÃ©but du message rÃ©expÃ©diÃ© : > > De: Guillermo Polito <guillermopolito(a)gmail.com> > Objet: IWST deadline extension > Date: 28 mars 2025 Ã 5:08:37â¯PM UTC+1 > Ã: Gordana Rakic via Esug-list <esug-list(a)lists.esug.org> > > Dear all, > > due to several requests, we have extended the submission deadlines for the call for presentations. > Please check the info below: > > -------- > > IWST is the International Workshop on Smalltalk Technologies. The goal of the workshop is to create a forum around contributions and experiences in building or using technologies related to Smalltalk. While the maturity of presented ideas and results is not crucial, their presentation is expected to trigger discussion and exchange of ideas. The topics of your paper can be on all aspects of Smalltalk, theoretical as well as practical. Authors are invited to submit research articles or industrial papers. > > https://esug.org/2025-Conference/IWST2025.html > > This year we will again have two different tracks: > > Two-Round Paper Submission. As in the previous year, submission will be in two rounds: > Extended abstracts are submitted to present at the conference > Later, full/short papers are submitted for proceedings publications > > Presenting Previously Published Works. We also invite authors of contributions related to IWST's topics, accepted for publication in Journals and Proceedings of top-rated international conferences within the previous 2 years, to submit an abstract and present their published results to the IWST workshop collocated with ESUG. Authors will be invited to present their paper after checking that the submission meets the above criteria. Having the submissions already reviewed and accepted by the peers, they will not be reviewed again for technical content. > Important Dates > > Extended abstract submission deadline: April 7th, 2025 > Already Published Papers Abstract submission deadline: April 7th, 2025 > Extended abstract notification deadline: April 14th, 2025 AoE > > Already Published Papers Abstract notifications: April 14th, 2025 AoE > Full/short paper submission deadline: May 19th, 2025 AoE > > Workshop: July 1-4, 2025 > > Best regards, > IWST team

March 28, 2025

Re: [Pharo-users] New VM Release v10.3.3

by Domenico Cipriani

Thanks a lot ! I am going to test it with Coypu and Phausto. peace. d On Thu, Jan 16, 2025 at 10:28â¯AM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi all, > > Weâve published a new VM release (v10.3.3) to be used with Pharo versions > 10 through 13. > > 10.3.3 includes all changes in 10.3.2 (that was rolled back) plus several > improvements. > > Highlights: > - improves the naming schema of built artifacts to differentiate releases > from intermediate/nightly builds > - is built on the old file server (that we recovered!) to support > compatibility with older GLibC versions > - builds and run properly on newer linux systems (we fixed a couple of > linking and compilation issues with newer versions of gcc) > - many improvements in the perm space > > Please find in the wiki information about the build and versions > > https://github.com/pharo-project/pharo-vm/wiki > > Full release changes log > https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.3 > > Finally, a big thanks to MaxLeske and Norbert for testing, and to > everybody who contributed even in the previous conversations. > > Cheers, > G

Jan. 20, 2025

Re: [Pharo-users] New VM Release v10.3.3

by stephane ducasse

Thanks a lot for you dedication and positive energy around this important artefact. S > On 16 Jan 2025, at 10:27, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > Weâve published a new VM release (v10.3.3) to be used with Pharo versions 10 through 13. > > 10.3.3 includes all changes in 10.3.2 (that was rolled back) plus several improvements. > > Highlights: > - improves the naming schema of built artifacts to differentiate releases from intermediate/nightly builds > - is built on the old file server (that we recovered!) to support compatibility with older GLibC versions > - builds and run properly on newer linux systems (we fixed a couple of linking and compilation issues with newer versions of gcc) > - many improvements in the perm space > > Please find in the wiki information about the build and versions > > https://github.com/pharo-project/pharo-vm/wiki > > Full release changes log > https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.3 > > Finally, a big thanks to MaxLeske and Norbert for testing, and to everybody who contributed even in the previous conversations. > > Cheers, > G StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Jan. 20, 2025

New VM Release v10.3.3

by Guillermo Polito

Hi all, Weâve published a new VM release (v10.3.3) to be used with Pharo versions 10 through 13. 10.3.3 includes all changes in 10.3.2 (that was rolled back) plus several improvements. Highlights: - improves the naming schema of built artifacts to differentiate releases from intermediate/nightly builds - is built on the old file server (that we recovered!) to support compatibility with older GLibC versions - builds and run properly on newer linux systems (we fixed a couple of linking and compilation issues with newer versions of gcc) - many improvements in the perm space Please find in the wiki information about the build and versions https://github.com/pharo-project/pharo-vm/wiki Full release changes log https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.3 Finally, a big thanks to MaxLeske and Norbert for testing, and to everybody who contributed even in the previous conversations. Cheers, G

Jan. 16, 2025

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 11.12.2024 um 15:51 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi Norbert, the patch has not been merged yet. > > Are we talking about the same? > > the pharo-10 branch still has the issue The PR looks much better. But now I notice that with the compile and install options documented on github the vm in build/dist does not include some libraries, e.g, libcrypto.* libssl.* etc. How is the packaging done for the archives on files.pharo.org? thanks, Norbert > >> Le 11 dÃ©c. 2024 Ã 3:50â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> >> >>> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: >>> >>> >>> >>>> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >>>> >>>> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >>>> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >>>> - run locally the failing tests >>>> >>>> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >>>> >>> It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. >>> >>> In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. >>> Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) >>> >> Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas >> >> Norbert >

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 11.12.2024 um 15:51 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi Norbert, the patch has not been merged yet. > > Are we talking about the same? > > the pharo-10 branch still has the issue Ah right, I think I got so confused throughout the day that reading the PR made me think it has been merged already. Will try with the PR branch. Norbert > >> Le 11 dÃ©c. 2024 Ã 3:50â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> >> >>> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: >>> >>> >>> >>>> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >>>> >>>> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >>>> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >>>> - run locally the failing tests >>>> >>>> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >>>> >>> It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. >>> >>> In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. >>> Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) >>> >> Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas >> >> Norbert >

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Guillermo Polito

Hi Norbert, the patch has not been merged yet. Are we talking about the same? the pharo-10 branch still has the issue > Le 11 dÃ©c. 2024 Ã 3:50â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > > >> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >> >> >>> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >>> >>> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >>> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >>> - run locally the failing tests >>> >>> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >>> >> It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. >> >> In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. >> Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) >> > Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas > > Norbert

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: > > > >> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >> >> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >> - run locally the failing tests >> >> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >> > It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. > > In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. > Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) > Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas Norbert

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you > - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 > - run locally the failing tests > > This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. > It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) If you want me to test somethig please just say so. Norbert

Dec. 11, 2024