From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.29-rc2
Date: Thu, 20 Oct 2016 18:28:05 +0200 [thread overview]
Message-ID: <201610201828.05511.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20161020151948.3y47rv5lwmqppubf@ws.net.home>
On Thursday 20 October 2016, Karel Zak wrote:
> On Thu, Oct 20, 2016 at 01:34:24PM +0200, Ruediger Meier wrote:
> > For me it looks like the even the ncurses authors do not like their
> > own pc files. Disabled by default and it's a pain to get them built
> > with correct names and installed in the right location. Even
> > --prefix does not work for their pc files. Plus the backward
> > compatibility problem ...
>
> OK, I have applied:
>
> https://github.com/karelzak/util-linux/commit/e5cc93b5a8854fce80537f8
>6a244977df212dcb5
>
> with ncurses-config and fallback to old good AC_CHECK_LIB.
Thanks!
> We can add fallback to pkg-config too, but it sounds like overkill if
> ncurses-config is everywhere.
>
> It seems drone.io don't like the change
> https://drone.io/github.com/karelzak/util-linux/641 but not sure if
> the problem is our build-system or drone.io.
It finds ncursesw5-config but not the lib. Looks like a packaging bug in
Ubuntu 12.04.
I guess libncursesw5-dev is not installed but ncursesw5-config is from
the installed ncurses-bin. The config script should be in the dev
packages as well as the .pc files.
http://packages.ubuntu.com/precise/amd64/ncurses-bin/filelist
http://packages.ubuntu.com/precise/amd64/libncursesw5-dev/filelist
We don't need to handle such broken installation. In drone.io script you
could try
apt-get install -qq libncursesw5-dev
cu,
Rudi
next prev parent reply other threads:[~2016-10-20 16:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 13:25 [ANNOUNCE] util-linux v2.29-rc2 Karel Zak
2016-10-20 6:03 ` Ruediger Meier
2016-10-20 9:17 ` Karel Zak
2016-10-20 10:25 ` Ruediger Meier
2016-10-20 11:00 ` Karel Zak
2016-10-20 11:34 ` Ruediger Meier
2016-10-20 15:19 ` Karel Zak
2016-10-20 16:28 ` Ruediger Meier [this message]
2016-10-20 16:40 ` Karel Zak
2016-10-20 17:08 ` Ruediger Meier
2016-10-21 14:44 ` Karel Zak
2016-10-21 15:03 ` Ruediger Meier
2016-10-20 19:20 ` Ruediger Meier
2016-12-10 17:15 ` Mike Frysinger
2016-12-12 10:29 ` Karel Zak
2016-12-12 14:31 ` Ruediger Meier
2016-12-12 14:01 ` Ruediger Meier
2016-12-12 14:28 ` Karel Zak
2016-12-12 18:27 ` Mike Frysinger
2016-12-13 11:44 ` Karel Zak
2016-12-12 17:52 ` Mike Frysinger
2016-10-20 17:11 ` Ruediger Meier
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=201610201828.05511.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--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