From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/transmission: fix gtk support
Date: Wed, 12 Jul 2017 09:49:24 +0200 [thread overview]
Message-ID: <20170712094924.435a5c54@windsurf.lan> (raw)
In-Reply-To: <a69e0db5-ae3c-fa51-7864-8fd8c98dd71c@mind.be>
Hello,
On Tue, 11 Jul 2017 23:42:24 +0200, Arnout Vandecappelle wrote:
> > configure: error: "The gtk client cannot be built without nls support. Try adding either --enable-nls or --without-gtk"
> >
> > Until the recent gettext revamp we were passing --disable-nls only when
> > BR2_ENABLE_LOCALE was disabled. However, the transmission-gtk support has:
> >
> > depends on BR2_PACKAGE_LIBGTK2 && BR2_ENABLE_LOCALE
>
> So in fact this dependency on LOCALE is wrong now. Indeed, the commit message
> that added it (d6dfc2109c7149a795f7bda963a9a583685dec3f) says:
Agreed, the BR2_ENABLE_LOCALE dependency is now wrong.
> > Therefore, we were never building transmission with --disable-nls. With
> > the gettext revamp, we now pass --disable-nls to all packages, unless
> > BR2_SYSTEM_ENABLE_NLS is enabled (which it isn't by default).
> >
> > So I am not sure the fix is complete. Indeed the error says that the
> > gtk client cannot be built without nls support. So I guess that if you
> > have BR2_PACKCAGE_TRANSMISSION_GTK=y, but BR2_SYSTEM_ENABLE_NLS
> > disabled it still fails to build.
>
> But only because we pass --disable-nls. I expect that passing --enable-nls
> should be sufficient to fix the build again. Indeed, all libcs not have libintl
"not -> now" I guess, correct?
> stubs built in so there is no reason why it shouldn't just work when you pass
> --enable-nls.
Why should we randomly pass --enable-nls to some packages? Why should
this package depends on BR2_SYSTEM_ENABLE_NLS, if it needs NLS support?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-12 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 17:51 [Buildroot] [PATCH 1/1] package/transmission: fix gtk support Bernd Kuhls
2017-07-11 19:37 ` Peter Korsgaard
2017-07-11 21:17 ` Thomas Petazzoni
2017-07-11 21:42 ` Arnout Vandecappelle
2017-07-11 21:57 ` Peter Korsgaard
2017-07-12 7:49 ` Thomas Petazzoni [this message]
2017-07-12 9:03 ` Thomas Petazzoni
2017-07-12 10:04 ` Arnout Vandecappelle
2017-09-01 23:18 ` Peter Korsgaard
2017-09-01 23:17 ` Peter Korsgaard
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=20170712094924.435a5c54@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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