Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libao: bump version to 1.2.2
Date: Sun, 05 Oct 2025 07:34:08 +0300	[thread overview]
Message-ID: <87347yynjz.fsf@tarshish> (raw)
In-Reply-To: <20251004105801.380109-1-bernd@kuhls.net> (Bernd Kuhls's message of "Sat, 4 Oct 2025 12:58:01 +0200")

Hi Bernd,

On Sat, Oct 04 2025, Bernd Kuhls wrote:
> Added upstream patch to fix a missing include, autobuild did not record
> any build errors but Arch Linux provides the patch:
> https://gitlab.archlinux.org/archlinux/packaging/packages/libao/-/commit/bad3196d4e3030d31b01eb3bd41fff8afc8ca113

Where is this patch?

baruch

>
> Switched to gitlab tarball because the previous site does not provide a
> tarball for version 1.2.2 which was tagged in 2016:
> https://gitlab.xiph.org/xiph/libao/-/tags/1.2.2
>
> Added autoreconf due to usage of gitlab tarball which does not contain
> a configure script.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
>  package/libao/libao.hash | 6 ++----
>  package/libao/libao.mk   | 5 +++--
>  2 files changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/package/libao/libao.hash b/package/libao/libao.hash
> index 91c6bd11a7..70e6b4987e 100644
> --- a/package/libao/libao.hash
> +++ b/package/libao/libao.hash
> @@ -1,5 +1,3 @@
> -# From http://downloads.xiph.org/releases/ao/SHA256SUMS.txt
> -sha256  03ad231ad1f9d64b52474392d63c31197b0bc7bd416e58b1c10a329a5ed89caf  libao-1.2.0.tar.gz
> -
> -# Hash for license file:
> +# Locally computed
> +sha256  df8a6d0e238feeccb26a783e778716fb41a801536fe7b6fce068e313c0e2bf4d  libao-1.2.2.tar.gz
>  sha256  32b1062f7da84967e7019d01ab805935caa7ab7321a7ced0e30ebe75e5df1670  COPYING
> diff --git a/package/libao/libao.mk b/package/libao/libao.mk
> index 19a4c165c6..a9fd739ff3 100644
> --- a/package/libao/libao.mk
> +++ b/package/libao/libao.mk
> @@ -4,13 +4,14 @@
>  #
>  ################################################################################
>  
> -LIBAO_VERSION = 1.2.0
> -LIBAO_SITE = http://downloads.xiph.org/releases/ao
> +LIBAO_VERSION = 1.2.2
> +LIBAO_SITE = https://gitlab.xiph.org/xiph/libao/-/archive/$(LIBAO_VERSION)
>  LIBAO_DEPENDENCIES = host-pkgconf
>  LIBAO_INSTALL_STAGING = YES
>  LIBAO_LICENSE = GPL-2.0+
>  LIBAO_LICENSE_FILES = COPYING
>  LIBAO_CPE_ID_VENDOR = xiph
> +LIBAO_AUTORECONF = YES
>  LIBAO_CONF_OPTS = \
>  	--disable-esd \
>  	--disable-wmm \

-- 
                                                     ~. .~   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

  reply	other threads:[~2025-10-05  4:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-04 10:58 [Buildroot] [PATCH 1/1] package/libao: bump version to 1.2.2 Bernd Kuhls
2025-10-05  4:34 ` Baruch Siach via buildroot [this message]
2025-10-05  4:36   ` Baruch Siach via buildroot

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=87347yynjz.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=bernd@kuhls.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox