[Hamlib-developer] Re: hamlib compilation problems

[Stephane F. <f8...@fr...>]

Ernie, David,

It seems you got the same problems at the same time.
Hence my reply is Cc:'d to the list.

On Sun, Sep 22, 2002, Ernest Stracener wrote:
> 
> In trying to compile the cvs snapshot (under RH7.3), I receive the following:
> gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib 
> -I../libltdl -D_GNU_SOURCE -g -O2 -Wall -Wp,-MD,.deps/register.pp -c 
> register.c  -fPIC -DPIC -o .libs/register.lo
> register.c: In function `rig_load_backend':
> register.c:297: `HAMLIB_MODULE_DIR' undeclared (first use in this function)
> register.c:297: (Each undeclared identifier is reported only once
> register.c:297: for each function it appears in.)
> make[1]: *** [register.lo] Error 1
> make[1]: Leaving directory `/home/ernie/CVS/hamlib/src'
> make: *** [all-recursive] Error 1
 
Okay, this is because you're using automake-1.4, which is too outdated
for Hamlib. Version at least 1.5 is required. Some systems have both 
installed. Unfortunately, the autogen.sh is not clever enough to handle 
this case. Therefore, either you have only the following version
installed:

	* autoconf >= 2.50	(I have 2.53)
	* automake >= 1.5	(1.6.3)
	* libtool  >= 1.4.2	(1.4.2)

Version are listed in README.developer (has to be moved to betatester),
and you can get version by running "autoconf --version" and so on.

On some systems like Debian, which have different versions installed,
You can run:

	$ aclocal-1.6
	$ autoheader2.50
	$ automake-1.6 -a
	$ autoconf2.50
	$ ./configure .....
	
I can update autogen.sh with these, but who knows if names are different
in other distros. If someone has a solution, I'll go with it!


Let me know how it works this time.

73's
Stephane