Gregory Haerr

Hello @Ellis2781, This usually means that the console isn't actually compiled or booted for graphics mode. > killing my initial xorg session I still get this same error. The Xorg...

Hello @lighth7015, Are you using `make -f Makefile_nr ARCH=DOS` to build it? This portion is contributed and maintained by @georgp24, lets see what he has to say.

> So `nano-x` and `nx11` both compile, That's good news, as we'll need to find/use the files in "drivers/scr_xxx.c, mou_xxx.c, and kbd_xxx.c to get the demo apps linked (see below)....

> And turning off FT2 makes no difference for compiling landmine. FT2 isn't required, and if configured out, all programs will use core text-based or simpler fonts instead. For the...

> `nanox/error.c` is missing (or was removed) from trunk That file used to define `GdError`, which has now been moved, along with many of the other system-dependent functions, to `drivers/osdep.c`....

Yes, it seems that these calls to __rtdc are being generated by the compilation of the libraries, not in the final link command line you reported above. So look at...

> Like I was interested in seeing if I could port FOX. NX11 has a large number of X11 routines mplemented, but few extensions. The easiest way to start is...

> Okay, here are the 'undefined' X11 symbols Looks like that's the complete list without NX11 or X11. Link with '-lNX11 -lnano-X'.

Not too bad, really. To sort into categories: - Xft\* - this is the freetype extension for X11, I think. You would need to draw implement each of these routines....

It would be far easier to start with a less complicated X11 application, IMO.