On Sat, Aug 15, 2020 at 11:30 AM Paul Howarth <paul(a)city-fan.org> wrote:
On Sat, 15 Aug 2020 16:28:47 +0200
Fabio Valentini <decathorpe(a)gmail.com> wrote:
> - autoreconf fails because %build needs a newer shell (protobuf):
>
> /usr/bin/autoconf: This script requires a shell more modern than all
> /usr/bin/autoconf: the shells that I found on your system.
> /usr/bin/autoconf: Please tell bug-autoconf(a)gnu.org about your system,
> /usr/bin/autoconf: including any error possibly output before this
> /usr/bin/autoconf: message. Then install a modern shell, or manually
> run /usr/bin/autoconf: the script under such a shell if you do have
> one. autoreconf: /usr/bin/autoconf failed with exit status: 1
>
> - shell not executing stuff in backticks `command foo` but returns
> empty string (tonto):
> `build-classpath foo` # this doesn't work?
>
>
> I'm getting the sinking feeling that RPM scriptlets are broken? Do
> they get run in the wrong shell? sh instead of bash maybe?
>
> I'm grasping at straws here, but all those build failures are starting
> to be really disruptive to the work that I'm actually trying to do ...
I had an issue with a configure script wanting a more modern shell. I
tried running mock with --isolation-simple and it stopped complaining.
Maybe that would help you too?
Running in simple isolation fixes it for me. This makes me think that
this was broken by the following change listed in the current Rawhide
glibc[1]:
- Linux: Use faccessat2 to implement faccessat (bug 18683)
I suspect that this change is not compatible with nspawn, which is
mock's default mode of operation.
[1]:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1592537
--
真実はいつも一つ!/ Always, there's only one truth!