[Buildroot] [PATCH v2] lzo: security bump to version 2.07

[Mike Zick <minimod@morethan.org>]

On Sun, 29 Jun 2014 07:47:51 +0300
Baruch Siach <baruch@tkos.co.il> wrote:

> Fixes CVE-2014-4607.
> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2:
>    Rephrase the comment explaining the need for AUTORECONF (Peter).
> ---
>  package/lzo/lzo.mk | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/package/lzo/lzo.mk b/package/lzo/lzo.mk
> index 10107fea3be3..3b348a3eff30 100644
> --- a/package/lzo/lzo.mk
> +++ b/package/lzo/lzo.mk
> @@ -4,11 +4,14 @@
>  #
>  ################################################################################
>  
> -LZO_VERSION = 2.06
> +LZO_VERSION = 2.07
>  LZO_SITE = http://www.oberhumer.com/opensource/lzo/download
>  LZO_LICENSE = GPLv2+
>  LZO_LICENSE_FILES = COPYING
>  LZO_INSTALL_STAGING = YES
> +# Out libtool patch does not apply to bundled ltmain.sh since it's too new.
s/out/our/

Two things mentioned in sentence, which of them is "too new"?

 try: "Our libtool patch is too new to apply to the bundled ltmain.sh"

> +# Run autoreconf to regenerate ltmain.sh.
> +LZO_AUTORECONF = YES
>  
>  $(eval $(autotools-package))
>  $(eval $(host-autotools-package))