Re: Building from Euphoria repository
- Posted by jimcbrown (admin) Jan 16, 2012
- 1127 views
I checked out the source and tried building but it threw all these errors. I swear I just did the same thing the other day on another Linux box without any problems. Both are running Ubuntu 10.04. Did I miss something?
{{{ /usr/lib/gcc/i486-linux-gnu/4.4.3/../../../../lib/crt1.o: In function `_start': (.text+0x18): undefined reference to `main' /home/greg/euphoria/source/build/intobj/back/be_task.o: In function `call_task': be_task.c:(.text+0x3a1): undefined reference to `_00' /home/greg/euphoria/source/build/intobj/back/be_task.o: In function `ctask_create': be_task.c:(.text+0x18c8): undefined reference to `_00' /home/greg/euphoria/source/build/intobj/back/be_runtime.o: In function `ctrace': be_runtime.c:(.text+0x7b3a): undefined reference to `Argc'
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.
