All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mtd: add missing -lintl from util-linux when building statically
Date: Thu, 10 Sep 2015 16:45:56 +0300	[thread overview]
Message-ID: <20150910134556.GQ2191@tarshish> (raw)
In-Reply-To: <1441881890-6521-1-git-send-email-Vincent.Riera@imgtec.com>

Hi Vincent,

On Thu, Sep 10, 2015 at 11:44:50AM +0100, Vicente Olivert Riera wrote:
> mtd depends on util-linux when BR2_PACKAGE_MTD_MKFSUBIFS is selected.
> Also, util-linux depends on gettext and will need to link with -lintl if
> BR2_NEEDS_GETTEXT_IF_LOCALE is selected. So, when mtd tries to link with
> util-linux's uuid (-luuid) it should add -lintl as well, but it fails
> when building statically. The uuid.pc file lists -lintl as one of the
> needed libraries, but since mtd package doesn't have a configure phase
> we can't do the following:
> 
> MTD_DEPENDENCIES += host-pkgconf
> MTD_CONF_ENV += LIBS=`$(PKG_CONFIG_HOST_BINARY) --libs uuid"`

So why not something like:

MTD_MKFS_UBIFS_LIBS = `$(PKG_CONFIG_HOST_BINARY) --libs uuid"`

and use $(MTD_MKFS_UBIFS_LIBS) instead of hard coding -lintl in the sed 
expression. This way you can remove the condition from the sed expression.

baruch

> So, in further investigations I have seen that mtd hardcodes the libs
> for mkfs.ubifs in the Makefile, in a variable called LDLIBS_mkfs.ubifs,
> and that variable can't be overwritten by passing options or environment
> variables to make.
> 
> So, to fix the problem, we use a sed command to append -lintl to the
> LDLIBS_mkfs.ubifs variable only when building statically, because it's
> the case when it fails, and only when BR2_NEEDS_GETTEXT_IF_LOCALE is
> selected, because is the case when you also need -lintl when linking
> with util-linux.
> 
> Fixes:
> 
>   http://autobuild.buildroot.net/results/2dd/2ddd714446d9eb75701bd48c117dc5bbbd291a76/
> 
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
>  package/mtd/mtd.mk |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/package/mtd/mtd.mk b/package/mtd/mtd.mk
> index 0fb9fc2..a34c840 100644
> --- a/package/mtd/mtd.mk
> +++ b/package/mtd/mtd.mk
> @@ -18,6 +18,12 @@ endif
>  
>  ifeq ($(BR2_PACKAGE_MTD_MKFSUBIFS),y)
>  MTD_DEPENDENCIES += util-linux zlib lzo
> +ifeq ($(BR2_STATIC_LIBS)$(BR2_NEEDS_GETTEXT_IF_LOCALE),yy)
> +define MTD_ADD_MISSING_LINTL
> +	$(SED) '/^LDLIBS_mkfs\.ubifs/ s/$$/ -lintl/' $(@D)/Makefile
> +endef
> +MTD_PRE_BUILD_HOOKS += MTD_ADD_MISSING_LINTL
> +endif
>  endif
>  
>  ifeq ($(BR2_PACKAGE_BUSYBOX),y)

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-09-10 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 10:44 [Buildroot] [PATCH] mtd: add missing -lintl from util-linux when building statically Vicente Olivert Riera
2015-09-10 13:45 ` Baruch Siach [this message]
2015-09-10 14:00   ` Vicente Olivert Riera
2015-09-10 14:06     ` Baruch Siach
2015-09-10 14:16       ` Vicente Olivert Riera
2015-09-10 20:26         ` Baruch Siach

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=20150910134556.GQ2191@tarshish \
    --to=baruch@tkos.co.il \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.