make package-windows results in never-ending make loop

[lukebakken]

Describe the bug

I used to be able to do the following to build the Windows .exe installer:

cd rabbitmq/rabbitmq-server
make RABBITMQ_PACKAGING_REPO=$HOME/development/rabbitmq/rabbitmq-packaging package-windows

...but now it gets caught in a never-ending loop. I will attach a verbose make log.

Reproduction steps

git clone https://github.com/rabbitmq/rabbitmq-server.git
git clone https://github.com/rabbitmq/rabbitmq-packaging.git
cd rabbitmq-server
make RABBITMQ_PACKAGING_REPO=../rabbitmq-packaging package-windows

Expected behavior

Windows release artifacts are built.

Additional context

Current toolset:

elixir          1.18.4
erlang          27.3.4.2
make            GNU Make 4.3

OS is Ubuntu 24

[lukebakken]

It's strange because I see the same behavior when I presumably run the same commands as the release workflow, aka

gmake source-dist

...followed by...

gmake package-windows

[lukebakken]

Here is the verbose output when I run...

make RABBITMQ_PACKAGING_REPO=../rabbitmq-packaging package-windows V=2 2>&1 | tee /tmp/make-package-windows.txt

make-package-windows.txt

I will continue looking into this. I've always gotten the has modification time XXXX s in the future messages but now maybe they are showing that make thinks a target is really always out-of-date.

[lukebakken]

@michaelklishin I have no idea why you converted #14440 into this discussion. It is a legitimate bug, introduced in this commit - e435bc6

The only reason we have not seen this behavior until now is due to the recent-ish changes in how Elixir escripts are created, coupled with someone (me) wanting to build release artifacts on a non-UTC system, or in a timezone that is not UTC. Perhaps I'm the only person who does this on Earth 🌎