[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEUSe78X7_bwDiHwxS1u0TNTyuqDifoa36yjh=BgcByPp1i86w@mail.gmail.com>
Date: Mon, 4 Dec 2023 08:55:27 -0600
From: Daniel Díaz <daniel.diaz@...aro.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Francis Laniel <flaniel@...ux.microsoft.com>,
stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
allen.lkml@...il.com, Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 5.15 00/69] 5.15.141-rc1 review
Hello!
On Fri, 1 Dec 2023 at 17:05, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Fri, Dec 01, 2023 at 08:34:26AM -0600, Daniel Díaz wrote:
[...]
> > It failed in more architectures than we initially reported. FWIW, this error can be easily reproduced this way:
> >
> > tuxmake --runtime podman --target-arch arm --toolchain gcc-8 --kconfig imx_v4_v5_defconfig
>
> Fails for me:
>
> $ ~/.local/bin/tuxmake --runtime podman --target-arch arm --toolchain gcc-8 --kconfig imx_v4_v5_defconfig
> Traceback (most recent call last):
> File "/home/gregkh/.local/bin/tuxmake", line 8, in <module>
> sys.exit(main())
> ^^^^^^
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/cli.py", line 170, in main
> build.run()
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/build.py", line 652, in run
> self.prepare()
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/build.py", line 318, in prepare
> self.runtime.prepare()
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/runtime.py", line 423, in prepare
> self.prepare_image()
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/runtime.py", line 443, in prepare_image
> do_pull()
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/utils.py", line 36, in retry_wrapper
> ret = func(*args, **kwargs)
> ^^^^^^^^^^^^^^^^^^^^^
> File "/home/gregkh/.local/pipx/venvs/tuxmake/lib/python3.11/site-packages/tuxmake/runtime.py", line 441, in do_pull
> subprocess.check_call(pull)
> File "/usr/lib/python3.11/subprocess.py", line 408, in check_call
> retcode = call(*popenargs, **kwargs)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.11/subprocess.py", line 389, in call
> with Popen(*popenargs, **kwargs) as p:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.11/subprocess.py", line 1026, in __init__
> self._execute_child(args, executable, preexec_fn, close_fds,
> File "/usr/lib/python3.11/subprocess.py", line 1950, in _execute_child
> raise child_exception_type(errno_num, err_msg, err_filename)
> FileNotFoundError: [Errno 2] No such file or directory: 'podman'
>
> Are you sure that's the right command line to use? :)
Yes, it just needs `podman' to be installed. The Tuxmake team will
change that cryptic message into something easier to parse.
FWIW, `--runtime docker` also works (if Docker is installed), and
`--runtime null` simply makes Tuxmake rely on the cross-compilers you
have installed.
Greetings!
Daniel Díaz
daniel.diaz@...aro.org
Powered by blists - more mailing lists