From: Coia Prant <coiaprant@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] fix(configure): fix detection on windows arm64
Date: Fri, 23 May 2025 17:21:11 +0800
Message-ID: <CALj3r0hcRdvHK680EAhiRCskwMt2r=qwTzGStqNE4tmQKhOHYw@mail.gmail.com> (raw)
In-Reply-To: <20250523091129.1593-1-coiaprant@gmail.com>
Also we can check $MSYSTEM_CARCH if it exists
How about your idea?
Coia Prant <coiaprant@gmail.com> 于 2025年5月23日周五 17:11写道:
> On Windows Arm64
> `uname -m` returned `x86_64` instead of `aarch64`
> Link: https://github.com/msys2/msys2-runtime/issues/171
>
> But `uname -s` contains `ARM64` suffix
> So check MSYSTEM on windows arm64 (for clangarm64)
>
> This problem also in VideoLAN/x264
> Link: https://code.videolan.org/videolan/x264/-/merge_requests/177
>
> Signed-off-by: Coia Prant <coiaprant@gmail.com>
> ---
> configure | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/configure b/configure
> index 2e69b3c..1901da3 100755
> --- a/configure
> +++ b/configure
> @@ -4151,12 +4151,15 @@ response_files_default="auto"
> # OS
> target_os_default=$(tolower $(uname -s))
> host_os=$target_os_default
> +msystem=$(tolower $MSYSTEM)
>
> # machine
> if test "$target_os_default" = aix; then
> arch_default=$(uname -p)
> strip_default="strip -X32_64"
> nm_default="nm -g -X32_64"
> +elif test "$msystem" = clangarm64; then
> + arch_default="aarch64"
> else
> arch_default=$(uname -m)
> fi
> --
> 2.49.0.windows.1
>
>
_______________________________________________
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".
prev parent reply other threads:[~2025-05-23 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 9:11 Coia Prant
2025-05-23 9:21 ` Coia Prant [this message]
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='CALj3r0hcRdvHK680EAhiRCskwMt2r=qwTzGStqNE4tmQKhOHYw@mail.gmail.com' \
--to=coiaprant@gmail.com \
--cc=ffmpeg-devel@ffmpeg.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