From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH 3/4] kbuild: `nconf' needs -lintl
Date: Tue, 17 Aug 2010 11:00:18 +0200 [thread overview]
Message-ID: <4C6A4FA2.80907@suse.cz> (raw)
In-Reply-To: <1281932346-19067-3-git-send-email-lacombar@gmail.com>
On 16.8.2010 06:19, Arnaud Lacombe wrote:
> -HOSTLOADLIBES_nconf = -lmenu -lpanel -lncurses
> +HOSTLOADLIBES_nconf = -lmenu -lpanel -lncurses -lintl
This will not work on Linux though, the libintl functions are part of
glibc itself. There is already scripts/kconfig/check.sh and the
following snippet in scripts/kconfig/lkc.h
#ifndef KBUILD_NO_NLS
# include <libintl.h>
#else
static inline const char *gettext(const char *txt) { return txt; }
static inline void textdomain(const char *domainname) {}
static inline void bindtextdomain(const char *name, const char *dir) {}
#endif
that take care of disabling libintl support if it doesn't work. Not
optimal, but it should build in theory. Could you debug why it does not
work on NetBSD?
Michal
next prev parent reply other threads:[~2010-08-17 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 4:19 [PATCH 1/4] kbuild: don't assign `stdout' and `stderr' Arnaud Lacombe
2010-08-16 4:19 ` [PATCH 2/4] kbuild: don't include `check-lxdialog' ldflags in global HOST_LOADLIBES Arnaud Lacombe
2010-08-17 9:01 ` Michal Marek
2010-08-16 4:19 ` [PATCH 3/4] kbuild: `nconf' needs -lintl Arnaud Lacombe
2010-08-17 9:00 ` Michal Marek [this message]
2010-08-17 15:55 ` Arnaud Lacombe
2010-08-23 0:03 ` [PATCH] kbuild: don't overwrite HOST_EXTRACFLAGS Arnaud Lacombe
2010-08-23 0:17 ` Arnaud Lacombe
2010-08-26 12:00 ` Michal Marek
2010-08-26 12:11 ` Sam Ravnborg
2010-08-16 4:19 ` [PATCH 4/4] kbuild: fix typo Arnaud Lacombe
2010-08-17 8:27 ` [PATCH 1/4] kbuild: don't assign `stdout' and `stderr' Michal Marek
2010-08-17 15:28 ` Arnaud Lacombe
2010-08-18 5:16 ` Nir Tzachar
2010-10-21 2:22 ` Arnaud Lacombe
2010-10-27 22:56 ` Michal Marek
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=4C6A4FA2.80907@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=sam@ravnborg.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