linux-kernel - Re: [PATCH] MAINTAINERS: new kbuild maintainer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 10 Dec 2009 14:04:23 +0200
From:	Nir Tzachar <nir.tzachar@...il.com>
To:	Arkadiusz Miskiewicz <a.miskiewicz@...il.com>
Cc:	Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: new kbuild maintainer

>
> On my disto it works but it won't on a distro where /usr/include/ncurses
> contains wide version of headers.

ncurses does not support a proper pkg-config scheme, hence the
difficulty with finding the correct flags. Regarding the wideness of
the library, I would presume that any distro which mismatches
/usr/include/ncurses.h and libncurses.so is in itself broken. Taking
this into consideration, I think that including /usr/include/ncurses.h
and linking against -lncurses should work. We should entirely ignore
the wide version of the library, and use the default installation
provided.

>
>>
>> Moreover, currently nconfig does not use this check.
>
> I was testing on linus git and this flags from this check were used in nconfig
> build, too (that's why there were ncurses and ncursesw at the same time in
> linking command).

Well, I do not know why, by the check changed the flags for _all_
targets in the scripts/kconfig dir, such that even qconfig got copiled
with -lncursesw. Strange. The change I made in the Makefile in the
previous mail fixes that.

Cheers,
Nir.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/