On Wed May 28, 2025 at 1:34 AM PDT, softworkz . wrote: > > >> -----Original Message----- >> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of >> Martin Storsjö >> Sent: Mittwoch, 28. Mai 2025 10:29 >> 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 >> >> Christopher Snowhill >> >> Sent: Mittwoch, 28. Mai 2025 09:40 >> >> To: FFmpeg development discussions and patches <ffmpeg- >> >> de...@ffmpeg.org> >> >> Subject: Re: [FFmpeg-devel] Building for Mac x86 with GCC & NASM >> >> >> >> On Tue May 27, 2025 at 10:54 PM PDT, Martin Storsjö wrote: >> >>> On Tue, 27 May 2025, softworkz . wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I have an issue with the CI builds for Mac in a way that it >> prints >> >>>> tons of lines like this: >> >>>> >> >>>> ld: warning: no platform load command found in >> >> 'libavcodec/libavcodec.a[1008](sao_10bit.o)', assuming: macOS >> >>>> ld: warning: no platform load command found in >> >> 'libavcodec/libavcodec.a[1009](hpeldsp.o)', assuming: macOS >> >>>> ld: warning: no platform load command found in >> >> 'libavcodec/libavcodec.a[1011](huffyuvdsp.o)', assuming: macOS >> >>>> ld: warning: no platform load command found in >> >> 'libavcodec/libavcodec.a[1013](huffyuvencdsp.o)', assuming: macOS >> >>>> >> >>>> >> >>>> These are all about X86AM output. I've had those lines for all .o >> >> files >> >>>> before and was able to get rid of them by adding flags like >> below. >> >>>> >> >>>> Does anybody know how I can avoid those lines for the X86ASM >> output >> >> as well? >> >>>> (don't know much about building for Apple) >> >>> >> >>> 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. >> >>> >> >>> These warnings would go away of nasm could produce the right >> >> platform load >> >>> commands; this is https://github.com/netwide- >> assembler/nasm/pull/13, >> >> but >> >>> there hasn't been much progress on it. (And since the macOS >> >> ecossytem >> >>> mostly is moving away from x86, I guess there's progressively less >> >> effort >> >>> on it as well.) >> >>> >> >>> // Martin >> >> >> >> I do wonder how this is going, since I have never noticed such >> >> messages >> >> while building for x86 from an ARM machine. I continue to support >> x86 >> >> machines all the way down to the minimum spec of current Xcode, >> which >> >> is >> >> 10.13. >> > >> > I don't think you can cross-compile x86 assembler on an arm machine. >> >> Why wouldn't you be able to do that? The assembler is an executable >> like >> any other, taking in source code and outputting object files. You can >> run >> that on any machine. > > I haven't seen any arm binary in nasm's MacOS package. > Is there a nasm package for arm? Then I'm wrong of course!
I install dependencies with Homebrew, both for x86 and arm. Though I don't think I'm using any of them as static or dynamic links. Mostly just nasm and company. I build the x86 and arm versions separately, with x86 min speccing 10.13 and arm targeting 11.0. Then I use lipo to merge them. I also only pick a selection of audio codecs and containers, and no video support. Mainly because my project is an audio player. GPL3 licensed, so it shouldn't be terribly bad that I provide both binaries and the scripts I use to do the building, as well as some unmerged patches I apply. I may some day bother to provide the source code as well, if the license mandates I should have to do that, but I only take unmodified source code, then apply a handful of patches I still need to upstream. Just hadn't gotten around to dealing with filing those mails, as well as designing the test metrics to go into FATE for all the patches that may require new tests. > > 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". _______________________________________________ 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".
