Re: Problem building util-linux without a separate ncursesw include dir

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01 Aug 2017 09:20, Karel Zak wrote:
> On Mon, Jul 31, 2017 at 09:46:39PM -0300, Carlos Santos wrote:
> > > From: "Carlos Santos" <casantos@xxxxxxxxxxxxxx>
> > > To: util-linux@xxxxxxxxxxxxxxx
> > > Sent: Monday, July 31, 2017 9:12:03 PM
> > > Subject: Problem building util-linux without a separate ncursesw include dir
> > 
> > > of util-linux. Would it be possible to make the location of ncursesw
> > > headers configurable, instead?
> 
> We test for alone ncurses.h and term.h in the for non-wide ncurses.
> Can you send output from your configure from the current master
> branch (or v2.30.1)?
> 
> > I was thinking on something simple, like https://pastebin.com/VqM9G9yu
> 
> Hmm, but you don't distinguish between wide and non-wide ncurses.

why don't we just support ncurses's pkg-config files as the default ?
$ pkg-config --cflags ncurses
-D_GNU_SOURCE
$ pkg-config --cflags ncursesw
-D_GNU_SOURCE -I/usr/include/ncursesw
-mike

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux