From: Adrian Bunk <bunk@stusta.de>
To: Jerome Pinot <ngc891@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [KCONFIG] Can't compile 2.6.12 without Gettext
Date: Sat, 27 Aug 2005 14:47:52 +0200 [thread overview]
Message-ID: <20050827124751.GK6471@stusta.de> (raw)
In-Reply-To: <88ee31b705082421303697aef7@mail.gmail.com>
On Thu, Aug 25, 2005 at 01:30:41PM +0900, Jerome Pinot wrote:
> Hi,
Hi Jerome,
> I didn't see much informations about this.
>
> It's not possible to "make {,menu}config" and even to compile a 2.6.12
> kernel if there is no or partially installed Gettext on the system.
>
> Full Gettext is *required* to launch the kbuild scripts since the
> modifications to add i18n to the config scripts.
>
> Not all system have gettext, I'm thinking about small or embedded
> system with specific toolchain. For example, uClibc is widely used but
> as still a partial nls support.
>
> Anyway, this should not be required for compiling a kernel. At least
> an option to pass to make which override the default behavior could
> solve the issue.
>
> Moreover, the script doesn't do any sanity check about the system
> (there is no configure script of course) and just try to catch the
> gettext binaries he founds first. There is a hard-coded filename too.
>
> Seems dangerous to me and should not be allowed by default.
>
> Am I misleading ?
are you using an ftp.kernel.org 2.6.12 kernel or a vendor kernel?
If it's an ftp.kernel.org kernel, please send the exact error messages
you are seeing.
> Jerome Pinot
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-27 12:48 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 [this message]
2005-08-27 15:23 ` Jerome Pinot
2005-08-27 17:49 ` Adrian Bunk
2005-08-28 1:19 ` Jerome Pinot
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=20050827124751.GK6471@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ngc891@gmail.com \
/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.