Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lttng-babeltrace: fix build with standalone gettext
Date: Sat, 19 Mar 2016 23:12:30 +0300	[thread overview]
Message-ID: <1458418350-13924-1-git-send-email-jcmvbkbc@gmail.com> (raw)

lttng-babeltrace can't detect that uuid_generate is provided by -luuid
because the configure test fails with the following message:
  libuuid.a(libuuid_la-randutils.o): In function `random_get_bytes':
  randutils.c:(.text+0x204): undefined reference to `libintl_gettext'

Add LIBS=-lintl to configure options in case we're building with
standalone gettext.
Fixes:
  http://autobuild.buildroot.net/results/1ab89c6e8d704bc28c9ff8b5ffda3f60e57a25b4/

Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
 package/lttng-babeltrace/lttng-babeltrace.mk | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/package/lttng-babeltrace/lttng-babeltrace.mk b/package/lttng-babeltrace/lttng-babeltrace.mk
index 5de77fb..cf57843 100644
--- a/package/lttng-babeltrace/lttng-babeltrace.mk
+++ b/package/lttng-babeltrace/lttng-babeltrace.mk
@@ -12,5 +12,9 @@ LTTNG_BABELTRACE_LICENSE_FILES = mit-license.txt gpl-2.0.txt LICENSE
 
 LTTNG_BABELTRACE_DEPENDENCIES = popt util-linux libglib2
 
+ifeq ($(BR2_NEEDS_GETTEXT),y)
+LTTNG_BABELTRACE_CONF_OPTS += LIBS=-lintl
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))
-- 
2.1.4

             reply	other threads:[~2016-03-19 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-19 20:12 Max Filippov [this message]
2016-07-01  8:15 ` [Buildroot] [PATCH] lttng-babeltrace: fix build with standalone gettext Thomas Petazzoni

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=1458418350-13924-1-git-send-email-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --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