Hi,
Has this been tested at all yet? I would like to know if it works, so
that I can maybe fix it if it doesn't.
On 25/05/2021 12.07, Skyler Mäntysaari wrote:
That command basically executes an container in privileged mode which
enables qemu emulation for mips architecture only.
Docker doesn't emulate it natively per se, which is why the usage of
QEMU is required because otherwise the container will not be able to
even run sed command.
You can read more about that specific container here:
https://github.com/dbhi/qus <https://github.com/dbhi/qus>.
I also wasn't sure where that command should be done as it needs to be
done on the host which is executing the container.
On Mon, May 24, 2021, at 19:18, Ondrej Zajicek wrote:
On Mon, May 24, 2021 at 04:12:33PM +0300, Skyler Mäntysaari wrote:
> Hi!
>
> I hope that this will work and help with the mips package building.
> I originially had forgotten to do the pkg gitlab steps too.
>
> Please let me know if I can help with that in any other way and
disregard the previous patch. This is basically the same one, with
both commits.
Hi
Interesting, i did not know that it can emulate different arch. It is
done natively by Docker, or it is done in those dockerfiles from
multiarch/*, by some integration of qemu?
Also, what exactly this command does:
> + - $DOCKER_CMD --rm --privileged aptman/qus -s -- -p mips
?
We can try it, but it depends of how fast it will be.
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: [email protected]
<mailto:santiago%40crfreenet.org>)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
