NetBSD Problem Report #57461

From www@netbsd.org  Fri Jun  9 23:19:58 2023
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id E53911A923D
	for <gnats-bugs@gnats.NetBSD.org>; Fri,  9 Jun 2023 23:19:57 +0000 (UTC)
Message-Id: <20230609231926.45A961A9241@mollari.NetBSD.org>
Date: Fri,  9 Jun 2023 23:19:26 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: crypto/external/bsd/openssl/lib needs build_install treatment
X-Send-Pr-Version: www-1.0

>Number:         57461
>Category:       lib
>Synopsis:       crypto/external/bsd/openssl/lib needs build_install treatment
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    lib-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 09 23:20:00 +0000 2023
>Closed-Date:    Sat Jun 17 22:08:44 +0000 2023
>Last-Modified:  Sat Jun 17 22:08:44 +0000 2023
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The NetBuildinstall Foundation
>Environment:
>Description:
On update from the openssl11 era to the openssl3 era, updates builds often lead to libssl.so.15 linked against libcrypto.so.14.

This is a consistent problem that many people have hit.  We discussed this on IRC but I forget the details.  Probably crypto/external/bsd/openssl/lib needs the build_install treatment -- either lib/Makefile needs to list each openssl library directly, or we need a way to use bsd.buildinstall.mk in crypto/external/bsd/openssl/lib/Makefile, so that the installed libcrypto.so symlink is definitely updated before libssl.so can be linked.

Incidence of this particular manifestation of the problem will likely diminish as people update their trees to openssl3 and nuke the objdirs to get clean builds, but the underlying problem will likely remain and waste hours of debugging silly problems like when we next have libssl.so.16.
>How-To-Repeat:
build.sh with openssl11
build.sh -u with openssl3
>Fix:
Yes, please!

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Sat, 17 Jun 2023 22:08:44 +0000
State-Changed-Why:
probably fixed by
https://mail-index.netbsd.org/source-changes/2023/06/17/msg145369.html
https://mail-index.netbsd.org/source-changes/2023/06/17/msg145370.html


>Unformatted:

Home	PR Database Search