Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Jul 2023 11:46:39 +0100
From:      Nuno Teixeira <eduardo@freebsd.org>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pkg" and others
Message-ID:  <CAFDf7UKF9UZ3HR=9Ssuw%2Bs8-tPZBJvHT=3AWUrwPLpdbNm4D6A@mail.gmail.com>
In-Reply-To: <1AB46452-89CC-4879-BBBB-EA2B9BD04DC8@yahoo.com>
References:  <1AB46452-89CC-4879-BBBB-EA2B9BD04DC8.ref@yahoo.com> <1AB46452-89CC-4879-BBBB-EA2B9BD04DC8@yahoo.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
Hello Mark,

Yes, I will start building my own ports as well as I do it before.

I'm using poudriere jail:
---
14amd64  14.0-CURRENT 1400092 amd64 src=/usr/src
---
That I update each time I update main, but it could also be null mount too.

Thanks,

Mark Millard <marklmi@yahoo.com> escreveu no dia domingo, 2/07/2023 à(s)
09:15:

> Nuno Teixeira <eduardo_at_freebsd.org> wrote on
> Date: Sun, 02 Jul 2023 05:22:48 UTC :
>
> > I'm returning to current and installed from
> > 20230622-b95d2237af40-263748-bootonly.iso
> > <
> https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-amd64-20230622-b95d2237af40-263748-bootonly.iso
> >
> > and upgraded to cab2d43b83b (amd64).
> >
> > Did a magnific delete-old and delete-old-libs and now a lot of packages
> > complain about "ld-elf.so.1: Shared object "libssl.so.111" not found,
> > required by..."
> >
> > To fix it I rebooted with BE from first instalation since I used
> > beinstall.sh for upgrade.
> >
> > I know that a lot of things happened in the last days with
> llvm15->llvm16,
> > openssl3, etc.
> >
> > My question is when can I do a delete-old{-libs}?
> > I'm thinking building pkgs with a updated current on poudriere and then
> > clean up libs?
>
> The world in use for building packages from ports (such as in the
> poudriere jail if poudriere is used), should not have libssl.so.111
> or libcrypto.so.111 present.
>
> I've two files (using amd64 as an example):
>
> A) ~/origins/amd64-origins.txt
> B) ~/origins/amd64-pkgs.txt
>
> (A) lists the ports I want to build (but not what those are dependent on).
> (B) lists the packages I want to install (but not what those are dependent
> on).
>
> The two have to list flavors in different notations, so having just one
> file
> ends up not being sufficient. Given that I use poudriere, neither file
> lists
> ports-mgmt/pkg explicitly.
>
> To build I use:
>
> # more ~/build-ports-main-amd64-all_ports.sh
> #! /bin/sh
> poudriere pkgclean -jmain-amd64 -A
> poudriere bulk -jmain-amd64 -w -f ~/origins/amd64-origins.txt
>
> (You might not want the -w . Also, I have poudriere null mount my own world
> build's installation for use by the jail. In the current context, no
> libssl.so.111 or libcrypto.so.111 is present in the jail for the bulk run.)
>
> To install I use:
>
> # more ~/pkg-update-amd64-sys.sh
> #! /bin/sh
> pkg update \
> && pkg install -f ports-mgmt/pkg \
> && pkg delete -a \
> && pkg install `cat ~/origins/amd64-pkgs.txt`
>
> (Note: ports that fail to build need to not be listed in
> ~/origins/amd64-pkgs.txt .)
>
> I deal with delete-old-libs after the packages are installed.
> I do not have any extra non-port software that would need
> rebuilding.
>
> (In my context, I do all this activity as root.)
>
> ===
> Mark Millard
> marklmi at yahoo.com
>
>

-- 
Nuno Teixeira
FreeBSD Committer (ports)

[-- Attachment #2 --]
<div dir="ltr"><div>Hello Mark,</div><div><br></div><div>Yes, I will start building my own ports as well as I do it before.</div><div><br></div><div>I&#39;m using poudriere jail:</div><div>---<br></div><div>14amd64  14.0-CURRENT 1400092 amd64 src=/usr/src</div><div>---</div><div>That I update each time I update main, but it could also be null mount too.</div><div><br></div><div>Thanks,<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Mark Millard &lt;<a href="mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>&gt; escreveu no dia domingo, 2/07/2023 à(s) 09:15:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Nuno Teixeira &lt;<a href="http://eduardo_at_freebsd.org" rel="noreferrer" target="_blank">eduardo_at_freebsd.org</a>&gt; wrote on<br>
Date: Sun, 02 Jul 2023 05:22:48 UTC :<br>
<br>
&gt; I&#39;m returning to current and installed from<br>
&gt; 20230622-b95d2237af40-263748-bootonly.iso<br>
&gt; &lt;<a href="https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-amd64-20230622-b95d2237af40-263748-bootonly.iso" rel="noreferrer" target="_blank">https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-amd64-20230622-b95d2237af40-263748-bootonly.iso</a>&gt;<br>;
&gt; and upgraded to cab2d43b83b (amd64).<br>
&gt; <br>
&gt; Did a magnific delete-old and delete-old-libs and now a lot of packages<br>
&gt; complain about &quot;ld-elf.so.1: Shared object &quot;libssl.so.111&quot; not found,<br>
&gt; required by...&quot;<br>
&gt; <br>
&gt; To fix it I rebooted with BE from first instalation since I used<br>
&gt; beinstall.sh for upgrade.<br>
&gt; <br>
&gt; I know that a lot of things happened in the last days with llvm15-&gt;llvm16,<br>
&gt; openssl3, etc.<br>
&gt; <br>
&gt; My question is when can I do a delete-old{-libs}?<br>
&gt; I&#39;m thinking building pkgs with a updated current on poudriere and then<br>
&gt; clean up libs?<br>
<br>
The world in use for building packages from ports (such as in the<br>
poudriere jail if poudriere is used), should not have libssl.so.111<br>
or libcrypto.so.111 present.<br>
<br>
I&#39;ve two files (using amd64 as an example):<br>
<br>
A) ~/origins/amd64-origins.txt<br>
B) ~/origins/amd64-pkgs.txt<br>
<br>
(A) lists the ports I want to build (but not what those are dependent on).<br>
(B) lists the packages I want to install (but not what those are dependent on).<br>
<br>
The two have to list flavors in different notations, so having just one file<br>
ends up not being sufficient. Given that I use poudriere, neither file lists<br>
ports-mgmt/pkg explicitly.<br>
<br>
To build I use:<br>
<br>
# more ~/build-ports-main-amd64-all_ports.sh <br>
#! /bin/sh<br>
poudriere pkgclean -jmain-amd64 -A<br>
poudriere bulk -jmain-amd64 -w -f ~/origins/amd64-origins.txt<br>
<br>
(You might not want the -w . Also, I have poudriere null mount my own world<br>
build&#39;s installation for use by the jail. In the current context, no<br>
libssl.so.111 or libcrypto.so.111 is present in the jail for the bulk run.)<br>
<br>
To install I use:<br>
<br>
# more ~/pkg-update-amd64-sys.sh<br>
#! /bin/sh<br>
pkg update \<br>
&amp;&amp; pkg install -f ports-mgmt/pkg \<br>
&amp;&amp; pkg delete -a \<br>
&amp;&amp; pkg install `cat ~/origins/amd64-pkgs.txt`<br>
<br>
(Note: ports that fail to build need to not be listed in<br>
~/origins/amd64-pkgs.txt .)<br>
<br>
I deal with delete-old-libs after the packages are installed.<br>
I do not have any extra non-port software that would need<br>
rebuilding.<br>
<br>
(In my context, I do all this activity as root.)<br>
<br>
===<br>
Mark Millard<br>
marklmi at <a href="http://yahoo.com" rel="noreferrer" target="_blank">yahoo.com</a><br>
<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committer (ports)</span></div></div>
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UKF9UZ3HR=9Ssuw%2Bs8-tPZBJvHT=3AWUrwPLpdbNm4D6A>