I would like to propose something to the community. For those who have managed to be installed in the Raspberry Pi CQLog an image of the disk.
I've tried both Ubuntu Mate and Raspbian and I always get the same error time that I can not solve.
Fri, 2016-09-30 20:15
#1
Raspberry Pi and CQRLog
Is there still an interesting and need in working directions for CQRLog on Raspberry Pi? I have 2.0.2 working fine on a Raspberry Pi 3 using Raspbian Jessie.
I am very interested in having the latest working on the Pi3. How did you do it?
I am using 1.8.2 and have a few problems. I'm hoping 2.0.2 will work better. I am sure there are others that would like to have the latest.
Best Wishes,
Rich, K0PIR
CQRLOG 2.0.2 on PI3
My setup:
* Raspberry Pi 3B
* Raspbian 8 Jessie
* Using a USB-attached hard drive for /home, not the SD card
Assumptions:
* General working knowledge of Linux
* Using the default 'pi' user
* Raspbian setup is not broken or compiled over with custom software
* You're not using MySQL for anything else (or any of the other dependencies)
Caveats:
* I've not done any testing of this process to upgrade from a previous version of CQRLOG. Specifically I do not know what might happen to your local database when you upgrade from MySQL 5.5 to 5.6. Caveat emptor!!
NOTE: I am recreating these directions from trial and error as I don't have another Pi and/or SD card to try this install from scratch. Once we have any kinks worked out, I will start a new thread with the final directions.
WARNING: I STRONGLY SUGGEST YOU BACKUP YOUR CQRLOG DATA BEFORE BEGINNING THIS PROCESS!!
Steps:
1. Update your base Raspbian to the latest packages:
# aptitude update
# aptitude upgrade
2. Enable apt to use the jessie-backports by creating the file /etc/apt/sources.list.d/jessie-backports.list with the following contents:
deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
3. Load the new configuration:
# aptitude update
4. Install all of the non-compile pre-requisites for CQRLOG, using the jessie-backports repository for MySQL:
# aptitude install libaio1 libdbd-mysql-perl libdbi-perl libhamlib-utils libhamlib2 libhtml-template-perl libnetpbm10 libssl-dev libssl-doc libterm-readkey-perl python2.7-libxml2 trustedqsl xplanet xplanet-images
# aptitude -t jessie-backports install libmysqlclient18 libmysqlclient-dev mysql-client mysql-common mysql-server
5. Stop and disable mysql-server because CQRLOG will launch its own local server:
# systemctl disable mysql
# systemctl stop mysql
6. Install the build tools for CQRLOG - Pascal and Lazarus:
# aptitude -t jessie-backports install fpc lazarus
7. Check your installation with dpkg --list | egrep '(laz|fpc)'. You should see fpc (Free Pascal) version 3.0 and Lazarus 1.6. If you have other versions of any of the packages, remove them by version number with 'aptitude remove PACKAGE'. Do the same with dpkg --list | grep mysql and check for any MySQL that is NOT MySQL 5.6.
8. Download and unpack the CQRLOG tarball
9. **VERY IMPORTANT** Do an 'rm -rf /tmp/.lazarus' to clear our any previous build leftovers. The CQRLOG Makefile does not clean up after itself and it will not overwrite old files it finds in the temp build directory.
10. Build the software with 'make'. If you want to install it locally in your /home/pi directory rather than all over the system you can add DESTDIR=/home/pi/cqrlog to your make statement. However if you install it locally, you won't get menu items automatically. I personally did not use a local installation.
11. Install the software with 'make install'. Same caveat about DESTDIR as above.
12. Run the cqrlog from a terminal window to watch for any errors and to check on any MySQL issues.
13. Use CQRLOG
The trickest problems I had was getting the MySQL packages right and the unclean build environment in /tmp/.lazarus. I ended up having an odd mix of 5.5 and 5.6 packages. Removing all 5.5 packages and rebuilding is the fix for that. This will manifest itself either as a failure of mysqld to start as viewed in the terminal or a GUI error about a missing libmysqlclient.so. The other problem I mention above in step 9.
Thanks Jason. I'm going to give it a shot.
Best Wishes,
Rich, K0PIR
<p>My setup: * Raspberry Pi 3B * Raspbian 8 Jessie * Using a USB-attached hard drive for /home, not the SD card Assumptions: * General working knowledge of Linux * Using the default 'pi' user * Raspbian setup is not broken or compiled over with custom software * You're not using MySQL for anything else (or any of the other dependencies) Caveats: * I've not done any testing of this process to upgrade from a previous version of CQRLOG. Specifically I do not know what might happen to your local database when you upgrade from MySQL 5.5 to 5.6. Caveat emptor!! NOTE: I am recreating these directions from trial and error as I don't have another Pi and/or SD card to try this install from scratch. Once we have any kinks worked out, I will start a new thread with the final directions. WARNING: I STRONGLY SUGGEST YOU BACKUP YOUR CQRLOG DATA BEFORE BEGINNING THIS PROCESS!! Steps: 1. Update your base Raspbian to the latest packages: # aptitude update # aptitude upgrade 2. Enable apt to use the jessie-backports by creating the file /etc/apt/sources.list.d/jessie-backports.list with the following contents: deb http://httpredir.debian.org/debian jessie-backports main contrib non-free 3. Load the new configuration: # aptitude update 4. Install all of the non-compile pre-requisites for CQRLOG, using the jessie-backports repository for MySQL: # aptitude install libaio1 libdbd-mysql-perl libdbi-perl libhamlib-utils libhamlib2 libhtml-template-perl libnetpbm10 libssl-dev libssl-doc libterm-readkey-perl python2.7-libxml2 trustedqsl xplanet xplanet-images # aptitude -t jessie-backports install libmysqlclient18 libmysqlclient-dev mysql-client mysql-common mysql-server 5. Stop and disable mysql-server because CQRLOG will launch its own local server: # systemctl disable mysql # systemctl stop mysql 6. Install the build tools for CQRLOG - Pascal and Lazarus: # aptitude -t jessie-backports install fpc lazarus 7. Check your installation with dpkg --list | egrep '(laz|fpc)'. You should see fpc (Free Pascal) version 3.0 and Lazarus 1.6. If you have other versions of any of the packages, remove them by version number with 'aptitude remove PACKAGE'. Do the same with dpkg --list | grep mysql and check for any MySQL that is NOT MySQL 5.6. 8. Download and unpack the CQRLOG tarball 9. **VERY IMPORTANT** Do an 'rm -rf /tmp/.lazarus' to clear our any previous build leftovers. The CQRLOG Makefile does not clean up after itself and it will not overwrite old files it finds in the temp build directory. 10. Build the software with 'make'. If you want to install it locally in your /home/pi directory rather than all over the system you can add DESTDIR=/home/pi/cqrlog to your make statement. However if you install it locally, you won't get menu items automatically. I personally did not use a local installation. 11. Install the software with 'make install'. Same caveat about DESTDIR as above. 12. Run the cqrlog from a terminal window to watch for any errors and to check on any MySQL issues. 13. Use CQRLOG The trickest problems I had was getting the MySQL packages right and the unclean build environment in /tmp/.lazarus. I ended up having an odd mix of 5.5 and 5.6 packages. Removing all 5.5 packages and rebuilding is the fix for that. This will manifest itself either as a failure of mysqld to start as viewed in the terminal or a GUI error about a missing libmysqlclient.so. The other problem I mention above in step 9.</p>
Okay, that looked REALLY different in preview....
I don't know how, but it is working. The first time I tried to start it I get the MYSQL error you mention. Ran rm -rf /tmp/.lazarus and tried make install again. Ran it and CQRLOG 2.04 (001) started. Had my database and settings. I got rig control working (hamlib3 installed earlier) and now my Icom 7300 is working with it. On to making some contacts and getting WSJT-X and Fldigi working with remote.
Thank you so much.
Best Wishes,
Rich, K0PIR
Glad it worked.
I have to install 2.0.4 yet ... was working with 2.0.2.
Just a quick update here for other Raspberry Pi users - the procedure put forth by Jason N8JDM worked very well for me. My RPi had been running CQRlog 1.9.0 and the install / update had no issues. I had to prefix many commands with "sudo" to be sure I had privileges to run them. The only "glitch" in my case was that the tarball would not process on my RPi so I downloaded the .zip file and went with it. As a bonus, I wound up with not only a current CQRlog, but a current Raspian Jessie, too!
Bottom line is that if you want to use CQRlog on your RPi, give Jason's instructions a try.
Jim / W6JHB
Folsom, CA
Glad to hear!
A few extra points based on some e-mail feedback:
1. If you have problems with a GPG key for the jessie-backports, you need to import the key specified using:
gpg --keyserver pgpkeys.mit.edu --recv-key >>KEY ID HASH HERE<<
gpg -a --export >>KEY ID HASH HERE<< | sudo apt-key add -
where you replace ">>KEY ID HASH HERE<<" with the missing key. For jessie-backports 8 it should be 2B90D010 but it will change with every release.
2. Everywhere above I prefixed the command with the # prompt you need to do as root, either using 'su' or 'sudo'.
3. For step 8 you have to use the SOURCE CODE tarball which is in Github. The link to the Github project is on the downloads page.
Glad this is working for people.
Are you able to upload to HRDLog.net or any other? I get connect errors. "Check Internet connection" I'm connected.
Best Wishes,
Rich, K0PIR
I use LoTW and HamQTH and both have worked fine. I don't use HRDLog.net but I can confirm that general Internet connectivity works for me.
Okay, glad to hear! I'll keep looking into it.
BTW, I received your QSL card and thank you. Sending yours out.
Best Wishes,
Rich, K0PIR