Mail archive

Re: [alpine-devel] [PATCH] testing/nut: new aport

From: Natanael Copa <>
Date: Wed, 5 Mar 2014 10:11:38 +0100

On Sun, 2 Mar 2014 17:19:40 +0400
Kozak Ivan <> wrote:

> +# bcmxcp.patch - sorry no bcmxc and no bcmxcp_usb (get errors about undefined reference to `ldexp')

I fixed it and pushed a fix to aports.

> diff --git a/testing/nut/bcmxcp.patch b/testing/nut/bcmxcp.patch
> new file mode 100644
> index 0000000..644d9b7
> --- /dev/null
> +++ b/testing/nut/bcmxcp.patch
> _at_@ -0,0 +1,178 @@
> +---
> ++++ src/nut-2.7.1/drivers/

A comment about the way this was 'resolved'. We normally try avoid
patching the since it is generated from The
drawback with patching is that then we need re-run the
autotools (aclocal, autoconf automake etc) and that might introduce new
issues. The biggest benefit though is that the pach can normally be
submitted upstream.

Would you be able to submit a bugreport upstream (to nut developers)
and give them the patch i made:

Basically when using ldexp you should link against libm (even the
manpage[1] says:

  Link with -lm.




Received on Wed Mar 05 2014 - 10:11:38 UTC