On Tue, Aug 31, 2021 at 2:23 PM Frans de Boer
wrote: On 8/31/21 12:41, Andrei Borzenkov wrote:
On Tue, Aug 31, 2021 at 1:08 PM Frans de Boer
wrote: However, configure - from multiple packages - still complains about the outdated shell version, while previously compiled aarch64 programs are just running in the jail. TW has no pre-compiled bash shell for aarch64, but from what I see in trace output, configure get the proper version data, but does not recognize it. But maybe someone with intimate knowledge about the inner workings of the configure script can decrypt the attached trace output? Command was 'bash -x ./configure 2>&1 | tee db.txt'
To interpret this output configure script itself is needed.
it is - as an example - the output of the configure script of bison-3.7.6. Many others have the same output.
It tries to find shell that can execute shell-compatible script, it calls
/bin/sh -c "script" /bin/bash -c "script"
and apparently all of them fail. There is no information why or what exit code is but it must fail with non-zero exit code. As it is unlikely that script fails, I assume you have problem with calling /bin/bash (or /usr/bin/bash). To that end, I already had made sure that /bin/bash exist for real and
On 8/31/21 15:25, Andrei Borzenkov wrote: that /bin is no link to /usr/bin. Also, the tools I use are bash scripts, which calls other bash scripts without problem - in any /bin configuration. I even made bash statically linked, just like most other tools. All to no avail. That's why it is so hard to understand. Everything works, but not the configure scripts. If only there was a way to cut out the shell check code from configure, but reading and understanding configure is hard to do due to the way it is created :( Frans