oprofile's configure.ac contains Bashisms (use of == operator with test built-in). Thus, configure emits errors when /bin/sh is not Bash. This doesn't cause the build to fail outright, but it may be causing misdetection of features.
elif test "`getent passwd oprofile 2>/dev/null`" == "" || \
test "`getent group oprofile 2>/dev/null`" == ""; then
./configure: 22444: test: oprofile:x:105:989:added by portage for oprofile:/dev/null:/sbin/nologin: unexpected operator
./configure: 22445: test: oprofile:x:989:: unexpected operator
Suggest setting CONFIG_SHELL=/bin/bash when running configure. The "unexpected operator" messages above are not present when CONFIG_SHELL=/bin/bash.
I'll look into this, but this is extremely strange: on my systems I use dash as /bin/sh for many years now and had no such problems.
What is you shell?
(In reply to Andrew Savchenko from comment #1)
> I'll look into this, but this is extremely strange: on my systems I use dash
> as /bin/sh for many years now and had no such problems.
> What is you shell?
I use Dash as /bin/sh too.
Dash in Gentoo was only recently unbroken so that Autoconf now uses it by default (unless CONFIG_SHELL is set):
The bug has been closed via the following commit(s):
Author: Andrew Savchenko <email@example.com>
AuthorDate: 2020-08-30 13:01:42 +0000
Commit: Andrew Savchenko <firstname.lastname@example.org>
CommitDate: 2020-08-30 13:05:04 +0000
dev-util/oprofile: version bump
- Update to 1.4.0
- Migrate to GLEP 81
- Add support for doxygen docs build via USE=apidoc
- Remove bash-specific operators from configure
- Add USE="static-libs" to control *.a and *.la installation
Package-Manager: Portage-3.0.3, Repoman-3.0.0
Signed-off-by: Andrew Savchenko <email@example.com>
dev-util/oprofile/Manifest | 1 +
dev-util/oprofile/metadata.xml | 3 ++
dev-util/oprofile/oprofile-1.4.0.ebuild | 87 +++++++++++++++++++++++++++++++++
3 files changed, 91 insertions(+)