Dingoonity.org

First thing, you're compiling Lua. What's the point? We have already that in the rootfs, a faster version even (LuaJIT).
Second, why the hell are you compiling as root?

These are linking issues to objects within your source code directory (included lua fails to compile with an error earlier in the log?). This shouldn't have anything to do with our toolchain. Revise your building script/Makefile. Secondly, do as pcercuei said and use the lua library that comes with our toolchain.

First off, you've picked a difficult port for a beginner because GLTron is meant for OpenGL and not OpenGLES.  That means you will either need to convert it all to OpenGLES yourself, or you should base your port on another port that has already done so. 
I would guess your best bet is here:  https://github.com/lunixbochs/pandora-gltron
or here:   https://github.com/olegk0/gltron-0.7_GLES

Also, compiling larger projects made by someone else under Code::Blocks can be a pain because the original game is meant to use autoconf to generate a Makefile for you and have that compile it.   Or, they'll provide a project file for Visual C+ or something.  They rarely ever give you a Code::Blocks project file. 

You are still going to need to do a good bit of work to get those GLES ports to work on GCW, and I have a feeling you're not quite there yet experience-wise.   Especially because the resolution of the GCW is so low and also because the Pandora GLES port uses X11 to create a GLES context.  You will need to adapt that code to make a raw framebuffer context.   Sigh.. Regardless, here's the next steps...

Follow all the directions on this GCW Wiki page first:    http://wiki.surkow.com/Tutorials:CodeBlocks

At the bottom, it instructs you to add libraries to the Linker Settings tab..  From looking at GLTron's source code, I can tell you'll have to at least add the following libraries to it:
SDL
pthread
GLES_v1_CM
EGL
SDL_sound
png
z
luajit-5.1

I know other people might say otherwise, but I found I had to add this include directory to the Compiler sub-tab under the  "Search Directories" tab to get things to build, in addition to the one you already added for SDL:
/opt/gcw0-toolchain/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/include/

Reading over your response, I noticed you pointed me to two code repositories, the first one, was obviously a OpenGL ES port for use under the Pandora device, and the other what appears as a more general OpenGL ES port for Android? I assumed that it was for Android since it says that it as tested on an mk808m (an Android powered minipc). But then it states that it was merged with the first code repository for Pandora that you listed earlier. Do they both rely on X11, and / or is there a reason to choose one release over the other? Sorry if this is a 'newbie' question, but I wanted to have this clear before doing anything else.

I'm not sure which one you should choose, as I haven't looked far into it, only posted the two topmost google return search results.  However, I do know that the author of the Pandora GLTron port is also the maintainer of GLshim which often allows unmodified OpenGL programs to run directly on OpenGLES devices.  He's Lunixbochs on the Pandora forums and goes by _aegis_ on IRC chat in Freenode #gcw and #openpandora. 

If you need an example of how to set up an OpenGLES context on the GCW Zero, there's a simple example on my github page: https://github.com/senquack/lineloop      (Much credit to Pickle for example code I adapted from)  One big thing to take note of is that you do not initiate the SDL video subsystem like a normal SDL program would.  You do initialize the other SDL subsystems that you need, like audio and input. Oddly, you still use SDL_SetVideoMode() to set the screen dimensions and depth, despite having not initialized the SDL video subsystem.

You're still gonna have quite a bit of work ahead of you to make a good GCW port, though. Especially if you're not familiar that much with Linux. Good luck, though, looks like a cool game. If you decide not to do it in the end,  let us know here and someone else maybe will try to get on top of it.