Date: Mon, 8 May 2023 16:11:12 -0400 From: Ed Maste <emaste@freebsd.org> To: Pierre Pronchery <pierre@freebsdfoundation.org> Cc: freebsd-arch@freebsd.org Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc Message-ID: <CAPyFy2D-an-15ePrmKSiomg_-N2-hSawWAYQqOs9NZZTEKFLqQ@mail.gmail.com> In-Reply-To: <CAPyFy2BCvwz7nbvbpbfsXHnst6Z69aCpnGMz2zXz5WkZVyUkEA@mail.gmail.com> References: <C6F8DD52-348E-42D8-84DE-B3A399D2606F@gmail.com> <CAALwa8m7P2daUd9%2BS4oBXqexBrczcXnmL6sGJ8fR4gwJDPDbcg@mail.gmail.com> <12f8559c-d696-5344-98d5-1751d04088af@FreeBSD.org> <u2up6s$mio$1@ciao.gmane.io> <CAPyFy2BCvwz7nbvbpbfsXHnst6Z69aCpnGMz2zXz5WkZVyUkEA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 May 2023 at 16:03, Ed Maste <emaste@freebsd.org> wrote: > > I had a look at the remaining build failures with your changes merged > in, and I see errors due to deprecation notices in: For the simple cases where deprecation notices are the only issue we can just set OPENSSL_API_COMPAT=0x10100000L to specify the API in use explicitly. We can do this in advance of bringing in OpenSSL 3; it will just be a NFC at present. I've done this for bhyve just now, with commit 9c6f3dfda6dd. We can do the same for the other components using OpenSSL, and can switch each of these to using OpenSSL 3 APIs at some point after we import OpenSSL 3.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2D-an-15ePrmKSiomg_-N2-hSawWAYQqOs9NZZTEKFLqQ>