search for: libupsclient

Hi, when building with the WITH_DEV conditional, either `libupsclient.pc' *or* `libupsclient-config' is installed. This is annoying when linking with libupsclient, because you basically have to do the check twice, once using `pkg-config' and once using `libupsclient-config'. Please consider the attached patch, which changes the behavior of `lib/Makef...

...e reports Making install in clients make[1]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' make[2]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' /usr/bin/mkdir -p '/usr/lib64' /bin/sh ../libtool --mode=install /usr/bin/install -c libupsclient.la libnutclient.la '/usr/lib64' libtool: install: /usr/bin/install -c .libs/libupsclient.so.4.0.0 /usr/lib64/libupsclient.so.4.0.0 libtool: install: (cd /usr/lib64 && { ln -s -f libupsclient.so.4.0.0 libupsclient.so.4 || { rm -f libupsclient.so.4 && ln -s libupsclient.so.4.0...

.../common' Making install in clients make[1]: Entering directory `/home/artesano/Downloads/nut-2.7.2.6/clients' make[2]: Entering directory `/home/artesano/Downloads/nut-2.7.2.6/clients' /bin/mkdir -p '/usr/local/ups/lib' /bin/sh ../libtool --mode=install /usr/bin/install -c libupsclient.la libnutclient.la '/usr/local/ups/lib' libtool: install: /usr/bin/install -c .libs/libupsclient.so.4.0.0 /usr/local/ups/lib/libupsclient.so.4.0.0 libtool: install: (cd /usr/local/ups/lib && { ln -s -f libupsclient.so.4.0.0 libupsclient.so.4 || { rm -f libupsclient.so.4 && l...

...te to the list. Thanks a lot for your help. Have a good day. 2015-02-13 17:45 GMT-06:00 Charles Lepple <clepple at gmail.com>: > On Feb 13, 2015, at 10:46 AM, Leopoldo Cantillo < > leopoldo.cantillo at gmail.com> wrote: > > > libtool: install: /usr/bin/install -c .libs/libupsclient.so.4.0.0 > /usr/local/ups/lib/libupsclient.so.4.0.0 > > libtool: install: (cd /usr/local/ups/lib && { ln -s -f > libupsclient.so.4.0.0 libupsclient.so.4 || { rm -f libupsclient.so.4 && ln > -s libupsclient.so.4.0.0 libupsclient.so.4; }; }) > > libtool: install:...

...te to the list. Thanks a lot for your help. Have a good day. 2015-02-13 17:45 GMT-06:00 Charles Lepple <clepple at gmail.com>: > On Feb 13, 2015, at 10:46 AM, Leopoldo Cantillo < > leopoldo.cantillo at gmail.com> wrote: > > > libtool: install: /usr/bin/install -c .libs/libupsclient.so.4.0.0 > /usr/local/ups/lib/libupsclient.so.4.0.0 > > libtool: install: (cd /usr/local/ups/lib && { ln -s -f > libupsclient.so.4.0.0 libupsclient.so.4 || { rm -f libupsclient.so.4 && ln > -s libupsclient.so.4.0.0 libupsclient.so.4; }; }) > > libtool: install:...

Hi, Made a test build of the Testing branch. The problem is that upsmon and upsc is not respecting the revision change of libupsclient.so. It is now libupsclient.so.1, but i get this. /usr/sbin/upsmon: error while loading shared libraries: libupsclient.so.0: cannot open shared object file: No such file or directory and: upsc: error while loading shared libraries: libupsclient.so.0: cannot open shared object file: No such fil...

Hello together, after upgrading from nut 2.2.1 to nut 2.2.2, I noticed there's a (new?) libupsclient.so library. On my Redhat based system, f.e. the "upsc" binary links against it and is unhappy as the library is not included in the current RPM file. If you look at the .spec file for Redhat, the libupsclient.* stuff is included in the "nut-devel" package only. The SuSE .spec...

Tags: patch, upstream Hi, when configuring nut 2.2.0 the variable/symbol `@SSL_LDFLAGS@' is not resolved by the libupsclient-config script. The attached patch changes `@SSL_CFLAGS@' to `@LIBSSL_CFLAGS@' `@SSL_LDFLAGS@' to `@LIBSSL_LDFLAGS@' which should solve this issue. Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/ -------------- next part --------...

...libnutclient.la -rw-r--r-- 1 root staff 984 Apr 10 14:32 libnutclient.lai lrwxrwxrwx 1 root staff 21 Apr 10 14:32 libnutclient.so -> libnutclient.so.0.0.0 lrwxrwxrwx 1 root staff 21 Apr 10 14:32 libnutclient.so.0 -> libnutclient.so.0.0.0 -rw-r--r-- 1 root staff 237182 Apr 10 14:28 libupsclient.a lrwxrwxrwx 1 root staff 18 Apr 10 14:28 libupsclient.la -> ../libupsclient.la -rw-r--r-- 1 root staff 984 Apr 10 14:28 libupsclient.lai lrwxrwxrwx 1 root staff 21 Apr 10 14:28 libupsclient.so -> libupsclient.so.4.0.0 lrwxrwxrwx 1 root staff 21 Apr 10 14:28 libupsclient.so.4 -...

[I took the liberty of replying on nut-upsdev - not many people are using github yet since the NUT repository native format is still SVN.] On Sep 4, 2012, at 10:17 AM, Emilien Kia wrote: > This is a proposal for a new client library which scopes an higher level than the existing libupsclient. > > It needs less dependencies to be compiled than the libupsclient and can be easier to integrate in other projects (including on windows with visual studio projects). The original need for this library was to have a minimal platform to integrate in Balooloo/hazelnut to communicate to upsd...

Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternat...

Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternat...

...rable > (especially if the default location is wrong on some platforms). > Most current packages install it by default. > > Attached patch removes configurability of pkgconfig support and installs > it to the recommended path. > > Note that you may even think about removal of libupsclient-config: > pkg-config is a more current and more flexible way to do the same and > you don't have to keep both in sync. --- configure.in +++ configure.in @@ -39,10 +39,6 @@ cgiexecdir='${exec_prefix}/cgi-bin' driverexecdir='${exec_prefix}/bin' htmldir='${prefix}/htm...

...onf/upssched.conf.sample config.status: creating data/html/header.html config.status: creating data/html/Makefile config.status: creating data/Makefile config.status: creating docs/Makefile config.status: creating drivers/Makefile config.status: creating include/Makefile config.status: creating lib/libupsclient-config config.status: creating lib/libupsclient.pc config.status: creating lib/Makefile config.status: creating man/Makefile config.status: creating packaging/Makefile config.status: creating packaging/debian/Makefile config.status: creating packaging/mandriva/Makefile config.status: creating packa...

2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk>: > On 04/04/17 14.10, Roger Price wrote: > >> On Tue, 4 Apr 2017, Arnaud Quette wrote: >> >> > [cuuuuut] > > Hi Arnaud, It seems to me that, looking out into the future, there are >> three >> things upsmon needs: >> >> 1. A fall-through <notify type> of

Hi, Currently, "configure.in" in both testing and the trunk have libupsclient disabled by default, which means the build is broken if the user doesn't explicitly enable it when running configure. Why was it like this and can I commit the fix? -- Carlos Rodrigues

...r to prevent lockups. This is a major one and I think this alone warrants a -pre3. I'll fix this later today in the trunk and Testing. Second (minor) problem I found is in the development stuff. In 'lib/Makefile.am' we have this: if WITH_DEV if WITH_PKG_CONFIG pkgconfig_DATA = libupsclient.pc else bin_SCRIPTS = libupsclient-config endif endif but in 'man/Makefile.am' we have the following: if WITH_PKG_CONFIG LIB_PAGES += libupsclient-config.1 endif So effectively, we'll only include the manual page if we don't include the 'libupsclient-config&...

Hi, Below is a log of what I did. In summary, I think the problem lies in that I can't build libupsclient: e.g. make[1]: *** No rule to make target `libupsclient.la', needed by `upsc'. Stop. I'm not very familiar with autoconf, aclocal, automake, I tried hacking it a bit, but couldn't get it to fix the errors... Thanks, Edwin $ svn update At revision 845. $ autoreconf configure.i...

...ould be to use a define, such as > #define UPSCONN UPSCONN_t > > The third best option would be to add something to let the preprocessor > determine the libraries version and have it configure the program > accordingly. An example could be: > /* Version 2.2.0 */ > #define LIBUPSCLIENT_VERSION 200200000L Since I'm preparing 2.2.1, I will add a typedef to manage the backward compat. I've fixed it in the subversion trunk and Testing branches. A last question: what is your use of this (wmnut or something else)? Thanks for the report. Arnaud -- Free Software Developer - h...

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