similar to: Error installing Nut 2.7.2 on RedHat 6.6

Displaying 20 results from an estimated 2000 matches similar to: "Error installing Nut 2.7.2 on RedHat 6.6"

2008 Aug 15
2
Problem with APC and Fedora 8 I86_64
I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via
2007 Mar 06
3
make errors on solaris express dev 02/07
make fails at drivers: make[1]: Entering directory `/export/home/zoly/Documents/trunk/drivers' /bin/sh ../libtool --tag=CC --mode=link gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare -o al175 al175.o ../common/libcommon.a ../common/upsconf.o
2007 May 24
7
Debian package
Seems to be broken in the current SVN: [...] x86_64-linux-gnu-gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I. -I/usr/include -O2 -Wall -Wsign-compare -s -o energizerups energizerups.o ../common/upsconf.o ../common/parseconf.o ../common/state.o main.o dstate.o
2013 Jul 02
0
Installing NUT on Solaris
On Mon, 2013-07-01 at 15:42 -0800, John Thurston wrote: > On 7/1/2013 2:55 PM, Charles Lepple wrote: > > On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > > > >> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. > >> > >> Can anyone
2013 Jul 01
3
Installing NUT on Solaris
On 7/1/2013 2:55 PM, Charles Lepple wrote: > On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > >> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. >> >> Can anyone share a how-to for solaris? > > Here's some general NUT-on-Solaris
2013 Jul 05
1
Installing NUT on Solaris
On 7/1/2013 8:27 PM, Bernd Markgraf wrote: > On Mon, 2013-07-01 at 15:42 -0800, John Thurston wrote: >> On 7/1/2013 2:55 PM, Charles Lepple wrote: >>> On Jul 1, 2013, at 12:47 PM, John Thurston wrote: >>> >>>> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the
2008 Apr 30
0
[Fwd: Re: openSUSE 11.0 - NUT]
Stanislav Brabec wrote: > Please note that 2.2.2-pre3 installs hald addons by default to / on > openSUSE 11.0 beta 2 x86_64. Not a big problem. Here is a patch, which fixes openSUSE 11.0 beta 2 x86_64: --- m4/nut_check_libhal.m4 +++ m4/nut_check_libhal.m4 @@ -63,7 +63,7 @@ dnl As per HAL spec, ?5 Callouts and ?2 Device Information Files dnl - addon install path: $libdir/hal
2008 Feb 24
1
nut-subversion Tripp Lite 750AVR
Hi, i new on this list i don't know if this goes on development list or this list,? i have a ups Tripp Lite 750AVR(lusb info in the attach)? , i retrieve the current development tree from the subvervsion repo, and trying to compile NUT on Fedora8 to test the usb driver. the configure is ok: Configuration summary: enable SSL development code: yes enable IPv6 support: yes build
2006 Jul 22
1
Error during make: *** No rule to make target `usb.h', needed by `tripplite-hid.o'. Stop.
I downloaded the latest development tree (revision 471), ran configure with the following command: ./configure --with-user=nut --with-drivers=tripplite-hid make The common directory is built normally, then when it tries to make the drivers, I get this error: make[1]: *** No rule to make target `usb.h', needed by `tripplite-hid.o'. Stop. I get this error when I try to build any usb or
2015 Mar 09
2
Install problems (group permissions) with nut 2.7.2
Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c
2015 Mar 09
0
Install problems (group permissions) with nut 2.7.2
Sorry for the bad formatting of the previous message...I tried to use plus signs as bullet points, and that caused a problem somehow. Ok...I discovered that if I do the autoreconf after the first failed make (and the autoreconf still gives that error message), and then do make again...it builds. Conclusions: 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c
2008 Feb 08
1
Building NUT 2.2.1 under Solaris 10 (SPARC)
I'm trying to build NUT 2.2.1 on a SunBlade 2000 running Solaris 10 (Solaris 10 11/06 s10s_u3wos_10 SPARC) It won't compile. I'm not a programmer, so I'm afraid I don't know why... [huge at anubis ~/Prog/nut/nut-2.2.1]: ./configure --with-user=ups --with-group=nutNetwork UPS Tools version 2.2.1 checking build system type... sparc-sun-solaris2.10 checking host system type...
2006 May 20
1
building a library for common/ [was: minor building issues (svn HEAD revision 427)]
NUT developers, I'm looking for a low-tech solution for this linker error: > gcc -I../include -O -Wall -Wsign-compare -g -Dsolaris2 > -I/software/openssl-0.9.7_runtime/include -I. > -I/software/netsnmp-5.3/include -o snmp-ups snmp-ups.o main.o dstate.o \ > ../common/state.o ../common/upsconf.o ../common/parseconf.o \ > ../common/common.o ../common/setenv.o
2015 Jul 08
1
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
Hi Charles, Yes, it looks like my g++ does contain STL library which might be just my specific case... However, as a temporary solution I disabled nutclient in Makefile (please find the file attached). And nut-2.7.3 can be compiled now. Thanks, Sergey On Wed, Jul 8, 2015 at 4:13 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 6, 2015, at 10:32 AM, Sergey Talchuk
2008 May 02
1
nut: simplification of the automake stuff
Hallo. Here is a simplification of the automake stuff for nut 2.2.2. The idea is simple: libcommon.a contains stuff for the binaries libparseconf.la contains stuff for binaries and shared library Both are NOINST, automake understands perfectly our intentions. The rest is only a removal of the implicitly defined stuff. On top of the parallel build patch I got build success on all platforms
2005 Aug 17
0
Re: Problems compiling snmp-ups on Solaris
Hello Kim, First, I've forwarded your mail to the nut user mailing list. Thanks to register there (https://alioth.debian.org/mail/?group_id=30602) and we'll follow on the thread on it. > Terribly sorry to bother you, but I was hoping to get nut to work with > our Symmetra, which uses SNMP. nut-2.0.2 built fine on my Solaris 8 box, > but when I do "make build-snmp" it
2007 Jan 12
2
Makefiles driving me NUTs
I want to use upsdebugx, upslogx in 'clients/upsclient.c', however this fails with the following error messages (I trimmed the path to the build directory to <path> in order to prevent line wrapping): <path>/clients/upsclient.c:941: undefined reference to `upsdebugx' <path>/clients/upsclient.c:910: undefined reference to `upslogx'
2006 May 19
3
minor building issues (svn HEAD revision 427)
While attempting to package up the HEAD version of nut for our department/campus, I've run into a couple of minor issues with the latest HEAD - I'm going to give it another whack at a PW9170+ UPS and want to make sure I have the latest revision. :) First is, whilst building the drivers (SNMP required), I get: gmake[1]: Entering directory `/fsys2/source/nut-2.1/nut-2.1_cvs/drivers'
2005 Jun 23
1
USB UPS Question...
Hello, I have been trying to get a TrippLite Internet Office 750 UPS to talk to my Linux PBX for a couple of evenings now and I'm getting nowhere... I tried searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is
2015 Oct 19
0
upsmon Poll UPS "Driver not connected" messages
I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I am testing implementation of NUT features with APC and Tripp-Lite USB UPS interfaces. Things are going reasonably well. However, I'm seeing many more messages than I would like in /var/log/messages when I boot the system without the UPS connected. I have configured NOCOMMWARNTIME 3600, which takes care to only broadcast