Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zlib-ng: fix version in zlib.pc when building statically
Date: Wed, 1 Jun 2022 14:29:46 +0200	[thread overview]
Message-ID: <20220601142946.2916eaba@windsurf> (raw)
In-Reply-To: <20220531191036.107607-1-fontaine.fabrice@gmail.com>

On Tue, 31 May 2022 21:10:36 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Fix the following static build failure with transmission:
> 
> checking for ZLIB... configure: error: Package requirements (zlib >= 1.2.3) were not met:
> 
> Package dependency requirement 'zlib >= 1.2.3' could not be satisfied.
> Package 'zlib' has version '', required version is '>= 1.2.3'
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/b3b882482f517726e5c780ba4c37818bd379df82
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...ix-version-in-zlib.pc-when-building-.patch | 53 +++++++++++++++++++
>  1 file changed, 53 insertions(+)
>  create mode 100644 package/zlib-ng/0002-CMakeLists.txt-fix-version-in-zlib.pc-when-building-.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-06-01 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 19:10 [Buildroot] [PATCH 1/1] package/zlib-ng: fix version in zlib.pc when building statically Fabrice Fontaine
2022-06-01 12:29 ` Thomas Petazzoni via buildroot [this message]
2022-06-07 12:21 ` Peter Korsgaard

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=20220601142946.2916eaba@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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