On Thu, Jan 18, 2018 at 09:47:17PM -0500, Mike Frysinger wrote: > 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 BTW, why we have this discussion now (6 months after the change)? Do have a problem to build util-linux? Karel -- Karel Zak <kzak@xxxxxxxxxx> http://karelzak.blogspot.com -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
