The editor I use is able to jump to source lines with errors if you run the make command inside it (I use vim, but I'm sure emacs would do the same). But I usually don't bother with this. I just run make in another terminal, look at the line number in the error output, and jump there in the editor. It's no big deal. Honestly, fixing compiler errors is a tiny part of the time it takes me write a program. Fixing logical errors is where most of my time is spent.
I haven't looked at calcplus yet, although it is on my list of things to do. However, I've never even used the default calculator on the PB device yet, so I'm not in a big hurry. I think I should put learning how to multi-quote somewhere higher on my list.
I use Slackware linux, and 32-bit compatibility libraries aren't part of the standard distribution. Eric Hameleers has made some packages and scripts available for creating your own 32-bit compatibility packages, and I have used them in the past (when Adobe's flash was only available as a 32-bit executable). However, the packages caused subtle problems when building 64-bit programs on my system (mostly through the pkgconfig system, and similar type configuration systems), so I just removed them. I've been using VirtualBox to run a 32-bit Slackware system for those times when I really need it, and that's where I've been building my PocketBook programs so far.
Anyway, I think I'll try building my own 64-bit cross-compiler suite and remove the need for the 32-bit compatibility libraries. The emulation stuff won't work, but that's okay for me.