The specific example here is that, when running make_conf in a Docker build, it comes up with machine 6076aea5b9f3, which starts with a number and is therefore not valid.
There are three ways I can think of to fix this:
Relax ACT IDs so that they can start with a number (they take this restriction from C identifiers, but aren't C identifiers, so maybe it's just not necessary? This might cause lexing problems later on where, say, 2836 and 2721.1234 are both valid number literals and ACT identifiers;
Escape the hostname before using it in make_conf;
Don't use the hostname at all, and just emit local or similar as the machine name. This is probably the easiest.
The specific example here is that, when running
make_confin a Docker build, it comes up withmachine 6076aea5b9f3, which starts with a number and is therefore not valid.There are three ways I can think of to fix this:
make_conf;localor similar as the machine name. This is probably the easiest.