Also we can check $MSYSTEM_CARCH if it exists How about your idea?
Coia Prant <coiapr...@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 <coiapr...@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-requ...@ffmpeg.org with subject "unsubscribe".
