<div dir="auto">Yes, Volker, the Docker image fosters an integrated approach in which your environment is within the image. It's the only way, with static linking, to avoid dependency nightmares and quickly get something that "just works" as Linus says. <div dir="auto">This is why there is an Emacs build in the image and a handful of common developer dependencies.<div dir="auto">Also, Mercury builds are more often than not static builds, unless there are external dynamic libraries used, which often causes pain at deployment stage. I tend to statically build as much as possible and then copy the build out of the image, which is super easy to do.</div><div dir="auto">FN</div></div></div> <div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le sam. 13 déc. 2025, 14:19, Volker Wysk <<a href="mailto:post@volker-wysk.de">post@volker-wysk.de</a>> a écrit : </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Fabrice, Ralph I've tried the Docker image, four months ago. I found it very confusing at first. Please note that you will have your entire development environment inside the container, when you choose to do it this way. You can copy your compiled program out of the container and use it outside, if you have linked it statically. I had tried to set things up, such that only the compiler is inside and the source code and the generated files are outside. This can be done with a bind mount inside-outside of the container. But that didn't work satisfactorily. About Fabrice's suggestion to bootstrap the compile by using the docker image, I'm not so confident that this will work easily. You need to understand Docker images for that. You can bootstrap the compiler the way it's intended by the developers. That isn't that hard. Hope this helps, Volker Am Samstag, dem 13.12.2025 um 13:53 +0100 schrieb Fabrice Nicol: > If you are comfortable with using Docker there is also a working ROTD > image dating back from about a month. It is normally updated daily to > current ROTD. > <a href="https://github.com/fabnicol/ubuntu4mercury" rel="noreferrer noreferrer" target="_blank">https://github.com/fabnicol/ubuntu4mercury</a> > > You can use this image to possibly bootstrap a build from recent source > code, should you meet problems doing so directly (this has been recently > tested). > > Fabrice Nicol > NB: For about a month the GitHub Actions process has been failing owing to > memory overload. I will have to streamline the build a little for it > continue working. > > > Le sam. 13 déc. 2025, 13:42, David Overton <<a href="mailto:david@overtons.id.au" target="_blank" rel="noreferrer">david@overtons.id.au</a>> a > écrit : > > Welcome back Ralph. I also have recently (well last year) returned to > > Mercury after a couple of decades away. > > Prince builds are using an ROTD from last February, this one in > > particular: > > <a href="https://github.com/Mercury-Language/mercury-srcdist/releases/tag/rotd-2024-02-27" rel="noreferrer noreferrer" target="_blank">https://github.com/Mercury-Language/mercury-srcdist/releases/tag/rotd-2024-02-27</a> > > So installing that ROTD from source may be a good place to start. > > > > David > > > > > > On Sat, 13 Dec 2025 at 17:34, Paul Bone <<a href="mailto:paul@bone.id.au" target="_blank" rel="noreferrer">paul@bone.id.au</a>> wrote: > > > > > > Yes, the right thing to do would be install from source. > > > > > > As you noticed, those packages & instructions are for .deb based > > > systems, and that's not Arch, it's Debian and Ubuntu. > > > > > > Good to see you again, good luck! > > > > > > On Sat, 13 Dec 2025, at 3:47 PM, Ralph Becket wrote: > > > > Hi everybody, > > > > > > > > After nearly a couple of decades using C# in industry, it looks like > > > > I'm coming back to Mercury! > > > > > > > > I'm trying to install Mercury under WSL on my home Windows box and > > > > I'm getting nowhere. (Please forgive me if I come across a touch > > > > Forest Gump: even back in the day I only had half a clue about Linux > > > > admin.) If anyone can offer advice, I'd be most grateful. I've > > > > installed Arch Linux under WSL and I'm trying to install Mercury > > > > using the instructions at Mercury packages for .deb based systems > > > > > > > > Now Arch, it seems, uses something called 'pacman' to install > > > > things, whereas the instructions refer to 'apt'. Okay, so > > > > > > > > * I install 'apt', edit /etc/apt/sources.list.d/mercury.list to > > > > include > > > > > > > > deb <a href="http://dl.mercurylang.org/deb/" rel="noreferrer noreferrer" target="_blank">http://dl.mercurylang.org/deb/</a> DISTRO main > > > > deb-src <a href="http://dl.mercurylang.org/deb/" rel="noreferrer noreferrer" target="_blank">http://dl.mercurylang.org/deb/</a> DISTRO main > > > > > > > > * I run the weird GPG thing that the document tells me to do > > > > > > > > * I run 'apt update' and then... > > > > [root@Herbert tmp]# apt update > > > > Ign:1 <a href="http://dl.mercurylang.org/deb" rel="noreferrer noreferrer" target="_blank">http://dl.mercurylang.org/deb</a> DISTRO InRelease > > > > Err:2 <a href="http://dl.mercurylang.org/deb" rel="noreferrer noreferrer" target="_blank">http://dl.mercurylang.org/deb</a> DISTRO Release > > > > 404 Not Found [IP: 45.56.89.38 80] > > > > Error: The repository '<a href="http://dl.mercurylang.org/deb" rel="noreferrer noreferrer" target="_blank">http://dl.mercurylang.org/deb</a> DISTRO Release' > > > > does not have a Release file. > > > > Notice: Updating from such a repository can't be done securely, and > > > > is therefore disabled by default. > > > > Notice: See apt-secure(8) manpage for repository creation and user > > > > configuration details. > > > > Notice: Missing Signed-By in the sources.list(5) entry for > > > > '<a href="http://dl.mercurylang.org/deb" rel="noreferrer noreferrer" target="_blank">http://dl.mercurylang.org/deb</a>' > > > > > > > > At this point I'm so far down the rabbit hole of Things I Don't Care > > > > About While Recovering From The Flu that I'm here to call for help. > > > > > > > > Is the right thing to do now to try installing from the sources > > > > instead? > > > > > > > > Anyway, looking forward to re-connecting with everyone again! > > > > > > > > Cheers, > > > > Ralph > > > > _______________________________________________ > > > > users mailing list > > > > <a href="mailto:users@lists.mercurylang.org" target="_blank" rel="noreferrer">users@lists.mercurylang.org</a> > > > > <a href="https://lists.mercurylang.org/listinfo/users" rel="noreferrer noreferrer" target="_blank">https://lists.mercurylang.org/listinfo/users</a> > > > > > > > > > > _______________________________________________ > > > users mailing list > > > <a href="mailto:users@lists.mercurylang.org" target="_blank" rel="noreferrer">users@lists.mercurylang.org</a> > > > <a href="https://lists.mercurylang.org/listinfo/users" rel="noreferrer noreferrer" target="_blank">https://lists.mercurylang.org/listinfo/users</a> > > _______________________________________________ > > users mailing list > > <a href="mailto:users@lists.mercurylang.org" target="_blank" rel="noreferrer">users@lists.mercurylang.org</a> > > <a href="https://lists.mercurylang.org/listinfo/users" rel="noreferrer noreferrer" target="_blank">https://lists.mercurylang.org/listinfo/users</a> > _______________________________________________ > users mailing list > <a href="mailto:users@lists.mercurylang.org" target="_blank" rel="noreferrer">users@lists.mercurylang.org</a> > <a href="https://lists.mercurylang.org/listinfo/users" rel="noreferrer noreferrer" target="_blank">https://lists.mercurylang.org/listinfo/users</a> _______________________________________________ users mailing list <a href="mailto:users@lists.mercurylang.org" target="_blank" rel="noreferrer">users@lists.mercurylang.org</a> <a href="https://lists.mercurylang.org/listinfo/users" rel="noreferrer noreferrer" target="_blank">https://lists.mercurylang.org/listinfo/users</a> </blockquote></div>