From: Karel Zak <kzak@redhat.com>
To: Assaf Gordon <assafgordon@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.30-rc2
Date: Wed, 31 May 2017 11:16:48 +0200 [thread overview]
Message-ID: <20170531091648.3eql47zhfo6sy6sd@ws.net.home> (raw)
In-Reply-To: <89E326AC-7FC7-48E9-8781-02791E0E8A7F@gmail.com>
On Tue, May 30, 2017 at 11:48:46PM -0400, Assaf Gordon wrote:
> Hello,
>
> > On May 30, 2017, at 11:18, Karel Zak <kzak@redhat.com> wrote:
> >
> > On Tue, May 30, 2017 at 01:03:53AM -0400, Assaf Gordon wrote:
> >> /usr/bin/ld: cannot find -lncursesw
> >> collect2: error: ld returned 1 exit status
> >> make[2]: *** [cfdisk] Error 1
> >> ===
> >
> > OK, I had nice afternoon with Debian (after 10 years;-)
>
>
> I'm still seeing this error (tested with util-linux-2.30-rc2-16-2ac1b on
> same Debian 8.1 system).
Ah, I had another issues with ncurses on debian, so I forget to very
this one. Fixed now (I hope).
> +++-=======================-================-================-====================================================
> un libncurses-dev <none> <none> (no description available)
> ii libncurses5:amd64 5.9+20140913-1+b amd64 shared libraries for terminal handling
> ii libncurses5-dev:amd64 5.9+20140913-1+b amd64 developer's libraries for ncurses
> ii libncursesw5:amd64 5.9+20140913-1+b amd64 shared libraries for terminal handling (wide charact
The issue is that we get -lncursesw from pkg-config (probably due to
installed ncursesw-config), but the rest of the build system assumes
non-widechar version. It seems better to use pkg-config as fallback
solution only.
> Also,
> On alpine-linux, the compilation now fails with:
> ===
> CC sys-utils/dmesg-dmesg.o
> sys-utils/dmesg.c:9:26: fatal error: linux/unistd.h: No such file or directory
> compilation terminated.
> Makefile:9274: recipe for target 'sys-utils/dmesg-dmesg.o' failed
> make[2]: *** [sys-utils/dmesg-dmesg.o] Error 1
> ===
> Again, this could be due to missing "linux-headers" package - but is it really the kernel's
> "unistd.h" that's needed, or could this work with the standard one?
The file linux/unistd.h is unnecessary for dmesg (fixed), but we have
many another places where kernel header files are required.
So, now the header file <linux/version.h> is required by ./configure
on Linux. I guess it's not overkill.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-05-31 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 10:50 [ANNOUNCE] util-linux v2.30-rc2 Karel Zak
2017-05-30 5:03 ` Assaf Gordon
2017-05-30 9:27 ` Karel Zak
2017-05-30 13:28 ` Karel Zak
2017-05-30 15:18 ` Karel Zak
2017-05-31 3:48 ` Assaf Gordon
2017-05-31 9:16 ` Karel Zak [this message]
2017-05-31 17:41 ` Assaf Gordon
2017-05-31 18:36 ` Ruediger Meier
2017-05-31 20:05 ` Assaf Gordon
2017-05-31 20:36 ` Ruediger Meier
2017-05-31 20:03 ` 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=20170531091648.3eql47zhfo6sy6sd@ws.net.home \
--to=kzak@redhat.com \
--cc=assafgordon@gmail.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 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.