From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Casey Reeves <casey@xogium.me>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/lzop: bump to version 1.04
Date: Sun, 26 Feb 2023 08:07:34 +0200 [thread overview]
Message-ID: <87mt51ez6l.fsf@tarshish> (raw)
In-Reply-To: <20230225132927.4067626-1-casey@xogium.me>
Hi Casey,
On Sat, Feb 25 2023, Casey Reeves wrote:
> diff --git a/package/lzop/lzop.mk b/package/lzop/lzop.mk
> index 55157c4d48..056d724a7b 100644
> --- a/package/lzop/lzop.mk
> +++ b/package/lzop/lzop.mk
> @@ -4,13 +4,22 @@
> #
> ################################################################################
>
> -LZOP_VERSION = 1.03
> +LZOP_VERSION = 1.04
> LZOP_SITE = http://www.lzop.org/download
> LZOP_LICENSE = GPL-2.0+
> LZOP_LICENSE_FILES = COPYING
> LZOP_DEPENDENCIES = lzo
> HOST_LZOP_DEPENDENCIES = host-lzo
>
> +LZOP_LIBTOOL_PATCH=NO
> +#LZOP_POST_PATCH_HOOKS += LZOP_LIBTOOL_FIXUP
This commit looks redundant.
baruch
> +
> +define LZOP_LIBTOOL_FIXUP
> + patch -i support/libtool/buildroot-libtool-v2.4.4.patch $(@D)/autoconf/ltmain.sh
> +endef
> +
> +LZOP_POST_PATCH_HOOKS += LZOP_LIBTOOL_FIXUP
> +
> $(eval $(autotools-package))
> $(eval $(host-autotools-package))
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-26 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 11:28 [Buildroot] [PATCH] package/lzop: bump to version 1.04 Casey Reeves
2023-02-25 13:29 ` [Buildroot] [PATCH v2] " Casey Reeves
2023-02-26 6:07 ` Baruch Siach via buildroot [this message]
2023-02-26 11:04 ` Casey R.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mt51ez6l.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=casey@xogium.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.