Displaying 20 results from an estimated 4000 matches similar to: "Testing recommend, make Install error Digest, Vol 116, Issue 10"
2015 Feb 14
0
Fwd: Attc. Testing, make Install Digest, Vol 116, Issue 10
Hi Charles,
I forgot add attaches.[?]
I try to do from a new clean installations after reset my server (some
changes need it), and now the make install seems to works.
Now i going to configure and test it.
I attached the logs files from the last run.
If i have any other problem I write to the list.
Thanks a lot for your help.
Have a good day.
2015-02-13 17:45 GMT-06:00 Charles Lepple
2015 Feb 13
1
Testing recommend, make Install error Re: Nut-upsuser Digest, Vol 116, Issue 10
Hi,
Thanks for help.
- I download the last version of NUT, 2.7.2.6
- I install library:
nss-devel
gcc-c++
So now I didn't get last errors on make.
But I get a new one when I try to do - make install
---------------------------
*[root at artesano nut-2.7.2.6]# make install*
Making install in include
make[1]: Entering directory `/home/artesano/Downloads/nut-2.7.2.6/include'
2016 Dec 10
2
2.7.4 make install fails: libnutclient.so.0.0.0 missing
I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled
nut 2.7.4. ./configure, make clean and make went well, but make install
failed. Make 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'
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017 Apr 10
0
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 04/04/17 15.19, Arnaud Quette wrote:
>
>
> 2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk
> <mailto:jon.bendtsen at jonix.dk>>:
[cuuuuut]
>
> there is a Github issue: https://github.com/networkupstools/nut/issues/415
> + a branch with the implementation:
> https://github.com/networkupstools/nut/tree/upsmon_alarm
>
> For now:
> -
2015 Jul 21
0
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
2015-07-06 10:40 GMT+02:00 Sergey Talchuk <tals1975 at gmail.com>:
> 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
2015 Jul 06
0
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
On Jul 6, 2015, at 4:40 AM, Sergey Talchuk wrote:
> 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.
What does the error message look like? Does the configure script fail when checking for the C++ compiler, or later on?
> There wasn't such a problem with nut-2.6.5.
>
>
2015 Jul 06
4
Nut-2.7.3 & gcc-3.3.6
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 alternative to
2015 Jul 06
4
Nut-2.7.3 & gcc-3.3.6
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 alternative to
2015 Jul 06
2
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
Hi Charles,
Thanks for the prompt reply!
Errors occur when execute make:
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../include -MT nutclient.lo -MD -MP -MF $depbase.Tpo -c -o
nutclient.lo nutclient.cpp &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo
-MD -MP -MF .deps/nutclient.Tpo -c
2012 Nov 10
1
libnutclient pull request
Hello all,
I come back to request comments (and merge) on my pull request of the
libnutclient.
https://github.com/clepple/nut/pull/2
All previous comments have been addressed (some fixes and documentation).
For memory, the libnutclient is an high-level C++ and C client library
allowing to dialog with upsd. The addressed model is oriented around
devices, variables and commands; unlike
2012 Sep 05
2
[nut] High level C and C++ libnutclient (#2)
[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
2015 Feb 13
1
Error installing Nut 2.7.2 on RedHat 6.6
Hi,
I need help because I can't install Nut in RedHat EL 6.6
The version of Nut in repository ot RHEL is 2.6.5-2, but doesn't suppor my
UPS,
Liebert GXT3-200RT.
I read that it is supported using Nut version 2.7.2, but I looking all
around the web how to install it in my RedHat but I didn't find answers.
Follow the guide, I can downlad lasted version stable on web: 2.7.2
Here the
2024 Dec 16
1
NUT on FBSD 14-2 fails to shut down UPS - select with socket: Invalid argument
I'm still digging into this but thought I'd post what I have so far in case
there's a known issue that's easily fixed.
I'm using the version of NUT that's in the ports tree (see the info at the
bottom). Using the SNMP drivers to talk with two ACP SmartUPSs.
NUT is functional about monitoring and initiating host shutdown. However,
when it comes time to shut down the UPSs
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017 Apr 04
4
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
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
2024 Dec 17
1
NUT on FBSD 14-2 fails to shut down UPS - select with socket: Invalid argument
Hello,
Thanks for the report and sorry about any complications.
A few first questions:
* is this setup known to have been working with earlier NUT releases (e.g.
same OS and devices, older NUT - can try with a custom build of older
tags)? Is this a regression, or we never knew the correct mappings for
timeouts and/or shutdown commands used by this model?
* is there the `select` error when
2012 Oct 29
1
Nut-upsdev Digest, Vol 88, Issue 22
?Hello everybody,
just a few notes to the doxygen X man issue:
1/ AFAIK doxygen can generate man pages, so why don't
we just generate them and decide then whether they
are ill fitted or usable...
2/ I'd definitely use doxygen when possible; I mean I don't
know any alternative that's able to do (at least partial)
validation of the documentation with the source
3/ I
2009 Jan 24
1
Patch to always install libupsclient-config
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/Makefile.am' to install
2007 Aug 07
1
pkgconfig fix for nut
Dear Stanislav,
thanks for your patch. The problem with your "recommended"
pkgconfigdir is that in many cases, it does not work. Namely, when
${prefix} is not one of the standard places such as /usr.
As I understand it, the whole point of a tool like pkgconfig is to
allow other software to automatically detect the install location of
NUT, especially when that location is not one of
2008 Feb 21
3
libupsclient.so
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
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