Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] cryptsetup: Add libintl for UCLIBC toolchain
Date: Thu, 31 Oct 2013 18:07:17 -0300	[thread overview]
Message-ID: <5272C685.70901@zacarias.com.ar> (raw)
In-Reply-To: <1383248924-426-1-git-send-email-clshotwe@rockwellcollins.com>

On 10/31/2013 04:48 PM, Clayton Shotwell wrote:

> Fixes autobuild error
> http://autobuild.buildroot.net/results/cc1a65b9554bc2ece1b3ea8b51cd805b9bda7e86/
> 
> Adding libintl to the libraries list for cryptsetup when using a
> uclibc toolchain.
> 
> Signed-off-by: Clayton Shotwell <clshotwe@rockwellcollins.com>
> ---
> Realized an error in original commit.  Here is the fix.
> 
> Changes v1 -> v2:
>   - Adding TARGET_LDFLAGS to make sure they are not dropped
> 
>  package/cryptsetup/cryptsetup.mk |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/package/cryptsetup/cryptsetup.mk b/package/cryptsetup/cryptsetup.mk
> index 48d37f6..46e75ad 100644
> --- a/package/cryptsetup/cryptsetup.mk
> +++ b/package/cryptsetup/cryptsetup.mk
> @@ -12,4 +12,8 @@ CRYPTSETUP_DEPENDENCIES = lvm2 popt e2fsprogs libgcrypt host-pkgconf
>  CRYPTSETUP_LICENSE = GPLv2+ (programs), LGPLv2.1+ (library)
>  CRYPTSETUP_LICENSE_FILES = COPYING COPYING.LGPL
>  
> +ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
> +CRYPTSETUP_CONF_ENV += LDFLAGS="$(TARGET_LDFLAGS) -lintl"
> +endif
> +
>  $(eval $(autotools-package))

You're using libintl without selecting it or adding it to DEPENDENCIES.
See docs/manual/adding-packages-gettext.txt for the correct way to do
this (libintl is part of gettext and built when there's no libc
implementation).
It's probably working because some other dependency is pulling it in.
Regards.

      reply	other threads:[~2013-10-31 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 19:48 [Buildroot] [PATCH v2 1/1] cryptsetup: Add libintl for UCLIBC toolchain Clayton Shotwell
2013-10-31 21:07 ` Gustavo Zacarias [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=5272C685.70901@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.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