From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> 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 10:05:18 +0000 Message-ID: <DM8P223MB0365591C1636628581D0900CBA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <DM8P223MB0365F593406BF1B82D9C3937BA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > softworkz . > Sent: Mittwoch, 28. Mai 2025 11:09 > To: FFmpeg development discussions and patches <ffmpeg- > devel@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 _______________________________________________ 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".
next prev parent reply other threads:[~2025-05-28 10:05 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ö 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 . [this message] 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=DM8P223MB0365591C1636628581D0900CBA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --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