From: "Martin Storsjö via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Cc: "Martin Storsjö" <martin@martin.st>,
"Timo Rothenpieler" <timo@rothenpieler.org>
Subject: Re: [FFmpeg-devel] CI
Date: Fri, 22 Aug 2025 21:48:23 +0300 (EEST)
Message-ID: <8bef33e-2a44-303f-9012-9260655cb51@martin.st> (raw)
In-Reply-To: <26b1768d-e8b4-4c8f-84ce-4207d4399133@rothenpieler.org>
On Fri, 22 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:
> For arm I'm not sure if we really need qemu? All it might take is a
> 32bit arm chroot on aarch64? Not sure if it works like x86 though, where
> a 64bit CPU can also run 32bit code.
It works pretty much like x86, yes - you don't need QEMU, you can run it
natively on an aarch64 kernel.
And you don't need a separate chroot - on Debian/Ubuntu multiarch it's
quite straightforward to install 32 bit arm as a separate architecture:
dpkg --add-architecture armhf
apt-get update && apt-get install g++-arm-linux-gnueabihf libc6:armhf libstdc++6:armhf
This is enough for being able to build things for it, with
--cross-prefix=arm-linux-gnueabihf- and to run the binaries normally.
That said, the very latest generations of aarch64 chips have removed
support for executing in 32 bit mode; luckily the recent github aarch64
runners (which are quite cutting edge otherwise, and have features like
SVE2) still do support 32 bit. But e.g. on Amazon, the Graviton 4 series
no longer supports 32 bit, and the Apple M1 (and newer ones) also lack 32
bit support entirely.
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-08-22 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 23:26 Michael Niedermayer via ffmpeg-devel
2025-08-20 15:56 ` Timo Rothenpieler via ffmpeg-devel
2025-08-20 19:25 ` Michael Niedermayer via ffmpeg-devel
2025-08-20 22:31 ` Timo Rothenpieler via ffmpeg-devel
2025-08-21 16:03 ` Kacper Michajlow via ffmpeg-devel
2025-08-21 21:16 ` Michael Niedermayer via ffmpeg-devel
2025-08-21 21:33 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 5:00 ` Kieran Kunhya via ffmpeg-devel
2025-08-22 12:13 ` Timo Rothenpieler via ffmpeg-devel
2025-08-22 14:51 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 14:54 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 15:22 ` Timo Rothenpieler via ffmpeg-devel
2025-08-22 18:48 ` Martin Storsjö via ffmpeg-devel [this message]
2025-08-22 20:31 ` Michael Niedermayer via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bef33e-2a44-303f-9012-9260655cb51@martin.st \
--to=ffmpeg-devel@ffmpeg.org \
--cc=martin@martin.st \
--cc=timo@rothenpieler.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git