From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0EB69C433EF for ; Thu, 9 Jun 2022 19:32:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343547AbiFITcu (ORCPT ); Thu, 9 Jun 2022 15:32:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37258 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241978AbiFITct (ORCPT ); Thu, 9 Jun 2022 15:32:49 -0400 Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id E4A44144BD7; Thu, 9 Jun 2022 12:32:48 -0700 (PDT) Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 259JWcqM010839; Thu, 9 Jun 2022 21:32:38 +0200 Date: Thu, 9 Jun 2022 21:32:38 +0200 From: Willy Tarreau To: Linus Torvalds Cc: Sedat Dilek , Kees Cook , keyrings@vger.kernel.org, Linux Kernel Mailing List , Salvatore Bonaccorso , David Woodhouse , David Howells , Tasmiya Nalatwad , James Bottomley Subject: Re: [Linux v5.17.9] -Wdeprecated-declarations warnings with LLVM-14 and OpenSSL v3.0.x Message-ID: <20220609193238.GD10732@1wt.eu> References: <20220609192308.GB10732@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: keyrings@vger.kernel.org On Thu, Jun 09, 2022 at 12:25:31PM -0700, Linus Torvalds wrote: > On Thu, Jun 9, 2022 at 12:23 PM Willy Tarreau wrote: > > > > IIRC you can also disable the deprecation warnings by defining the > > OPENSSL_SUPPRESS_DEPRECATED macro. It doesn't require to change the > > compiler's options and allows us to put our head in the sand. > > That one had the downside that you have to know what you're doing to > make such a change ;) Sure, but when I had to go through it, I found that it was the one that's used to decide whether another macro would point to either __attribute__((deprecated)) or to an empty string. It was doing exactly the required job for that. My plan was to use it only for default builds but let developers remove it to see new warnings. Finally we did better and disabled engines completely! > I just wanted to be able to start doing pulls again after mistakenly > thinking that an upgrade would be pain-free. :-) Willy