From nobody Wed Apr 19 10:58:00 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q1d7362XRz45KGV for ; Wed, 19 Apr 2023 10:58:07 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1d732YfRz4KMG for ; Wed, 19 Apr 2023 10:58:07 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm2 header.b=HM7gZ+S4; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="T SswgoE"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 408EE3200925 for ; Wed, 19 Apr 2023 06:58:04 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 19 Apr 2023 06:58:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1681901883; x=1681988283; bh=Oi6o6euwAMg6T5+6+AAp26pzxafqa7bz+fS NzbCZsUI=; b=HM7gZ+S4GSEbWOmFJYXcw6KGawk41I05wYezpPb2I6SgZ/w6hiM 6ind1Q7Tpab/wXRZIG5RvZN/7TonWZKla5GRJ5HPBGb1qa0mL8EDOd3HLiJqqAkC UWMOQM5FMn8/KufKbuPVlrS8Q91nq7axNg2Z6Dga+ptM+/IDZ55mE47OWH/tjBCb lU1i3lbK6G8dtgDsj1ed/osboMg5W1FQ+2+StU6pLYyypfM+mwovZ8q/2IetvLfj 8HaS3DZnty0yf22T/Zqomxg+QtFuh9X6ioQr4mMQrlT0XSKMLPka62N1RhcDwvYm qzn1iPLC/M0ZK1swPT1NLyt7LF5QIMCQP1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1681901883; x= 1681988283; bh=Oi6o6euwAMg6T5+6+AAp26pzxafqa7bz+fSNzbCZsUI=; b=T SswgoE/DoY5tTBcbfc89hG7sDENI8ojsRiq9+qUMOLyfSTzmg2pAi274lTfN3c4t osmncCiaKkaDc/0LaFMVdy0fv50GNtzZuQtwGp3GYBXOR6Sqmldq8TlXP1liTmaa qwHJYm4ffEFxbFtstH6B3vPJZ9MknPbRdefSjfs62oDjKLVQCXVUasj3I+4Go8K3 GiXhBiHn91ZC9rAwEkaU9bhiFuE8jZta50cN4MN53uHlD4yY2WCRamrKKg6IlaTd Hn1t07ZzSRJD/Wcm5Vt5dOQlxTa6COgiXCup8tW9WrPn7clEPQr9olCIXp+5fwuY VafUMdG/dFN8KBEddnE3Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfedttddgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomhepjghurhhi uceohihurhhisegrvghtvghrnhdrohhrgheqnecuggftrfgrthhtvghrnhepgfeljeduie euhfelueehffehudeiudeuleeufeejjeelfefhvdehhefgleffkeegnecuffhomhgrihhn pedukeejrdhsohenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpeihuhhrihesrggvthgvrhhnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 19 Apr 2023 06:58:03 -0400 (EDT) Message-ID: <1be44824-01e1-b1f8-72e0-73c7c18cda35@aetern.org> Date: Wed, 19 Apr 2023 12:58:00 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Problem with left over files from earlier releases Content-Language: en-US To: FreeBSD questions References: <7898912.iDzAj6rjnq@curlew> From: Yuri In-Reply-To: <7898912.iDzAj6rjnq@curlew> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4Q1d732YfRz4KMG X-Spamd-Bar: / X-Spamd-Result: default: False [-0.40 / 15.00]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm2,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N Mike Clarke wrote: > After the latest round of package upgrades sysutils/vm-bhyve and > graphics/digikam failed to start with the error: > > > ld-elf.so.1: /usr/lib/libelf.so.1: version ELFUTILS_1.0 required by > /usr/local/lib/libdw.so.1 not found > > > Digging around for libelf.so I found: > > > curlew:/home/mike% locate libelf.so.1 > > /usr/lib/libelf.so.1 > > /usr/local/lib/libelf.so.1 > > curlew:/home/mike% ls -l /usr/lib/libelf.so.1 /usr/local/lib/libelf.so.1 > > -r--r--r--  1 root  wheel  90760 30 Apr  2016 /usr/lib/libelf.so.1 > > lrwxr-xr-x  1 root  wheel     15  2 Apr 02:42 > /usr/local/lib/libelf.so.1@ -> libelf-0.187.so > > > It looks like seven year old /usr/lib/libelf.so.1 is left over from an > old version. Booting from a memstick image confirms there is no > /usr/lib/libelf.so.1 in 'out of the box' FreeBSD 13.1 so I deleted it > and both programs worked. But this makes me wonder how many redundant > old files might be lying around in the base system and potentially > causing problems. Is there any easy way to track these down other than > doing a fresh install from scratch? Since I'm intending to upgrade to > 13.2 soon this could be a good time to see if there's more redundant > stuff to clean out. If you are using source upgrades, check list-old* and delete-old* targets in /usr/src/Makefile.