From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Nir Tzachar <nir.tzachar@gmail.com>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: new kbuild maintainer
Date: Tue, 8 Dec 2009 21:31:25 +0100 [thread overview]
Message-ID: <200912082131.26051.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <4B1EB5E9.3010506@suse.cz>
On Tuesday 08 of December 2009, Michal Marek wrote:
> Arkadiusz Miskiewicz napsal(a):
> > On Tuesday 08 of December 2009, Michal Marek wrote:
> >> Arkadiusz Miskiewicz napsal(a):
> >>> Maybe we can get colors back in menuconfig then? ;-)
> >>> http://bugzilla.kernel.org/show_bug.cgi?id=13677
> >>
> >> Does it also happen with Nir's nconfig
> >> (http://lkml.org/lkml/2009/11/25/119)?
> >
> > Yes, it does happen, I have non-color menus. That's because nconfig also
> > mixes wide ncurses library with non wide ncurses headers.
> >
> > gcc -Wp,-MD,scripts/kconfig/.nconf.o.d -Wall -Wmissing-prototypes
> > -Wstrict- prototypes -O2 -fomit-frame-pointer -I/usr/include/ncurses -
> > DCURSES_LOC="<ncurses.h>" -DLOCALE -c -o scripts/kconfig/nconf.o
> > scripts/kconfig/nconf.c
> >
> > /usr/include/ncurses is non wide version of ncurses headers (but on other
> > distros it could be done differently aka /usr/include/ncures being wide
> > version)
> >
> > gcc -o scripts/kconfig/nconf scripts/kconfig/nconf.o
> > scripts/kconfig/zconf.tab.o scripts/kconfig/nconf.gui.o -lncursesw -lmenu
> > - lpanel -lncurses
> >
> > and here it's linked to non wide version of library (also to wide, too
> > due to scripts/kconfig/lxdialog/check-lxdialog.sh putting it here)
> >
> > Anyway way to solve this is:
> > - detect if ncurses header is wide or non-wide
> > - link with proper ncurses library based on detected header
>
> Nir, you surely know ncurses better than me :). Could you look into
> this? Arkadiusz, which distribution are you using?
PLD/Linux
> Michal
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2009-12-08 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 12:52 [PATCH] MAINTAINERS: new kbuild maintainer Michal Marek
2009-12-08 13:18 ` Sam Ravnborg
2009-12-08 15:11 ` Arkadiusz Miskiewicz
2009-12-08 19:56 ` Michal Marek
2009-12-08 20:07 ` Arkadiusz Miskiewicz
2009-12-08 20:24 ` Michal Marek
2009-12-08 20:31 ` Arkadiusz Miskiewicz [this message]
2009-12-09 6:22 ` Nir Tzachar
2009-12-09 6:28 ` Arkadiusz Miskiewicz
2009-12-10 12:04 ` Nir Tzachar
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=200912082131.26051.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nir.tzachar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox