Nut upsuser - Feb 2014 - Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)

>
> I forgot to mention, if you don't want to deal with autoconf, etc.,
when
> building from Git, you can grab a snapshot from Buildbot:
>
>
nut-2.7.1.5.tar.gz<http://buildbot.networkupstools.org/~buildbot/cayman/snapshot/snmp_subdriver/rab7b0452e21aef8aaf308963da6380e712427e1d-146/nut-2.7.1.5.tar.gz>
>
>
Thanks a lot, I downloaded it from this link and ran commands "autoreconf
&& ./configure && make" to build it:

It says:
configure.ac:108: error: possibly undefined macro:
AC_C_FLEXIBLE_ARRAY_MEMBER
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:109: error: possibly undefined macro: AC_C_VARARRAYS
configure.ac:119: error: possibly undefined macro: AC_TYPE_LONG_DOUBLE
configure.ac:120: error: possibly undefined macro: AC_TYPE_LONG_LONG_INT
autoreconf: /usr/bin/autoconf failed with exit status: 1

I ran "autoreconf && ./configure && make" on two
Linux'es: CentOS 5 and
Enterprise Linux 5, and the output is the same on both of them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140217/3852711e/attachment.html>

On Feb 16, 2014, at 11:33 PM, ??? ????? wrote:
> 
> 
> I forgot to mention, if you don't want to deal with autoconf, etc.,
when building from Git, you can grab a snapshot from Buildbot:
> 
> nut-2.7.1.5.tar.gz
> 
> 
> Thanks a lot, I downloaded it from this link and ran commands
"autoreconf && ./configure && make" to build it:
> 
You shouldn't need to run autoreconf when building from a .tar.gz file.

What if you re-extract it, and just run "./configure && make"?

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140216/7b4e6a03/attachment.html>

>
> You shouldn't need to run autoreconf when building from a .tar.gz file.
>
> What if you re-extract it, and just run "./configure &&
make"?
>
Ok, I re-extracted and ran "./configure && make" and I guess
it built
successfully:)

....
make[1]: Leaving directory `/distr/ups/nut/nut-2.7.1.5/server'
Making all in tests
make[1]: Entering directory `/distr/ups/nut/nut-2.7.1.5/tests'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/distr/ups/nut/nut-2.7.1.5/tests'
make[1]: Entering directory `/distr/ups/nut/nut-2.7.1.5'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/distr/ups/nut/nut-2.7.1.5'

Also, config.log file says "configure: exit 0".

I am sorry for my few knowledge on compiling and building processes, since
I used to install them from rpm packages.
If it built successfully, should I install it now? I read installation
instructions at online documentation

http://www.networkupstools.org/docs/user-manual.chunked/ar01s05.html

It says, that after configuring and building, it is installed by the
following command:

make install

Is that right? I ran this command but it doesn't seem to have installed it,
maybe because of the previous installation, that I should uninstall first?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140217/28d58cdc/attachment.html>