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

Hi all, There is a discussion going on one russian forum about NUT cross-compiling and packaging for some custom embedded firmware. And one of the authors complained about NUT script for checking ssl library ignoring supplied CFLAGS and LDFLAGS with the desired include and library paths. I checked several scripts in m4 folder and all of them do something like this:

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

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

[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

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 >

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.

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

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

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

Hello, I have a samba pdc running with openldap as backend. I have ou's for user and groups and used smbldap-populate to create the ldap entries. I can add windows clients and authenticate but i have a problem with the net tool (lvk is an samba user too): net -U Administrator rpc user info lvk will return Domain Users When running net -U Administrator rap user info lvk I get

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

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

On Monday 25 April 2005 14:43, Vladimir Prus wrote: > The 'i' variable is never modified in the program, however, all analyses > except for -globalsmodref-aa report that the > > %tmp.3 = call int %_Z3bari( int %p ) ; <int> [#uses=1] > > instruction can modify 'i'. I'm somewhat surprised, because it looks like > -globalsmodref-aa is the simplest

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

I notice that the user is not able to set their own CFLAGS or LDFLAGS in the ao, ogg, vorbis, and voribs-tools projects. Is there a reason for this? I understand the fact that these modules want to set extremely high optimization flags, and that most users won't know what these are offhand, but there are times when it is useful for the user to specify their own CFLAGS/LDFLAGS. For example,