OpenEuphoria

I've seen this before, when I run configure from a new branch and forget to pass the -eubin option to tell it where the current version of 4.1 eui is located.

If eui is installed in the path somewhere, and is executable, the configure script will run it and detect that it works, in which case it uses that eui to do the translation. (4.0.3's eui can't build the 4.1 code, you need to use an eui from the head of the 4.0 branch to build a working 4.1 eui.) If it can't find eui, then it assumes that you are using pre-translated source code and sets up the Makefile to only compile the C code. (The configure script doesn't bother to check to see if pre-translated source code exists at this point.)

In this case, the Makefile tries to build only the backend custom .c files which exist, and then tries to link the executable without any of the code that defines the front-end side symbols (such as _00 or Argc). That code doesn't exist because we never ran eui to translate the front-end into C, so the build fails.

If you only have 4.0.3 or earlier and don't want too much hassle in getting a workable eui for the translation step, you can just grab a 4.1.0 eubin use that to build the latest code.

http://openeuphoria.org/eubins/linux/4.1.0/32-bit/eubin-2011-06-29-3739d931e005.tar.gz