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 50790404CA for ; Tue, 21 Dec 2021 01:20:46 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C782D68AEAD; Tue, 21 Dec 2021 03:20:44 +0200 (EET) Received: from mail-ua1-f45.google.com (mail-ua1-f45.google.com [209.85.222.45]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 14E4468AE5A for ; Tue, 21 Dec 2021 03:20:38 +0200 (EET) Received: by mail-ua1-f45.google.com with SMTP id a14so21029595uak.0 for ; Mon, 20 Dec 2021 17:20:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ymz4cDSpxw2OgmtiDG3ObUykHq7eHVDLi3xxh84NN1c=; b=tQkF3VPji02cPE77uu6weOzQ5zwhOGZf/oMoTRmBQivYH6bZxiQ2Pdk8dTdqbsfDe0 r/ozt9ZRva2M3BvdYCHxhtNFB6XTQ8blv43E4WcYO0r+9PnJsRm6fReOksAP2fN6Rlou HxMbyxLTpdEQkoFCufdKZt1y40Ps3CVHHzuysX0lv2a5OUHIFAfI0915NPDbI3+SSlv4 r2Wb5ux8dTB2xaqMBTpeEsuusTKMZG4WQg5kqR/1NumX21tRtCupQfgFUV7txjtmf2Y7 sBKvWIWpHzBOTG8MlBi5lrItFUegErt/ydS/4t4j69+hpx4kge4SgcPxgwvBO9b+BzOq vqTA== X-Gm-Message-State: AOAM533GK2wJk9eXc44vNfOeHqTegIpCy1x3IraC3NLAF8xpR2a0TAoV nbQFrBQKAuHTRdwNXb1awm92oEkImZ8QMT+2SflfR20LEKQ= X-Google-Smtp-Source: ABdhPJweUxmV6/U5tGCbospQr7Fdk/U5wL6cMBdjY4Iw6VdJJsEUEYUOygw8WCHjqMHeFLBk0HpFyXoLXEN2jTq3zLI= X-Received: by 2002:ab0:2556:: with SMTP id l22mr392702uan.64.1640049636410; Mon, 20 Dec 2021 17:20:36 -0800 (PST) MIME-Version: 1.0 References: <5fb60616-5ded-1b3a-255c-14deb44924d9@evermeet.cx> In-Reply-To: From: Aman Karmani Date: Mon, 20 Dec 2021 17:20:24 -0800 Message-ID: To: FFmpeg development discussions and patches 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: Christopher Degawa 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 5:03 PM Helmut K. C. Tessarek 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. > > > - -- > 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".