I'm using the Pi 2, getting ready to do another build, been having trouble with saving the configuration file in cgminer-gekko. Think I narrowed it down to libjansson-dev, but not sure yet.
Are you sure that your config file is not damaged? If you're been cutting and copying from web pages, it might have high ASCII or other unreadable characters in it.
I don't know what platform you're on, but you probably can "clean" the text to make sure it doesn't have whacky characters in it. On the Mac there's a tool called TextWrangler (it's free) that has a "Zap Gremlins" command that removes non-ASCII characters. Very useful.
No, it's after the build and cgminer is running, when I hit "s" and "w" to save the cgminer.conf file, it quits cgminer and kicks me back to terminal.
When cgminer is running, if I hit "s" and "c" to restart cgminer that's where the fatal json error message comes up and with another message saying it can't read the cgminer.conf file (because all it makes is a blank file). Even when I fill in the cgminer.conf file with pool/s and freq, it can't read it.
I'm not sure about how to resolve the conf. file problem. BUT... Don't bother trying to "Restart" cgminer from a running instance. It is a LONNNNNnnngggggGG know fact that, that particular function "ReStart" is/has been broken. If you NEED to ReStart,
your only choice is too "Quit" and run .exe again.That's the problem, it should be as simple as just typing cd cgminer-gekko (if not already in the dir) sudo ./cgminer and have it start mining on the pool/s (after filling in the pool/s and everything "once", without any more typing.
But because it can't read/write the cgminer.conf file I have to type: sudo ./cgminer -o stratum+tcp://stratum+tcp://solo.ckpool.org:3333 -u 1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Jake36stick --compac-freq 150 every time.
Edit: that is on a Pi 2 with fresh and updated install of 2015-05-05-raspbian-wheezy on it. And scrolling back after every step of the build and seeing no errors in the build. Hmmm, that gives me an ideal, try building with out updating raspbian and see if maybe something in the updates are not compatible.
Edit 2: I have cgminer-4.9.2 running on a second Pi 2 with the same raspbian on it, but it reads/writes the cgminer.conf file, but it was done back around when 4.9.2 was first released.