From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Yuri Vasilevski <yvasilev@duke.math.cinvestav.mx>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Daniel Drake <dsd@gentoo.org>
Subject: Re: Patch that allows >=2.6.12 kernel to build on nls free systems
Date: Tue, 1 Nov 2005 10:42:31 -0800 [thread overview]
Message-ID: <29495f1d0511011042x6bb571c3tb8a4752173eadbbf@mail.gmail.com> (raw)
In-Reply-To: <20051101123534.39d273c3@dune.math.cinvestav.mx>
On 11/1/05, Yuri Vasilevski <yvasilev@duke.math.cinvestav.mx> wrote:
> Hi,
>
> It was caused by my copy/pasting error.
>
> On Tue, 1 Nov 2005 09:13:50 -0800
> Nish Aravamudan <nish.aravamudan@gmail.com> wrote:
>
> > On 10/26/05, Yuri Vasilevski <yvasilev@duke.math.cinvestav.mx> wrote:
> > > diff -Naur linux-2.6.14_rc2.orig/scripts/kconfig/Makefile linux-2.6.14_rc2/scripts/kconfig/Makefile
> > > --- linux-2.6.14_rc2.orig/scripts/kconfig/Makefile 2005-11-06 04:13:01 +0000
> > > +++ linux-2.6.14_rc2/scripts/kconfig/Makefile 2005-11-18 03:52:03 +0000
> > > @@ -116,6 +116,15 @@
> > > clean-files := lkc_defs.h qconf.moc .tmp_qtcheck \
> > > .tmp_gtkcheck zconf.tab.c zconf.tab.h lex.zconf.c
> > >
> > > +# Needed for systems without gettext
> > > +KBUILD_HAVE_NLS := $(shell \
> > > + if echo "\#include <libint.h>" | $(HOSTCC) $(HOSTCFLAGS) -E - > /dev/null 2>&1 ; \
>
> The file name is libintl.h and not libint.h (patch in the next e-mail)
Makes sense.
> > Looks like this patch was merged:
> >
> > http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=70a6a0cb92f24fd6bbe2e75299168909f735676a
> >
> > I noticed with builds of -git3/-git4, I get the following complaints
> > from oldconfig:
> >
> > scripts/kconfig/mconf.c: In function `main':
> > scripts/kconfig/mconf.c:1048: warning: statement with no effect
> > scripts/kconfig/mconf.c:1049: warning: statement with no effect
>
> This should be the output on nls free systems, but all systems were
> detected as nls free because of that error.
Ah, I see.
> > Not a big deal, just more complaints to have to see during the build
> > process (with CONFIG_NLS=y) :)
> >
> > Thanks,
> > Nish
>
> Sorry for this mistake.
No worries, it didn't make the compile fail :) Thanks for the quick response!
Thanks,
Nish
prev parent reply other threads:[~2005-11-01 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 16:50 Yuri Vasilevski
2005-10-27 20:43 ` Roman Zippel
2005-10-27 22:01 ` Arnaldo Carvalho de Melo
2005-11-01 17:13 ` Nish Aravamudan
2005-11-01 18:35 ` Yuri Vasilevski
2005-11-01 18:42 ` Nish Aravamudan [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=29495f1d0511011042x6bb571c3tb8a4752173eadbbf@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=akpm@osdl.org \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yvasilev@duke.math.cinvestav.mx \
/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
all inboxes | Powered by JetHome®