fail to build `amuse-mesa-r2208` and some other pkg

[Yang-Taotao]

Describe the bug

The following packages failed to build:

• amuse-aarsethzare
• amuse-fractalcluster
• amuse-galactics
• amuse-krome
• amuse-mesa-r2208

To Reproduce

Steps to reproduce the behavior:

• Clone and checkout v2025.9.0
• Run ./setup install all
• Profit

Expected behavior

Listed pkg should build/install without issue, other than amuse-mesa-r15140 which is stated to only be installable in develop mode.

Logs

Log files attached.

• install-amuse-mesa-r2208.log -> exit code 0
• distclean-amuse-aarsethzare.log -> exit code 0
• distclean-amuse-fractalcluster.log -> exit code 0
• distclean-amuse-galactics.log -> exit code 0
• distclean-amuse-krome.log -> exit code 0

Environment (please complete the following information):

• OS and version: CachyOS Linux on 6.19.3-2-cachyos kernel
• Compiler: gcc (conda-forge gcc 13.4.0-17) 13.4.0, clang version 21.1.8

[LourensVeen]

Hi Yang,

Looking at the MESA r2208 log, it seems that this is from a second attempt at building, and that something went wrong when downloading the MESA source code on an earlier attempt. Possibly the download failed due to network problems, or due to a lack of disk space.

Could you check that you have enough disk space available (AMUSE requires about 2GB IIRC, and MESA is huge unfortunately), and then remove the broken file using

rm /home/tyang/Projects/amuse/src/amuse_mesa_r2208/mesa_r2208.zip

and then try to build it again using

~/Projects/amuse/$ ./setup install mesa_r2208

That will see that the file is missing and try to download it again.

To see what's wrong with the others, I'll need the installation log files for them as well. Those have names starting with install, rather than distclean, e.g. install-amuse-aarsethzare.log. Could you attach those as well?

[Yang-Taotao]

Hi Lourens,

Thanks! I've attached the wrong .log by mistake. Here are the ones generated after the following, all under an activated conda environment for amuse:

cd ~/Project/amuse
./setup install all

The .log:

• install-amuse-mesa-r2208.log -> exit code 2
• install-amuse-aarsethzare.log -> exit code 2
• install-amuse-fractalcluster.log -> exit code 2
• install-amuse-galactics.log -> exit code 2
• install-amuse-krome.log -> exit code 2

Prior to attempting ./setup again I noticed that there's a empty mesa_r2208.zip at the directory you have listed. I did:

rm /home/tyang/Projects/amuse/src/amuse_mesa_r2208/mesa_r2208.zip
./setup install mesa_r2208

This gives:

Checking for dependencies, one moment please...

Package amuse-mesa_r2208 was not found.
Please run ./setup to show enabled packages.

And I'm looking at a 403 error in terminal/log output for mesa_r2208 install.

Hope this helps!

[LourensVeen]

Ah, so that sounds like there's a server problem for MESA r2208. I'm a bit confused that the download error doesn't show up in the log file, that's something for me to look at as well.

The other codes are both missing an f77 command, which is an issue that I've seen before (the Conda compilers don't have it) and that I thought I'd fixed.

Okay, this can all be fixed. I'll be back in Leiden on Tuesday, and I'll have a look at this then and we'll get you going, does that work?

[Yang-Taotao]

Yep, sounds perfect. I should be around on Tuesday next week also. Enjoy the weekend!

[LourensVeen]

I've looked at the f77 thing, and I'm wondering: do you have the FC environment variable set to f77 by any chance? If so, that would cause those problems, since the AMUSE installer will use that instead of detecting the compiler, and since the conda-forge compilers don't have an f77 command things will break.

I've just tested the MESA r2208 download, and it's downloading fine. It comes from Zenodo, which should have reliable infrastructure. So I'm a bit confused on that one still, and we should probably try to debug it on your laptop.

[LourensVeen]

I've sent you a message via the Observatory Slack, if you want to come by.

[LourensVeen]

Update: I've now been able to reproduce the download problem. It looks like it's because we're passing an empty User-Agent header.

That's actually required for downloading some other MESA files from their server, and it used to work fine on Zenodo, but not anymore. Possibly Zenodo have tightened their restrictions to keep the wave of AI companies tearing up the Internet at bay.

I can fix this in the AMUSE installer though, so I'll do that.