From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id A4AF740508 for ; Tue, 21 Dec 2021 06:05:40 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 99A3A68AB71; Tue, 21 Dec 2021 08:05:37 +0200 (EET) Received: from degawa.com (unknown [174.127.109.95]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 5F3BC680073 for ; Tue, 21 Dec 2021 08:05:31 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomderp.com; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date: From:In-Reply-To:References:MIME-Version:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=jo/pY2aHxeH8GUO0ameWfk7NCqlz2Igjb/p5THjWSHo=; b=S4afYpZey3a/ja9wy+ahdxtViU MnM+h5cpZ2g2lfNr7631kZabTwYqUXBSGC0/Lr0UFHL62ZGrFrTTPrbTWxGBqi19o7QrKUvgGTczE HOiseQXto9Hcv3bjEbaEM44xeUh35y8459NsYygz9om7taOva+Hf7CA2LXAbZsoKc7H/YuuB5m/v6 f81mscAa2Z0hgjkzkn1a1KYGPO23iAEDWu4du7joouuKKWKCGuOMXS8MQpBZ3dWraoAS2M345gi1b R4CwSpb10rc35miHQ/Cw64zuBZsrYFfMD+G7cBM1L9U/IcglfcPIr31IJhPuBJSCAb/d2O6yyrHTi 0yMjlgZw==; Received: from mail-vk1-f172.google.com ([209.85.221.172]:37580) by slmp-550-1.slc.westdc.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1mzYHC-0006Wk-29 for ffmpeg-devel@ffmpeg.org; Mon, 20 Dec 2021 23:05:29 -0700 Received: by mail-vk1-f172.google.com with SMTP id g65so4610307vkf.4 for ; Mon, 20 Dec 2021 22:05:29 -0800 (PST) X-Gm-Message-State: AOAM532+PNglgOQxeS4M8BSO3qr4zDOSCmTf4PysCLFOClmndytc0q34 69aN88XC+UVhozdg6kF8kUYVSfoyB1TIbzkmaIo= X-Google-Smtp-Source: ABdhPJyRiD3xgZIxPAR+xMx/qyUqPTrZRvMtf5KRbaWR2o0MfT8LB6H5akOkIej9S1ZwOglk5hAgYHuFccxr9hNZ+dM= X-Received: by 2002:a05:6122:180c:: with SMTP id ay12mr573000vkb.15.1640066728449; Mon, 20 Dec 2021 22:05:28 -0800 (PST) MIME-Version: 1.0 References: <5fb60616-5ded-1b3a-255c-14deb44924d9@evermeet.cx> In-Reply-To: From: Christopher Degawa Date: Tue, 21 Dec 2021 00:04:53 -0600 X-Gmail-Original-Message-ID: Message-ID: To: Aman Karmani X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - slmp-550-1.slc.westdc.net X-AntiAbuse: Original Domain - ffmpeg.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - randomderp.com X-Get-Message-Sender-Via: slmp-550-1.slc.westdc.net: authenticated_id: ccom/from_h X-Authenticated-Sender: slmp-550-1.slc.westdc.net: ccom@randomderp.com X-Source: X-Source-Args: X-Source-Dir: X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [FFmpeg-devel] commits ecee6af8bd and 4ac869ca2a break build for macOS X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Mon, Dec 20, 2021 at 7:53 PM Aman Karmani wrote: > > > On Mon, Dec 20, 2021 at 5:48 PM Christopher Degawa > wrote: > >> >> >> On Mon, Dec 20, 2021 at 7:21 PM Aman Karmani 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. >> > > Thanks for digging in and documenting this behavior. > > It seems like a bug in Xcode to me. Perhaps it's fixed in newer XC, which > is why we're not seeing it? > > It may be worth filing a radar either way. > > As an additional note, just spun up a new mac1.metal instance with macOS 10.15 to see if I could compile ffmpeg with nothing in the system other than build tools and I am getting an error of xcrun: error: unable to find utility "metal", not a developer tool or in PATH and realized that I can't even run xcodebuild because xcodebuild --version xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance It might be better to first check if `$metalcc --version` even runs first before enabling or even checking if metal works _______________________________________________ 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".