From: Carlos Santos <casantos@datacom.ind.br>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Problem building util-linux without a separate ncursesw include dir
Date: Tue, 1 Aug 2017 19:10:32 -0300 (BRT) [thread overview]
Message-ID: <1706511560.2888472.1501625432873.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20170801124405.ikj44ulhisvfthnf@ws.net.home>
> From: "Karel Zak" <kzak@redhat.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: util-linux@vger.kernel.org
> Sent: Tuesday, August 1, 2017 9:44:05 AM
> Subject: Re: Problem building util-linux without a separate ncursesw include dir
[...]
>
> We don't have to distinguish between wide and non-wide ncurses when we
> check for header files, because it's already done by
> UL_NCURSES_CHECK() and AC_CHECK_HEADERS() is executed only if we
> already have widechar lib.
>
> Fixed... git-pull and try it.
>
> Karel
Works like a charm. Thanks!
--
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
next prev parent reply other threads:[~2017-08-01 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 0:12 Problem building util-linux without a separate ncursesw include dir Carlos Santos
2017-08-01 0:46 ` 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 [this message]
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=1706511560.2888472.1501625432873.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--cc=kzak@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox