Re: [Hamlib-developer] @LTLIBOBJS@

[Robert <ro...@st...>]

Hi again,

> I remember having problems with LTLIBOBJS on some automake 1.5 versions=
,
> which was known btw to be, hmm, development work. Even 1.6 is considere=
d
> so. It looks like the 1.7 is a lot more stable, with features working a=
s
> expected.
> Okay, on some system this might be a pain to upgrade to a more recent
> automake, but this what I would suggest you. I've just tested to compil=
e
> a fresh checkout, and got no problem at all (autoconf-2.54-1 and
> automake1.7.1-1).
>
> Note, --config-cache was needed with some unstable automake versions.
> Since I'm not using it any more, some I'm going to update the README fi=
le.

now my PCs are running Gentoo Linux 1.4RC1... it defaults to automake 1.4=
-p5=20
and autoconf 2.13, but setting WANT_AUTOMAKE_1_6=3D1 calls automake 1.6.3=
 and=20
WANT_AUTOCONF_2_5 calls autoconf 2.54... this finally got rid of the=20
LTLIBOBJS message... now I get

gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib -=
g -O2=20
-Wall -c ft920.c -MT ft920.lo -MD -MP -MF .deps/ft920.TPlo  -fPIC -DPIC -=
o=20
=2Elibs/ft920.lo
ft920.c: In function `ft920_set_vfo':
ft920.c:814: warning: `cmd_index' might be used uninitialized in this fun=
ction
ft920.c: In function `ft920_get_vfo':
ft920.c:924: pointers are not permitted as case values
make[1]: *** [ft920.lo] Error 1
make[1]: Leaving directory `/usr/src/hamlib/yaesu'
make: *** [all-recursive] Error 1

but that'll go away soon surely ;-)

73, Robert