[FFmpeg-devel] Building for Mac x86 with GCC & NASM

[softworkz .]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> softworkz .
> Sent: Mittwoch, 28. Mai 2025 11:09
> To: FFmpeg development discussions and patches <ffmpeg-
> devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Building for Mac x86 with GCC & NASM

[..]
> > > Can you spot any difference to my configure that could be the
> > culprit?
> > >
> > > ./configure --pkg-config-flags="--static" --extra-libs="-lm" \
> >
> > The extra libs here should not be needed.
> 
> Okay, thanks.
> 
> 
> > Also while using the old linker would help with these warnings, I
> dont
> > think its a good thing to
> > do in CI as we would miss issues that only happen with the new
> linker…
> 
> That's a valid point for sure. Another option would be to just disable
> nasm. When it's the exact same tool on all platforms, it might not be
> needed to run that compilation on Mac? I'm not sure..

So, now I've 

- Switched to Clang
- Kept nasm
- Removed ld_classic

All seems well (besides the annoying "platform-load" warnings):

https://dev.azure.com/githubsync/ffmpeg/_build/results?buildId=90983&view=logs


> > I haven't looked into in detail it myself, but it is a known issue
> > since
> > some of the ffmepg multithreading work a couple years ago. It does
> > happen
> > occasionally in all build configurations, more or less often.
> 
> Yup. I thought about patching it in the build, but that's ugly.
> Probably it's better to just disable that test for Mac in the
> code..

PS: If somebody knows a trick to exclude a single fate test, please tell..


Thanks, Martin & Marvin,
consider those builders as FFmpeg assets, when you want to have anything  
changed, just let me know.

sw