Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Christopher Degawa <ccom@randomderp.com>
To: Aman Karmani <ffmpeg@tmm1.net>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS
Date: Mon, 20 Dec 2021 19:48:15 -0600
Message-ID: <CABDPGrzvKXt-Zn31np3MmoJ+xwK2UF5c1s9MU0aULg0hDA0oJA@mail.gmail.com> (raw)
In-Reply-To: <CAK=uwuys+7oZkkzpXLXgcATia82cdEbrJjxn2NjD6_DAsGwZ+w@mail.gmail.com>

On Mon, Dec 20, 2021 at 7:21 PM Aman Karmani <ffmpeg@tmm1.net> wrote:

>
>
> On Mon, Dec 20, 2021 at 5:03 PM Helmut K. C. Tessarek <
> tessarek@evermeet.cx> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On 2021-12-20 19:11, Christopher Degawa wrote:
>> > So I've exported "LIBRARY_PATH" to
>>
>> I'm sorry to say, this is a workaround but hardly a solution.
>>
>
> No one said this is the solution. We are just trying to figure out what is
> going on, and this added information is very helpful in that effort.
>
>
>> Before these 2 commits all worked perfectly. Now it doesn't. Tweaking the
>> build env is not a solution.
>> Next time someone commits something, are we supposed to tweak it again?
>> Where does it end?
>>
>
> I'm not sure what your point is. If you are having trouble with those
> commits, then you can use an older version?
>
> Or you can compile with `./configure --disable-metal` to disable the new
> feature.
>
> Obviously the code worked on both my and Ridley's computers. If it didn't
> work, we wouldn't have committed it.
>
> Once we figure out why some computers are using the wrong metal binary,
> then we can fix it and commit the fix to master as well.
>


Digging a bit into xcrun itself, looking at
https://real-world-systems.com/docs/xcrun.1.html, it says

> The SDK which will be searched defaults to the most recent available SDK

and

xcodebuild -version -sdk | head
iPhoneOS14.3.sdk - iOS 14.3 (iphoneos14.3)
SDKVersion: 14.3
Path:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk
PlatformVersion: 14.3

Which I'm guessing might be the reason, but still doesn't really make
logical sense and running

xcrun --verbose metal -v
...
xcrun: note: SDKROOT = '/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk'
...
xcrun: note: lookup resolved in
'/var/folders/yf/4yc0fdvx7zv1t17w41kxmr0r0000gn/T/xcrun_db' :
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/metal'
Apple LLVM version 31001.43 (metalfe-31001.43)
Target: air64-apple-darwin19.6.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/metal/ios/bin

which also, doesn't make sense.

exporting SDKROOT to `macosx` does make it show

xcrun: note: SDKROOT =
'/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk'

xcrun: note: lookup resolved in
'/var/folders/yf/4yc0fdvx7zv1t17w41kxmr0r0000gn/T/xcrun_db' :
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/metal'
Apple LLVM version 31001.143 (metalfe-31001.143)
Target: air64-apple-darwin19.6.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/metal/macos/bin

so, I'm not sure what conclusion to bring from this.


>
>>
>>
>> - --
>> regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
>> Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
>>
>> /*
>>    Thou shalt not follow the NULL pointer for chaos and madness
>>    await thee at its end.
>> */
>> -----BEGIN PGP SIGNATURE-----
>>
>> iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHBJ/EACgkQvgmFNJ1E
>> 3QDsJg//WzTdNngpbNhCihB0foMLjtL687/1FWqZKPfsCx5pvvLZq/Xj8cd1G2G5
>> XJOehG1YYkjKXE+I1oWBrRxxQ/1mkW49DjX6jyzGUFPvEV+e0yf6f6TUPrE9IYDw
>> nFkIq25rjJMo/+IPxklHw1bIuZxoqo4ohgYHfmcyYJWOPDBXRWCd93GJkbWJy3Cv
>> fRRp4/gIeQJJzlld1ISqGLP6GDIwrevtW7oUwUZbwIWvnJyl25UdnHLAMl82fQPu
>> QnCEuWgRODXI1eaYNXf15MwD6gGy39n7njon4AJ5C63678Yc2H0FfVh6wI9lIv1e
>> LR6WY942ziQx8uqr3y/2IV5wGDSvLZqyEvCMSh199xTcJdfL4WNEZlNS8hlWxN51
>> TfLHBLpjJHqEq2i6+hyaYF4Y3M9ctRa/JVjv1EjciXFWzMx2Ddhehxv0TPu1tY0A
>> UxiQ0By0hJhZDDzOPxez9DgCs/ecmIcUxq4mKuk6KXLIBfJqFrNIN/Mzsn7hBOI7
>> EPLui0+Jo+cWB3AsDRIGNO9UwN+gZAGKxGHt9U9//Af5rzzY0TQ09Z+To14BxD0V
>> lTqDp69JlsutJIpQfOywkPb5ExaFgX7vYZmXEb1f05zlIScIeBRdPxKJ9Sip2Cyo
>> AVzTsQIDTGkNM3KUJE8m3EgrX8V+gJOXKtfK+phUr5YvyhP5IpE=
>> =maKQ
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> 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".
>>
>
_______________________________________________
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".

  parent reply	other threads:[~2021-12-21  1:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 21:30 Helmut K. C. Tessarek
2021-12-20 23:25 ` Ridley Combs
2021-12-20 23:49   ` Helmut K. C. Tessarek
2021-12-21  0:06     ` Ridley Combs
2021-12-21  0:13       ` Helmut K. C. Tessarek
2021-12-21  0:11 ` Christopher Degawa
2021-12-21  0:38   ` Aman Karmani
2021-12-21  0:43     ` Christopher Degawa
2021-12-21  0:50       ` Aman Karmani
2021-12-21  0:54         ` Helmut K. C. Tessarek
2021-12-21  0:52     ` Helmut K. C. Tessarek
2021-12-21  0:54       ` Aman Karmani
2021-12-21  1:18         ` Christopher Degawa
2021-12-21  1:24           ` Aman Karmani
2021-12-21  1:31             ` Christopher Degawa
2021-12-21  1:28           ` Ridley Combs
2021-12-21  1:35             ` Christopher Degawa
2021-12-21  1:03   ` Helmut K. C. Tessarek
2021-12-21  1:20     ` Aman Karmani
2021-12-21  1:35       ` Helmut K. C. Tessarek
2021-12-21  1:39         ` Ridley Combs
2021-12-21  2:31           ` Helmut K. C. Tessarek
2021-12-21  1:48       ` Christopher Degawa [this message]
2021-12-21  1:52         ` Aman Karmani
2021-12-21  6:04           ` Christopher Degawa
2021-12-21  7:39             ` Ridley Combs
2021-12-21 18:04               ` Christopher Degawa

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=CABDPGrzvKXt-Zn31np3MmoJ+xwK2UF5c1s9MU0aULg0hDA0oJA@mail.gmail.com \
    --to=ccom@randomderp.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpeg@tmm1.net \
    /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