Sorry about that, when I saw the "DROID" part in the "ODROID C1" I assumed it was a device running Android, which is why I suggested love-android-sdl2. Since you're running lubuntu instead of android (I thought that lubuntu was the remote machine), use the GLES branch as suggested by bart. It works nicely on my rpi.

Unsurprisingly, things have changed over the last 2 years. Love now always supports GLES out of the box, I'm not sure what error you're getting from the binary package, but GLES (2) support is in there. If you do want to compile it yourself, you can either get the source package from the downloads, where automagic has been run for you, or you can get the repo version and make sure you've installed the dev package of sdl2 properly and its autoconf macro is in the aclocal search path.

I downloaded the latest sources for SDL2 and Love2D but it doesn't work. For some reason, it tries to use OpenGL (which fails, of course) and then doesn't try GLES. I verified this by running the SDL2 tests and seeing that it uses software rendering (and not GLES). I got the usual "driver not found' errors when things ran in software mode. Love2D reported that OpenGL and GLES weren't available and would not load.

Next, I recompiled SDL2 and disabled OpenGL support. I ran the SDL2 tests and verified that it was using GLES acceleration. In this case, I got confirmation that it loaded the right driver. Then I tried Love2D but it got a fatal error and would not start.

Love2D appears to depend on SDL2 to init and open windows. I'm not sure why SDL2 doesn't fall back from OpenGL to GLES(2) but when I force GLES in SDL2, then Love2D crashes.

Ah, there's a software OpenGL implementation it prefers? That's possible, since love probes for OpenGL before GLES. You can have it prefer GLES by setting the environment variable LOVE_GRAPHICS_USE_OPENGLES to 1, or setting the define LOVE_GRAPHICS_USE_OPENGLES when compiling.