Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Building for Mac x86 with GCC & NASM
Date: Wed, 28 May 2025 11:27:20 +0300 (EEST)
Message-ID: <1582d456-2894-2b96-a41a-ca3e8d1da81e@martin.st> (raw)
In-Reply-To: <DM8P223MB0365E1FE7DE888E54B8A0060BA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Wed, 28 May 2025, softworkz . wrote:

>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> Martin Storsjö
>> Sent: Mittwoch, 28. Mai 2025 07:55
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel@ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] Building for Mac x86 with GCC & NASM
>>
>> These warnings appeared since the new linker in Xcode 15.0, 1.5 years
>> ago.
>> I'm not aware of a flag for silencing these warnings; the only way I'm
>> aware of is to force using the old linker by passing -Wl,-ld_classic.
>
> Thanks for the tip. It works to the extent that it prevents those
> messages from appearing and make completes successfully. But almost
> all (4724) fate tests are failing, haven't tried to trace it down.

That sounds odd; it works fine for me (on an arm64 mac).

However this flag isn't a great solution either, since Xcode 16, the 
linker warns "ld: warning: -ld_classic is deprecated and will be removed 
in a future release".

> This led me to a reference indicating that YASM already does it right.
> I tried to build with YASM instead. After disabling HEVC and VVC decoders
> it ran almost to the end, but then it failed on tx_float:
>
> Warning: libavcodec/x86/vp9lpf.o
> skipping strip -x
> Warning: libavcodec/x86/vp9lpf.o
> libavutil/x86/tx_float.asm:1936: error:
> Warning: (PFA_15_FN:21) expression syntax
> Warning: error
> libavutil/x86/tx_float.asm:1937: error: (PFA_15_FN:21)
> Warning: expression syntax error
> make: *** [libavutil/x86/tx_float.o] Error
>
> I don't know whether it can be disabled in some way as it appears to be
> a prerequisite for many codecs and filters?
> Besides that, I suppose that YASM isn't a good idea at all, right?`

I'm not really familiar with the situation about x86 assemblers, but afaik 
yasm is much further behind on many other aspects.

> From a different angle - what do you think would be the most useful
> Mac build for Patchwork CI in general?
> The available runners are macos 13, 14 and 15 - all x86, there's no
> arm yet.
> And would it be better to use Clang like in case of your FATE machines?

I would recommend you to use the Apple provided Clang rather than GCC.

// 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".

  reply	other threads:[~2025-05-28  8:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 22:23 softworkz .
2025-05-28  5:54 ` Martin Storsjö
2025-05-28  7:39   ` Christopher Snowhill
2025-05-28  8:12     ` softworkz .
2025-05-28  8:28       ` Martin Storsjö
2025-05-28  8:34         ` softworkz .
2025-05-28  8:39           ` Martin Storsjö
2025-05-28  8:43             ` softworkz .
2025-05-28  8:43           ` Christopher Snowhill
2025-05-28  8:38       ` Christopher Snowhill
2025-05-28  8:11   ` softworkz .
2025-05-28  8:27     ` Martin Storsjö [this message]
2025-05-28  8:49       ` softworkz .
2025-05-28  8:56         ` Marvin Scholz
2025-05-28  9:08           ` softworkz .
2025-05-28 10:05             ` softworkz .
2025-05-28 10:17               ` Martin Storsjö
2025-05-28 23:19                 ` softworkz .
2025-05-28  8:58       ` softworkz .
2025-05-28  9:02         ` Martin Storsjö
2025-05-28  9:05           ` softworkz .

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=1582d456-2894-2b96-a41a-ca3e8d1da81e@martin.st \
    --to=martin@martin.st \
    --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