> From: "Karel Zak" <kzak@xxxxxxxxxx> > To: "Carlos Santos" <casantos@xxxxxxxxxxxxxx> > Cc: util-linux@xxxxxxxxxxxxxxx > Sent: Tuesday, August 1, 2017 4:20:17 AM > Subject: Re: Problem building util-linux without a separate ncursesw include dir > 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)? config.log: https://pastebin.com/DVAyx1Zb defconfig for buildroot: https://pastebin.com/U3pz0hvm >> I was thinking on something simple, like https://pastebin.com/VqM9G9yu > > Hmm, but you don't distinguish between wide and non-wide ncurses. That's because on Buildroot only one of the variants can exist. BTW I noticed that on Fedora each /usr/include/ncurses/<foo> is a symlink to ../<foo>, so the situation is exactly the same. -- Carlos Santos (Casantos) - DATACOM, P&D “The greatest triumph that modern PR can offer is the transcendent success of having your words and actions judged by your reputation, rather than the other way about.” — Christopher Hitchens -- 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
