Thread: [Hamlib-developer] Shared library support broken?
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: Ken K. <n7...@al...> - 2002-10-29 00:04:15
|
Is anyone else having problems compiling the latest CVS and getting share= d libraries? My build insists on creating only static libraries. Going ba= ck to 1.1.3 works fine. =20 It's been some months since I last played with hamlib and I want to get=20 caught up and add in some of my Ten-Tec Pegasus changes but right now I can't even get the compile back to where it was. Ken, N7IPB |
|
From: Nate B. <n0...@ne...> - 2002-10-29 00:43:06
|
* Ken Koster <n7...@al...> [2002 Oct 28 18:10 -0600]:
> Is anyone else having problems compiling the latest CVS and getting shared
> libraries? My build insists on creating only static libraries. Going back
> to 1.1.3 works fine.
Well, I had trouble last week, but my tools were outdated. Be sure your
automake and autoconf are newer than the listed versions in
README.betatester. Now, whether that is the cause of static libs, I'm
not sure. I've compiled the CVS Hamlib several times in the past few
days and have gotten shared libs each time along with the static libs.
> It's been some months since I last played with hamlib and I want to get
> caught up and add in some of my Ten-Tec Pegasus changes but right
> now I can't even get the compile back to where it was.
I've been building from anonymous CVS, not the copy I check out with my
SF userid. So you might try a new copy from anonymous CVS.
73, de Nate >>
--
Wireless | Amateur Radio Station N0NB | "We have awakened a
Internet | n0...@ne... | sleeping giant and
Location | Bremen, Kansas USA EM19ov | have instilled in him
Amateur radio exams; ham radio; Linux info @ | a terrible resolve".
http://www.qsl.net/n0nb/ | - Admiral Yamomoto
|
|
From: Ken K. <n7...@al...> - 2002-10-29 17:05:34
|
Problem found. On a SuSE 8.0 system with the standard install config.guess is coming up = with i686-suse-linux. The old config.guess from the 1.1.3 release came up wit= h i686-pc-linux-gnu. Configure is expecting to find anything with 'linux-g= nu' as the canonical name. For now I've just replaced the new config.guess with a copy from 1.1.3. There is also another bug with the configuration. Autogen.sh expects to find a copy of config.h.in in the include directory. After a fresh CVS=20 checkout there is no such file, so I had to comment out that part of auto= gen to get things to build. Ken, N7IPB |
|
From: Stephane F. <f8...@fr...> - 2002-10-29 22:46:15
|
Hi Ken, This is great news for the Ten-Tec Pegasus. On top of that, we have the full documentation. Some issues still need to be addressed, like the transmit watchdog (some kind of SIGALARM and sighandler?), but nothing that can't be worked out! On Tue, Oct 29, 2002, Ken Koster wrote: > On a SuSE 8.0 system with the standard install config.guess is coming up with > i686-suse-linux. The old config.guess from the 1.1.3 release came up with > i686-pc-linux-gnu. Configure is expecting to find anything with 'linux-gnu' > as the canonical name. > > For now I've just replaced the new config.guess with a copy from 1.1.3. yep, config.guess and config.sub are no more under cvs. So your system (ie. autotools-dev package or automake) must have some kind of recent ones. you can check with "./config.guess --version" and "./config.sub --version". Date of this year should be okay. Anyway, you've raised an good point. I've updated README.developer and README.betatester to be more explicit about versions. In the mean time, I've upgraded libtool to 1.4.3, which fixes couple of bugs, but not the ones you were expecting. > There is also another bug with the configuration. Autogen.sh expects to > find a copy of config.h.in in the include directory. After a fresh CVS > checkout there is no such file, so I had to comment out that part of autogen > to get things to build. oops, sorry, I did some cleanup without doing a full check afterwards. Anyway, that gave me the opportunity to improve a little bit the autogen.sh script. Modify to your own need! Thanks for the report and fixes. Stephane |
|
From: Ken K. <n7...@al...> - 2002-10-30 03:49:26
|
On Tuesday 29 October 2002 14:46, Stephane Fillod wrote: > Hi Ken, > > This is great news for the Ten-Tec Pegasus. On top of that, we have the > full documentation. Some issues still need to be addressed, like the > transmit watchdog (some kind of SIGALARM and sighandler?), but nothing > that can't be worked out! The assumption in the existing code appears to be that the Pegasus was=20 the same as the RX320 and it's not. Almost everything has subtle differe= nces so I've got a lot of work to do. I've already fixed up the code for=20 RIG_LEVEL_AF, RIG_LEVEL_SQL and RIG_LEVEL_RF. I'm working on the freque= ncy control now. The transmit side will come later, there doesn't appear to = be=20 any support for TX at all. =2E.. > Thanks for the report and fixes. You're welcome. more to follow as I find time to work on it. Ken, N7IPB |