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: Pierre-Jean Texier <texier.pj2@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libarchive: fix uclibc with libiconv build
Date: Mon, 20 Feb 2023 21:38:58 +0100	[thread overview]
Message-ID: <20230220213858.2104ae5e@windsurf> (raw)
In-Reply-To: <20230220192125.555632-1-fontaine.fabrice@gmail.com>

On Mon, 20 Feb 2023 20:21:25 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Replace patch added by commit 9525bc7e64e8f44c31ab9dfd3f516ecb35982429
> as current patch is not correct, build failures are still raised by
> uclibc-ng with libiconv on fwup/gvfs/...:
> 
> configure: error: Requires libarchive. Libarchive must be built with zlib support.
> 
> [...]
> 
> Run-time dependency libarchive found: NO (tried cmake)
> 
> ../output-1/build/gvfs-1.48.1/meson.build:405:2: ERROR: Dependency lookup for libarchive with method 'pkgconfig' failed: Could not generate cargs for libarchive:
> Package iconv was not found in the pkg-config search path.
> Perhaps you should add the directory containing `iconv.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'iconv', required by 'libarchive', not found
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/05a5496495e51da2c9caf7570695cc95e1745e30
>  - http://autobuild.buildroot.org/results/98dc4b415115cca65b53e4cd986144ef85bf17ad
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...y-add-iconv-to-the-pc-file-if-needed.patch | 44 -------------------
>  ...o-not-add-iconv-for-Requires.private.patch | 28 ++++++++++++
>  2 files changed, 28 insertions(+), 44 deletions(-)
>  delete mode 100644 package/libarchive/0001-Only-add-iconv-to-the-pc-file-if-needed.patch
>  create mode 100644 package/libarchive/0001-autotools-do-not-add-iconv-for-Requires.private.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:[~2023-02-20 20:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 19:21 [Buildroot] [PATCH 1/1] package/libarchive: fix uclibc with libiconv build Fabrice Fontaine
2023-02-20 20:38 ` Thomas Petazzoni via buildroot [this message]

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=20230220213858.2104ae5e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=texier.pj2@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