search for: parseconf

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

Stan, I'm very pleased to see you back to work with us on enhancing nut in that many areas ;-) 2008/4/30 Stanislav Brabec <sbrabec at suse.cz>: > 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:

[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >

...t --with-statepath=/var/ups --with-user=ups --with-group=ups returns alright, but the subsequent "make" fails with: > make[1]: Entering directory `/opt/downloads/nut-2.6.5/common' > /bin/bash ../libtool --tag=CC --mode=link gcc -I../include -g -O2 -Wall -Wsign-compare -o libparseconf.la parseconf.lo -lrt -lsocket -lnsl > libtool: link: false cru .libs/libparseconf.a .libs/parseconf.o > make[1]: *** [libparseconf.la] Error 1 But at this point I don't know if I have some library in the wrong location, or if the makefile is being told to look in the wrong location,...

...common.o ranlib libcommon.a gcc -DHAVE_CONFIG_H -I. -I../include -I../include -O -Wall -Wsign-compare -MT upsconf.o -MD -MP -MF .deps/upsconf.Tpo -c -o upsconf.o upsconf.c mv -f .deps/upsconf.Tpo .deps/upsconf.Po gcc -DHAVE_CONFIG_H -I. -I../include -I../include -O -Wall -Wsign-compare -MT parseconf.o -MD -MP -MF .deps/parseconf.Tpo -c -o parseconf.o parseconf.c mv -f .deps/parseconf.Tpo .deps/parseconf.Po gcc -DHAVE_CONFIG_H -I. -I../include -I../include -O -Wall -Wsign-compare -MT state.o -MD -MP -MF .deps/state.Tpo -c -o state.o state.c mv -f .deps/state.Tpo .deps/state.Po /bin/sh ../lib...

...e[1]: Leaving directory `/home/artesano/Downloads/nut-2.7.2/include' Making all in common make[1]: Entering directory `/home/artesano/Downloads/nut-2.7.2/common' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../include -I../include -g -O2 -Wall -Wsign-compare -MT parseconf.lo -MD -MP -MF .deps/parseconf.Tpo -c -o parseconf.lo parseconf.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include -g -O2 -Wall -Wsign-compare -MT parseconf.lo -MD -MP -MF .deps/parseconf.Tpo -c parseconf.c -fPIC -DPIC -o .libs/parseconf.o libtool: compile: gcc -DHAVE_CONFIG_H...

...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 ../common/parseconf.o ../common/state.o main.o dstate.o serial.o 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/upsconf.o ../common/parsecon...

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

...var/ups --with-user=ups --with-group=ups > > returns alright, but the subsequent "make" fails with: > > make[1]: Entering directory `/opt/downloads/nut-2.6.5/common' > > /bin/bash ../libtool --tag=CC --mode=link gcc -I../include -g -O2 -Wall -Wsign-compare -o libparseconf.la parseconf.lo -lrt -lsocket -lnsl > > libtool: link: false cru .libs/libparseconf.a .libs/parseconf.o > > make[1]: *** [libparseconf.la] Error 1 > > But at this point I don't know if I have some library in the wrong > location, or if the makefile is being told to look...

...gram received signal SIGSEGV, Segmentation fault. >> 0x280e84ad in realloc () from /lib/libc.so.7 >> (gdb) >> (gdb) >> (gdb) >> (gdb) >> (gdb) bt >> #0 0x280e84ad in realloc () from /lib/libc.so.7 >> #1 0x0804ba40 in add_arg_word (ctx=0xbfbfe8f4) at parseconf.c:152 >> #2 0x0804bc18 in endofword (ctx=0xbfbfe8f4) at parseconf.c:212 >> #3 0x0804bedb in collect (ctx=0xbfbfe8f4) at parseconf.c:317 >> #4 0x0804c2e5 in parse_char (ctx=0xbfbfe8f4) at parseconf.c:449 >> #5 0x0804c41d in pconf_file_next (ctx=0xbfbfe8f4) at parseconf.c:...

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

...h-user=ups --with-group=ups >> >> returns alright, but the subsequent "make" fails with: >>> make[1]: Entering directory `/opt/downloads/nut-2.6.5/common' >>> /bin/bash ../libtool --tag=CC --mode=link gcc -I../include -g -O2 -Wall -Wsign-compare -o libparseconf.la parseconf.lo -lrt -lsocket -lnsl >>> libtool: link: false cru .libs/libparseconf.a .libs/parseconf.o >>> make[1]: *** [libparseconf.la] Error 1 -snip - > that seems like configure didn't find ar and uses false instead. > add /usr/ccs/bin to your $PATH and configure...

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 information: http://people.cs.clemson.edu/~gdowdin/work/ch06.html Can't

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? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration

...g 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 ../common/inet_aton.o > -lnsl -lsocket -L/software/openssl-0.9.7_runtime/lib > -R/software/openssl-0.9.7_runtime/lib:/software/libz-1.1.4_runtime/lib > -L/software/netsnmp-5.3/lib -lnetsnmp -lgen -lcrypto -lkstat -lelf -lm > -lns...

Network UPS Tools version 2.4.3 has been released. http://www.networkupstools.org/ Note: this is only a bugfix release that only solves the regression on IPv6 activation. Direct access: - Download: http://www.networkupstools.org/source/2.4/nut-2.4.3.tar.gz - News: http://www.networkupstools.org/source/2.4/new-2.4.3.txt - ChangeLog: http://www.networkupstools.org/source/2.4/ChangeLog the NUT

...ystems engineer ps: Furthermore, there seems some inconsistency between driver.list and website: # Network UPS Tools driver.list # # This file is used to build the compat.html on the web server. Any line # with exactly 4 arguments will be turned into an entry on there. # Naturally, it is read by parseconf, so the usual escaping tricks are # allowed if you need to insert something unusual. Is compat.html really built from this file or is this just outdated information ? For example, I don`t find information about the fact, that Mustek UPS is known to NUT. (BTW: can NUT do autodetection? this should...

...ystems engineer ps: Furthermore, there seems some inconsistency between driver.list and website: # Network UPS Tools driver.list # # This file is used to build the compat.html on the web server. Any line # with exactly 4 arguments will be turned into an entry on there. # Naturally, it is read by parseconf, so the usual escaping tricks are # allowed if you need to insert something unusual. Is compat.html really built from this file or is this just outdated information ? For example, I don`t find information about the fact, that Mustek UPS is known to NUT. (BTW: can NUT do autodetection? this should...

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you