similar to: Reasons for nut-2.2.2-pre3 package

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

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

Hi Charles, 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 <clepple at gmail.com>: >

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'

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

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'

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: > -

On Thu, Jan 17, Richard W.M. Jones wrote: > On Wed, Jan 16, 2013 at 05:51:53PM +0100, Olaf Hering wrote: > > On Mon, Jan 14, Olaf Hering wrote: > > > This is a first attempt to build libguestfs with just a ocaml bytecode > > > compiler. The three tools written in ocaml will be build only when an > > > ocamlopt compiler is available. > > Here is a more

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

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

Cleanup make system so that all noninstalled headers are put to noinst_HEADERS. This quarentees that header will be present in tar ball but not installed with make install. CC: nouveau at lists.freedesktop.org Signed-off-by: Pauli Nieminen <suokkos at gmail.com> --- Makefile.am | 6 +++--- intel/Makefile.am | 10 ++++++---- nouveau/Makefile.am | 4 +++- 3 files changed,

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

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***

I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa

On Thu, 11 Jul, at 01:55:12PM, Michael Szerencsits wrote: > Hello, > > I tried to make my own binary with 'make efi64 install' but it fail with > > make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. > make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' > make[2]: ***

The -pre3 release is out and tends to be the last one before the release. This pre version adds two new features we thought it would be interesting to have in 0.3.5: - Reboot If your system features the reboot.c32 module, the "reboot" command will restart your computer. The floppy/iso images we provides includes this module to enable this feature. - Automatic Commands When starting

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

Hello, I just received a serious bug report from Stas Kysel of rPath (with a great test case); it appears that deleted files can confuse extlinux so that it misses files. This is bad. As a result, I have pushed out 3.63-pre3, and intend to make a 3.63 final shortly. I would appreciate any help testing this. Furthermore, I would like to finish the SDI booting module, but I have yet to

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

Okay, thanks. I just tried 6.01-pre1, downloading the .xz file. But that won't build because the gnu-efi directory is empty. ?? On Thu, Sep 19, 2019 at 9:29 PM Ady Ady via Syslinux <syslinux at syslinux.org> wrote: > > > fixes, decided to go with 6.04-pre3. First, is that about read for a > > > Please try either 6.04-pre1, or the current (binary) packages from