This is an upstream issue.

That said, there are really two problems. First, the executable cannot
be built without any graphics support. Second, it cannot be built
without WX support, using direct X11 instead. These are both upstream
issues.

This means that it isn't possible for me to work around the problem by
building two executables, a graphics-enabled one and a text-only one.
At least, not without solving the above bit rot.

The upstream problem seems simple enough: there is no configuration
option to request building without WX, and once you fix that, it
reveals a macro that uses "return" and it is used in two contexts, one
where an argument to return is required, the other where it is
forbidden. I have not fixed that yet, if I do there might be other
issues lurking.

But is logo fun without a turtle? I guess this bug needs to be solved
if we are ever to find out!

Reply via email to