Jean Philippe EIMER
2010-Feb-20 11:46 UTC
[Nut-upsdev] nut-2.4.2 : IPV6 badly managed at configure
I installed nut-2.4.2 from sources and IPV6 was disabled whereas configure detected it, preventing upsd to run properly on my ipv6 enabled system. In fact, HAVE_IPV6 is never enabled in include/config.h. If I force #define HAVE_IPV6 1 in config.h, everything is back to normal operation. J. Ph.
Charles Lepple
2010-Feb-20 14:38 UTC
[Nut-upsdev] nut-2.4.2 : IPV6 badly managed at configure
On Feb 20, 2010, at 6:46 AM, Jean Philippe EIMER wrote:> I installed nut-2.4.2 from sources and IPV6 was disabled whereas > configure detected it, preventing upsd to run properly on my ipv6 > enabled system. > > In fact, HAVE_IPV6 is never enabled in include/config.h. > > If I force > #define HAVE_IPV6 1 > in config.h, everything is back to normal operation.Jean Philippe, Thanks for reporting this. Arjen, the NUT_CHECK_IPV6 macro sets "nut_have_ipv6", but then references "nut_with_ipv6" which is not assigned until after NUT_CHECK_IPV6 is called.
Arjen de Korte
2010-Feb-20 20:18 UTC
[Nut-upsdev] nut-2.4.2 : IPV6 badly managed at configure
Citeren Charles Lepple <clepple op gmail.com>:> the NUT_CHECK_IPV6 macro sets "nut_have_ipv6", but then references > "nut_with_ipv6" which is not assigned until after NUT_CHECK_IPV6 is > called.Ouch! Sorry about that. Fixed in the trunk. I think we want to re-release nut-2.4.2, because this probably is going to hit a great number of people. Best regards, Arjen -- Please keep list traffic on the list
Alexander Gordeev
2010-Feb-20 22:47 UTC
[Nut-upsdev] nut-2.4.2 : IPV6 badly managed at configure
? Sat, 20 Feb 2010 21:18:30 +0100 Arjen de Korte <nut+devel at de-korte.org> ?????:> Citeren Charles Lepple <clepple at gmail.com>: > > > the NUT_CHECK_IPV6 macro sets "nut_have_ipv6", but then references > > "nut_with_ipv6" which is not assigned until after NUT_CHECK_IPV6 > > is called. > > Ouch! Sorry about that. Fixed in the trunk. I think we want to > re-release nut-2.4.2, because this probably is going to hit a great > number of people.Why not do 2.4.3 release? This is just numbers :) -- Alexander -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100221/ee9b4226/attachment.pgp>
Charles Lepple
2010-Feb-21 03:53 UTC
[Nut-upsdev] nut-2.4.2 : IPV6 badly managed at configure
On Feb 20, 2010, at 5:47 PM, Alexander Gordeev wrote:> Arjen de Korte <nut+devel at de-korte.org> ?????: > >> Citeren Charles Lepple <clepple at gmail.com>: >> >>> the NUT_CHECK_IPV6 macro sets "nut_have_ipv6", but then references >>> "nut_with_ipv6" which is not assigned until after NUT_CHECK_IPV6 >>> is called. >> >> Ouch! Sorry about that. Fixed in the trunk. I think we want to >> re-release nut-2.4.2, because this probably is going to hit a great >> number of people. > > Why not do 2.4.3 release? This is just numbers :)Or 2.4.2.1, or... I would like to try running the IPv6 code on my test machines before we re-release (since IPv6 was broken for a while on FreeBSD without the ports tree patches). That will probably be Sunday evening at the earliest. (I admit I was only looking at the configure script summaries when I checked to see if IPv6 was working.)