> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > Marvin Scholz > Sent: Mittwoch, 28. Mai 2025 10:57 > To: FFmpeg development discussions and patches <ffmpeg- > de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] Building for Mac x86 with GCC & NASM > > > > On 28 May 2025, at 10:49, softworkz . wrote: > > >> -----Original Message----- > >> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > >> Martin Storsjö > >> Sent: Mittwoch, 28. Mai 2025 10:27 > >> To: FFmpeg development discussions and patches <ffmpeg- > >> de...@ffmpeg.org> > >> Subject: Re: [FFmpeg-devel] Building for Mac x86 with GCC & NASM > >> > >> On Wed, 28 May 2025, softworkz . wrote: > >> > >>>> -----Original Message----- > >>>> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > >>>> Martin Storsjö > >>>> Sent: Mittwoch, 28. Mai 2025 07:55 > >>>> To: FFmpeg development discussions and patches <ffmpeg- > >>>> de...@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). > > > > 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. > > --extra-cflags="-mmacosx-version-min=14.0" \ > > --extra-ldflags="-mmacosx-version-min=14.0 -Wl,-ld_classic > -Wl,-platform_version,macos,14.0,14.0" \ > > Why are you using platform_version? That should not be necessary. Those were all attempts for getting rid of those log messages. It helped for the non-asm objs, then I wasn't sure anymore which one did it and kept it. > 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.. Thanks sw _______________________________________________ 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".
