public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerome Pinot <ngc891@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [KCONFIG] Can't compile 2.6.12 without Gettext
Date: Sun, 28 Aug 2005 10:19:34 +0900	[thread overview]
Message-ID: <88ee31b70508271819610af2ea@mail.gmail.com> (raw)
In-Reply-To: <20050827174934.GL6471@stusta.de>

On 8/28/05, Adrian Bunk <bunk@stusta.de> wrote:
[...]
> You said "full gettext" was required and that the presence of "gettext
> binaries" should be checked what surprised me. It seems this is not the
> problem. Under Linux, libintl.h is not shipped with gettext but with the
> C library if you are using glibc or dietlibc.

I said the libintl.h file didn't solve the problem
 
> I do not question your point that "uClibc is widely used", but it's
> widely used to _run_ a Linux kernel.
> You said you are "thinking about small or embedded system with specific
> toolchain". If a system is so limited that you run uClibc on it, is this
> really the right system to _compile_ a kernel on? Where's the problem
> with cross-compiling the kernel for such a system?

You need the libc headers, to compile a kernel.
If you want to really work cleanly, i.e. be as much independant of the
host system as possible, you will not compile on another system, or
even use a cross-compiler, but use your own environnement system in
chroot. Everything in your system should have been built with the same
toolchain.

The LFS project shown very nice informations about this 1 or 2 years
ago. They still found bytes of the host system in the final build
binaries (sorry, can't find back the mail with figures). They had to
change completly the way of doing the toolchain. You can check the
beginning of chapter 5 from current book for more informations.

Shall every toolchain have gettext?
I don't think so. Sometimes, you just don't need all the nls bloat.

Moreover, Kconfig should check before trying to compile. It could be a
nasty way to introduce "some code" to the build program. Hum.

Anyway, there is no need of this kind of dependency to actually
compile the kernel. I still could use gcc in the source tree to get my
binaries.

The rationnal way should be to check for correct nls implementation
and just not use it if it's missing. It's a matter of adding 2 #define
in the code and add a proper test.

I don't understand why gettext must be _required_

-- 
Jerome Pinot
ftp://ngc891.blogdns.net/pub

      reply	other threads:[~2005-08-28  1:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25  4:30 [KCONFIG] Can't compile 2.6.12 without Gettext Jerome Pinot
2005-08-27 12:47 ` Adrian Bunk
2005-08-27 15:23   ` Jerome Pinot
2005-08-27 17:49     ` Adrian Bunk
2005-08-28  1:19       ` Jerome Pinot [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=88ee31b70508271819610af2ea@mail.gmail.com \
    --to=ngc891@gmail.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.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