All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: util-linux@vger.kernel.org
Subject: Problem building util-linux without a separate ncursesw include dir
Date: Mon, 31 Jul 2017 21:12:03 -0300 (BRT)	[thread overview]
Message-ID: <1971282138.2691482.1501546323018.JavaMail.zimbra@datacom.ind.br> (raw)

Hello,

Since commit 3947ca4ca (build-sys: ncurses headers cleanup), util-linux
assumes that ncursesw headers are in an "ncursesw" subdirectory. That's
valid on systems that have both ncurses variants but not on embedded
systems like Buildroot on which only one variant is build, with headers
always installed directly at /usr/include.

I added a patch to revert commit 3947ca4ca to the Buildroot recipe but
such a drastic solution can easily become incompatible with new versions
of util-linux. Would it be possible to make the location of ncursesw
headers configurable, instead?

Thanks in advance.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
Rua América, 1000 - Eldorado do Sul, RS, Brasil - 92990-000
casantos@datacom.ind.br          +55 51 3933.3000 ext. 3627
http://www.datacom.ind.br

             reply	other threads:[~2017-08-01  0:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  0:12 Carlos Santos [this message]
2017-08-01  0:46 ` Problem building util-linux without a separate ncursesw include dir Carlos Santos
2017-08-01  7:20   ` Karel Zak
2017-08-01 12:09     ` Carlos Santos
2017-08-01 12:44       ` Karel Zak
2017-08-01 22:10         ` Carlos Santos
2018-01-19  2:47     ` Mike Frysinger
2018-01-19  9:40       ` Karel Zak
2018-01-19 18:21         ` Mike Frysinger
2018-01-20 17:50           ` Rüdiger Meier
2018-01-20 18:14             ` Mike Frysinger
2018-01-20 19:31               ` Rüdiger Meier
2018-01-21  2:49                 ` Mike Frysinger
2018-01-20 21:01             ` Bruce Dubbs
2018-01-22  8:50       ` Karel Zak

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=1971282138.2691482.1501546323018.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --cc=util-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.