From: Assaf Gordon <assafgordon@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.30-rc2
Date: Wed, 31 May 2017 17:41:40 +0000 [thread overview]
Message-ID: <20170531174139.GA30064@gmail.com> (raw)
In-Reply-To: <20170531091648.3eql47zhfo6sy6sd@ws.net.home>
Hello,
On Wed, May 31, 2017 at 11:16:48AM +0200, Karel Zak wrote:
>On Tue, May 30, 2017 at 11:48:46PM -0400, Assaf Gordon wrote:
>> 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).
Thanks, works now (tested with Debian 8.1, 7.6, Ubuntu 16.04, 15.04,
14.04).
>> On alpine-linux, the compilation now fails with:
>
>So, now the header file <linux/version.h> is required by ./configure
>on Linux. I guess it's not overkill.
Yes, works well and the error message is clear.
Adding linux-headers with `sudo apk add linux-headers` solves the issue.
Now that it builds on alpine-linux, two other issues (not necessarily
show-stoppers for the release):
1.
The test infrastrucutre uses some GNU extensions which aren't
available by default on Alpine-Linux (it has busybox instead of GNU
coreuils). Specifically: ./tests/run.sh uses `#!/bin/bash`, `xargs -P`
and `grep --after-context=1` .
The `grep` at least is easy to fix as busybox's grep supports the
short-option equivalent of `-A1`.
As a work-around, the GNU programs can be installed on alpine with:
sudo apk add findutils bash grep
2.
After installing the gnu programs `make check` works, but few tests
fail:
============
col: multibyte input ... FAILED (col/multibyte)
colcrt: regressions ...
: crash1 ... FAILED (colcrt/regressions-crash1)
: crash2 ... FAILED (colcrt/regressions-crash2)
: hang1 ... FAILED (colcrt/regressions-hang1)
... FAILED (3 from 3 sub-tests)
column: invalid multibyte ... FAILED (column/invalid-multibyte)
fdisk: invalid input tests ... FAILED (fdisk/oddinput)
getopt: options ...
: alternative_option_clash ... FAILED (getopt/options-alternative_option_clash)
: posix_correctly ... FAILED (getopt/options-posix_correctly)
... FAILED (2 from 29 sub-tests)
misc: swaplabel ... FAILED (misc/swaplabel)
rename: exit codes ... FAILED (rename/exit_codes)
utmp: subsecond ... FAILED (utmp/utmpdump-subsecond)
==============
Regarding the 'multibyte' failures - these could stem from musl-libc's differences
(compared to glibc).
'utmp' failure might be because musl-libc does not implement utmp support (only stubs).
I'm happy to test further if you have specific suggestions of what to test.
-----
Lastly,
I've hit a snag when trying to run 'make dist' on the latest version.
make failed with:
===
make[5]: Entering directory `/localdata2/sources/util-linux/po'
File da.new.po does not exist. If you are a translator, you can create it through 'msginit'.
make[5]: *** [da.new.po-create] Error 1
make[5]: Leaving directory `/localdata2/sources/util-linux/po'
===
I have no clue when this is coming from (it didn't fail on in previous builds).
Could be a problem on my system, or something else. Didn't investigate further
(just manually removed 'da.new.*' from po/Makefile).
regards,
- assaf
next prev parent reply other threads:[~2017-05-31 17:41 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
2017-05-31 17:41 ` Assaf Gordon [this message]
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=20170531174139.GA30064@gmail.com \
--to=assafgordon@gmail.com \
--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