Hi,

Speaking of this, it is worse than having to build your own. I'd
perfectly happy to do so if I could, but I do not know the secret sauce
needed so and nobody seems to know either 1.

In this particular case, I managed in the end to compile it from
generated C source 2. Now I need to back-port some fixes but again,
I do not know the secret sauce needed to build a VMMaker image.

I'd be great to fix this too (if not already).

Best, Jan

Thanks you for your time and energy fighting with this.
This is really great to have you around.

I hope that we will get out this situation with a nicer infrastructure.

S

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

a small update. I managed in 20 minutes to create a Dockerfile that seems to work:

Dockerfile for building pharo-10 branch under ubuntu 22.04

FROM ubuntu:22.04

RUN
apt-get update &&
apt-get install -y wget curl unzip inetutils-ping gnupg libcurl3-gnutls &&
apt-get install -y
build-essential
cmake
git
python3-minimal
pkg-config
libgit2-dev
libssh-dev
libsdl2-dev
libfreetype-dev
libffi-dev &&
rm -rf /var/lib/apt/lists/*

WORKDIR /opt

RUN mkdir -p /opt/src
WORKDIR /opt/src
RUN git clone https://github.com/pharo-project/pharo-vm.git && cd pharo-vm && git checkout pharo-10
RUN cmake -S pharo-vm -B pharo-vm-build
RUN cmake --build pharo-vm-build --target install
RUN rm -rf pharo-vm-build/build/dist/pharo-vm
RUN mv pharo-vm-build/build/dist /opt/pharo-vm
RUN rm -rf pharo-vm-build pharo-vm

Doing a

docker build .

in that directory builds the vm and installs it under /opt/pharo-vm/pharo

In the end it copies the files to a special place. But this could also be a way to zip them and put them somewhere else. The most simple use would be to have a Dockerfile per combination OS-pharoVmVersion. Maybe this would work on github. If I find time I might try somethig along that line. That would make zeroconf survive and still we can support a bit more. Of course it duplicates some work on the OBS but that deals with much more to integrate in the system. For me two uses cases.

What I do now is that the Dockerfile above builds and installs the vm in the docker image. I upload these and make them the basis of my docker builds so this is the closest I could get and apart from obstacles that might occur it works.

Just in case some has interests in the Dockerfile or volunteering building a repo with those Dockerfiles.

Norbert

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

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

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

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