From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/Makefile.in: fix per-package build with gettext-gnu
Date: Thu, 30 Dec 2021 22:34:21 +0100 [thread overview]
Message-ID: <20211230223421.059f0917@windsurf> (raw)
In-Reply-To: <20211230205544.2056341-3-bernd.kuhls@t-online.de>
On Thu, 30 Dec 2021 21:55:43 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Building a package which needs -lintl fails because the package
> gettext-gnu, containing this library, is not rsync'ed to the build
> directory.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Hu? Could you explain?
> TARGET_NLS_DEPENDENCIES = host-gettext
> ifeq ($(BR2_PACKAGE_GETTEXT_PROVIDES_LIBINTL),y)
> -TARGET_NLS_DEPENDENCIES += gettext
> +TARGET_NLS_DEPENDENCIES += gettext-gnu
gettext is a virtual package that depends either on gettext-gnu or
gettext-tiny, and both of them provide a libintl implementation.
How can this patch be correct?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-30 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 20:55 [Buildroot] [PATCH 1/4] package/vdr: bump version to 2.6.0 Bernd Kuhls
2021-12-30 20:55 ` [Buildroot] [PATCH 2/4] package/libexecinfo: new package Bernd Kuhls
2021-12-30 20:55 ` [Buildroot] [PATCH 3/4] package/Makefile.in: fix per-package build with gettext-gnu Bernd Kuhls
2021-12-30 21:34 ` Thomas Petazzoni [this message]
[not found] ` <20211230223421.059f0917__21186.4138067298$1640900090$gmane$org@windsurf>
2021-12-30 21:53 ` Bernd Kuhls
2021-12-30 20:55 ` [Buildroot] [PATCH 4/4] package/vdr: enable musl/uclibc build Bernd Kuhls
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=20211230223421.059f0917@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
/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