So I had the master branch running just fine on Ubuntu 18.04, but recently had to wipe the hard drive and reinstall. Every time I run autoreconf I get the following:
I know the master branch should work fine on this computer with 18.04, and I know I lost some hair while installing it the first time, but now I can't do it again. Am I missing a library or something?
--Roy
K3RLD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just to add, the prepackaged tar version 3.3 works just fine but is missing a rotor interface that is only in the master branch (specifically the ST2 interface).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm nto sure why you're using "sudo" as the build should complete from your home directory without any privileges. Do you have the build-essentials package installed along with the autoconf, automake, and libtool packages? Since you're building from the Git master checkout, you did run the bootstrap.sh script first, right?
The README.developer file should help you get going.
73, Nate
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nate - huge thanks for the respone. Initially, I was not using sudo for the autoreconf command. It just happened to be the last thing I tried (hoping that the error was due to some permissions problem). I do believe I have all of the prerequisite packages, but I will double check today.
As fo thebootstrap.sh script - no - first I've heard of it (didn't need it the first time, strange). I was following the top level readme and INSTALL, never realized there was a developer readme. I will attempt it again later today. Thanks again!
--Roy
K3RLD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you're building from a release or daily snapshot tarball, then the bootstrap.sh step has already been done to prepare the the generation of the tarball. On a Git checkout, none of those generated files are kept in the repository as they're specific to the various Autotools versions insstalled on a given system.
README.developer is historical and is found in the top level directory of the Git checkout, but is not distributed in the tarballs. You can get the latest Git code in a handy daily snapshot tarball from http://n0nb.users.sourceforge.net/ that way you don't have to install the Autotools or run bootstrap.sh as it will build just like a release tarball.
The daily snapshots are generated via a cron job around 4:30 AM Central time (0930 or 1030z depending on US DST shift).
73, Nate
Last edit: Nate Bargmann 2019-09-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nate, thanks a million! I have control of my rig and rotators! Thanks for the education on how sourceforge works - I didn't know about the daily build tarballs and it installed with no issues whatsoever.
--Roy
K3RLD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I had the master branch running just fine on Ubuntu 18.04, but recently had to wipe the hard drive and reinstall. Every time I run autoreconf I get the following:
I know the master branch should work fine on this computer with 18.04, and I know I lost some hair while installing it the first time, but now I can't do it again. Am I missing a library or something?
--Roy
K3RLD
Just to add, the prepackaged tar version 3.3 works just fine but is missing a rotor interface that is only in the master branch (specifically the ST2 interface).
I'm nto sure why you're using "sudo" as the build should complete from your home directory without any privileges. Do you have the
build-essentialspackage installed along with theautoconf,automake, andlibtoolpackages? Since you're building from the Git master checkout, you did run thebootstrap.shscript first, right?The
README.developerfile should help you get going.73, Nate
Nate - huge thanks for the respone. Initially, I was not using sudo for the autoreconf command. It just happened to be the last thing I tried (hoping that the error was due to some permissions problem). I do believe I have all of the prerequisite packages, but I will double check today.
As fo the
bootstrap.shscript - no - first I've heard of it (didn't need it the first time, strange). I was following the top level readme and INSTALL, never realized there was a developer readme. I will attempt it again later today. Thanks again!--Roy
K3RLD
If you're building from a release or daily snapshot tarball, then the
bootstrap.shstep has already been done to prepare the the generation of the tarball. On a Git checkout, none of those generated files are kept in the repository as they're specific to the various Autotools versions insstalled on a given system.README.developeris historical and is found in the top level directory of the Git checkout, but is not distributed in the tarballs. You can get the latest Git code in a handy daily snapshot tarball from http://n0nb.users.sourceforge.net/ that way you don't have to install the Autotools or runbootstrap.shas it will build just like a release tarball.The daily snapshots are generated via a cron job around 4:30 AM Central time (0930 or 1030z depending on US DST shift).
73, Nate
Last edit: Nate Bargmann 2019-09-22
Nate, thanks a million! I have control of my rig and rotators! Thanks for the education on how sourceforge works - I didn't know about the daily build tarballs and it installed with no issues whatsoever.
--Roy
K3RLD
Glad to be of help, Roy. Now if I can get my phone working again that FUBAR'ed this morning!
73, Nate