similar to: m4 scripts ignore user-supplied CFLAGS and LDFLAGS

Hi Alexander, no, I am not responsible for this! It's true that I created the scripts in m4/, but I only copied what was previously in configure.in. Try: svn up -r2 configure.in and you'll see that the code in question has been there since the beginning of SVN time (line 175). I cannot say why it was done that way. Probably because nobody needed a more general mechanism. Using

It looks like the change to m4/nut_check_libnetsnmp.m4 in r1968 broke the test on at least Solaris 10. Here is one possible fix. ---------------------------- --- m4/nut_check_libnetsnmp.m4.old 2009-12-15 09:30:48.000000000 -0800 +++ m4/nut_check_libnetsnmp.m4 2009-12-15 11:12:15.291295000 -0800 @@ -9,7 +9,8 @@ if test -z "${nut_have_libnetsnmp_seen}"; then

[moving this thread to nut-upsdev] On Jan 12, 2008 5:54 PM, Alexander I. Gordeev <lasaine at lvk.cs.msu.su> wrote: > On Sun, 13 Jan 2008 01:30:37 +0300, Charles Lepple <clepple at gmail.com> > wrote: > > when you figure this out, can we make sure that we know which > > changesets would need to be back-ported to branches/Testing (since > > that is where we would

[moving this thread to nut-upsdev] On Jan 12, 2008 5:54 PM, Alexander I. Gordeev <lasaine at lvk.cs.msu.su> wrote: > On Sun, 13 Jan 2008 01:30:37 +0300, Charles Lepple <clepple at gmail.com> > wrote: > > when you figure this out, can we make sure that we know which > > changesets would need to be back-ported to branches/Testing (since > > that is where we would

Citeren Alexander Gordeev <lasaine op lvk.cs.msu.su>: > I've received the units. Are there any special things I should test or > just the standard NUT setup? They should be detected out of the box (with the latest version from the trunk) through the 'usbhid-ups' driver. Note that I just added some additional commands to enable|disable|mute the beeper of the UPS.

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the

Hi Carlos, How do you do? :) Can you please clarify the change introduced by the subj (http://boxster.ghz.cc/projects/nut/changeset/1289)? I need to know in particular why did you add these intervals between sending a command and reading the response. They are the root of weird problems with megatec_usb. Can I safely remove READ_PACE and usleep-s? I tried to search the archives and found the

Hi, All! I've recently bought an UPS. It is Krauler UP-M500VA, it has USB port and is a HID device. But as I discovered the only HID application it supports is 0x860004, so it isn't claimed by both hidups and newhidups drivers, because it uses a vendor-specific values. I tried to discover values in that x86 page, but I failed. How can I do it? And after I get values how to understand

I have an UPS, that claims to be IPPon Back Power Pro 700. I'm trying to connect it using USB. lsusb -v says: Bus 1 Device 3: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

Does this require a new entry in scripts/hotplug/* and scripts/udev/*? -- Peter Alexander Gordeev wrote: > > Author: agordeev-guest > Date: Sat May 26 12:04:26 2007 > New Revision: 924 > > Log: > data/driver.list: added SVEN Power Smart RM 2000 to the list. > > Modified: > trunk/ChangeLog > trunk/data/driver.list > > Modified: trunk/ChangeLog >

Hi All, finally, I've got time and resources for development. Unfortunately I couldn't afford playing with my UPS because it was used permanently, but now it's ok. I've checked out cureent trunc and I see that Andrey Lelikov's changes haven't been applied yet. What's wrong with them? I think, he made a great job to simplify future support for this kind of

Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit

Hi, Please update the instructions for compiling trunk on the website: replace 'autoreconf' with 'autoreconf --install' because it stopped working after r1561. -- Alexander

Peter, Any objections to adding this to the trunk? When I run 'ldd upsc' without this patch, it lists the OpenSSL libraries, and the default ./configure setting is to not use OpenSSL. - Charles > Log: > If we are not using SSL_CFLAGS or SSL_LDFLAGS, do not add the OpenSSL libraries > to all of the binaries. > > > Modified: branches/deb_fixes_for_trunk/configure.in >

Hi Alexey, Please post the output of 'lsusb' and 'megatec_usb -a sven_625 -u nut -DDDDD'. On Monday 15 June 2009 14:32:16 you wrote: > Package: nut > Version: 2.4.1-3 > Severity: normal > > I have a SVEN Pro+ 625 ups that uses megatec_usb driver. > In ups.conf I describe it like: > [sven_625] > driver = megatec_usb > port = auto > desc =

On Friday, 31 August 2018 10:03:31 CEST Richard W.M. Jones wrote: > We also use -runtime-variant _pic which selects the OCaml runtime > linked with -fPIC. This will cause a performance regression on i686 > although that probably doesn't matter now. This is for supermin, right? > A bigger issue is that it will stop supermin from building with older > versions of OCaml (<=

Split CFLAGS into CFLAGS (user part) and AM_CFLAGS (not-so-user part; variable name taken from automake, but otherwise no relation). Also add LDFLAGS. This allows me to use `make CFLAGS="-O2 -fPIE" LDFLAGS="-pie"` without dropping the other important (AM_CFLAGS) flags. Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de> --- btrfs-progs/Makefile | 17

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

We also use -runtime-variant _pic which selects the OCaml runtime linked with -fPIC. This will cause a performance regression on i686 although that probably doesn't matter now. A bigger issue is that it will stop supermin from building with older versions of OCaml (<= 4.02.2). We might instead try detecting if it's the old version in ./configure but that gets a bit fragile. ---