Re: set -x path always returns 1 on fedora34 on arm64

[Alex fxmbsw7 Ratchev]

good luck and wishes :)

On Wed, May 12, 2021, 13:30 Boleyn Su <boleyn.su@gmail.com> wrote:

> Totally agree. The OS is a customized one shipping a very old dockerd and
> I am in no position to avoid using it. In fact, this is the very reason I
> am using a Fedora container on top of it.
>
> Sent from https://boleyn.su/phone
>
> On Wed, May 12, 2021, 19:19 Boleyn Su <boleyn.su@gmail.com> wrote:
>
>> For running it on an arm64 pc, you can run docker load or something
>> similar to load the image. The bug is not related to arm64 but the outdated
>> container runtime on the arm64 pc I am using. You can check the link to the
>> redhat bug tracker for more details.
>>
>> Sent from https://boleyn.su/phone
>>
>> On Wed, May 12, 2021, 19:05 Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com>
>> wrote:
>>
>>> do you have instructions how to run the container
>>> i have an a64 phone i wanted to try with termux ( and debian inside )
>>> but i dunno to spawn proot yet over the image, i think cause android fault
>>> chroot is not enuff.. but ill try soon
>>>
>>> On Wed, May 12, 2021, 11:58 Boleyn Su <boleyn.su@gmail.com> wrote:
>>>
>>>> I just found someone facing the same issuse
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1900021
>>>>
>>>> On Wed, May 12, 2021, 17:25 Boleyn Su <boleyn.su@gmail.com> wrote:
>>>>
>>>> > I tested that it is the container image to blame by compiling the
>>>> source
>>>> > code from both the host and the container and checking that it only
>>>> breaks
>>>> > in the container. Maybe it is a libc bug or something. I will file a
>>>> bug to
>>>> > Fedora later. Would be great if anyone can test the image. Note that
>>>> the
>>>> > x86_64 image works as expected.
>>>> >
>>>> >
>>>> > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri <
>>>> > andreas.kahari@abc.se> wrote:
>>>> >
>>>> >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote:
>>>> >> > Sorry, it is test -x instead of set -x. There are similar results
>>>> for
>>>> >> test
>>>> >> > - r file, [ -r file] and so on.
>>>> >>
>>>> >> If "[ -r file]" is your code, then it fails because the "[" utility
>>>> >> needs "]" as its last argument, and you are giving it "file]".
>>>> Insert a
>>>> >> space before that last "]".
>>>> >>
>>>> > That is just a typo.
>>>> >
>>>> >> If that is not the code you are using, then consider posting the code
>>>> >> you are using.  If you don't, we can only really say "it works for
>>>> me".
>>>> >>
>>>> >>
>>>> >> >
>>>> >> > On Wed, May 12, 2021, 13:34 Boleyn Su <boleyn.su@gmail.com> wrote:
>>>> >> >
>>>> >> > > Please refer to the subject.
>>>> >> > >
>>>> >>
>>>> >> --
>>>> >> Andreas (Kusalananda) Kähäri
>>>> >> SciLifeLab, NBIS, ICM
>>>> >> Uppsala University, Sweden
>>>> >>
>>>> >> .
>>>> >>
>>>> >
>>>>
>>>