Re: [Hamlib-developer] CVS compilation problem

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

Hi Nate!

On Wed, Oct 23, 2002, Nate Bargmann wrote:
> I'm tinkering with Hamlib a bit as I'm also tinkering with the TLF
> logging program.  I'm having trouble getting register.c to compile.

Looks like CQWW is getting closer ;-)

> Here is the output:
> 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

What does your gcc command line look like? Mine is as follow:

/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I.  -I../include -I../include -I../src -I../lib -I../libltdl   -DIN_HAMLIB -DHAMLIB_MODULE_DIR=\"/usr/local/lib\" -g -O2 -Wall -c -o libhamlib_la-register.lo `test -f 'register.c' || echo './'`register.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib -I../libltdl -DIN_HAMLIB -DHAMLIB_MODULE_DIR=\"/usr/local/lib\" -g -O2 -Wall -c register.c -Wp,-MD,.deps/libhamlib_la-register.TPlo  -fPIC -DPIC -o libhamlib_la-register.lo

> Okay, so I locate the appriate line in src/register.c:
> 
> 	lt_dladdsearchdir(HAMLIB_MODULE_DIR);
> 
> Okay, nothing spectacular there so I did a grep for HAMLIB_MODULE_DIR
> and find it is defined in src/Makefile at line 112:
> 
> libhamlib_la_CFLAGS = -DIN_HAMLIB $(AM_CFLAGS)
> -DHAMLIB_MODULE_DIR=\"$(libdir)\"
> 
> Looking through the gcc man page I see that HAMLIB_MODULE_DIR is being
> defined as a macro with the value of /usr/local/lib yet I am unclear as
> to just how this makes it onto the gcc command line as the one in my
> rxvt makes no sense!

libdir is defined in Makefile.in by automake/autoconf, you can check its
value by greppig in Makefile. FYI, its value will change if you specify is
different --prefix= to ./configure.

> I've built the configuration per the directions in README.betatester and
> README.developer as I'd like to try and add my FT-920 to Hamlib.  But I
> first wanted to be sure that things build before mucking around.

Hey, great news for the FT-920! On my side, I'm going to add the FT-1000MP 
for a friend.
If you have any doubts on your cvs checkout, you may try the cvs snapshot at
http://hamlib.org/bleeding-edge/  which comes ready for ./configure && make

BTW, what are your autoconf/automake versions (--version) ? Make sure
it's at least 2.50 for autoconf, and 1.5 for automake.
Debian supports different versions, and try to autodetect. Sometimes,
it's not clever enough, and you have to run with version suffixes
"aclocal-1.7 ; autoheader2.50; automake-1.7 -a ; autoconf2.50 "
hint: modify your autogen.sh accordingly 


73s
Stephane