Florian Forster
2007-Sep-04 09:15 UTC
[Nut-upsdev] Unresolved variable in `libupsclient-config'
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 -------------- A non-text attachment was scrubbed... Name: nut-2.2.0-sslflags.patch Type: text/x-diff Size: 508 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070904/b0923749/attachment.patch -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070904/b0923749/attachment.pgp
Arjen de Korte
2007-Sep-04 10:06 UTC
[Nut-upsdev] Unresolved variable in `libupsclient-config'
> 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.This was already solved in the development version, a few days after we released nut-2.2.0. Nevertheless, thanks for reporting. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
Arnaud Quette
2007-Sep-06 12:54 UTC
[Nut-upsdev] Unresolved variable in `libupsclient-config'
Hi Florian, 2007/9/4, Florian Forster <octo at verplant.org>:> 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.really strange! as Arjen told, I've found this few days after releasing 2.2.0. Fortunately, I was (as usual) late to throw out the debs, and so I've addressed it through a dpatch (as per the 2.2.0-1 debian/changelog): * debian/patches/02_libupsclient.dpatch: patch for the missing FLAGS I've just tested it again in a Sid pbuilder env, and everything is fine! So just to be sure, did you hit this problem with the debs? If so, an "apt-cache policy nut-dev" is welcome. Arnaud -- Free Software Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.debian.org/~aquette/ Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Ubuntu Media Center (UMC) Project Leader - https://launchpad.net/~umc-team