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:28:40 +0300 (EEST)
Message-ID: <f2eb2b2d-26d-4284-4198-acd6c3427ade@martin.st> (raw)
In-Reply-To: <DM8P223MB03659051AC7C63ECC2E228B7BA67A@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
>> Christopher Snowhill
>> Sent: Mittwoch, 28. Mai 2025 09:40
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel@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.
// 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".
next prev parent reply other threads:[~2025-05-28 8:28 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ö [this message]
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 .
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=f2eb2b2d-26d-4284-4198-acd6c3427ade@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