Nut upsdev - Feb 2008 - broken build with default configure flags

Hi,

Currently, "configure.in" in both testing and the trunk have
libupsclient disabled by default, which means the build is broken if
the user doesn't explicitly enable it when running configure.

Why was it like this and can I commit the fix?

-- 
Carlos Rodrigues

Carlos Rodrigues wrote:
> Currently, "configure.in" in both testing and the trunk have
> libupsclient disabled by default, which means the build is broken if
> the user doesn't explicitly enable it when running configure.
Works for me (and the buildbots too). Could it be you need to run
'autoreconf' again?

Best regards, Arjen

Hi Carlos,

2008/2/3, Carlos Rodrigues <carlos.efr at
mail.telepac.pt>:
> Hi,
>
> Currently, "configure.in" in both testing and the trunk have
> libupsclient disabled by default, which means the build is broken if
> the user doesn't explicitly enable it when running configure.
>
> Why was it like this and can I commit the fix?
ok, I think got it.
previously, libupsclient was only built for internal use, and
distributed as static if --with-lib was enabled.
I recently changed this to building and using the shared lib (for all
nut tools).
So as to, we should *always* build the shared lib, and only the static
if -with-lib is enabled.
I have to dig a bit more for the fix...

Arnaud
-- 
Linux / Unix Expert R&D - MGE Office Protection Systems -
http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/