Date: Wed, 24 Jan 2024 17:56:16 -0300 From: Eduardo Lemos de Sa <eduardo.lemosdesa@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: Frank Leonhardt <freebsd-doc@fjl.co.uk>, freebsd-questions@freebsd.org Subject: Re: "libcap_fileargs.so.1" not found Message-ID: <CA%2BnjGkvpnpy3DcXiKCwx3wa0EHn7pA163OgPSc_FGFztMHTU4w@mail.gmail.com> In-Reply-To: <ff11311a-52eb-4f2a-999e-b5b22f442f1b@nomadlogic.org> References: <542ee99a-c27f-4127-a723-abc0a77dd2fe@fjl.co.uk> <ff11311a-52eb-4f2a-999e-b5b22f442f1b@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Dear On Wed, Jan 24, 2024 at 3:08 PM Pete Wright <pete@nomadlogic.org> wrote: > > On 1/24/24 04:20, Frank Leonhardt wrote: > > This may have a simple fix, but it involves binary packages and these > > aren't my thing... > > > > This is a plain machine I keep as a reference for the latest version > > of FreeBSD. In December I tried to "upgrade" it 14, but the result > > didn't work out so I reverted to 13.2. All seemed okay. > > > > Except "wc" now barfs with 'ld-elf.so.1: Shared object > > "libcap_fileargs.so.1" not found, required by "wc"' > > > > libcap_fileargs.so.1 is present and correct, as far as I can tell: > > > > -r--r--r-- 1 root wheel 12684 Dec 8 17:23 > > /usr/lib32/libcap_fileargs.so.1 > > -r-xr-xr-x 1 root wheel 13744 Dec 8 17:23 /usr/bin/wc.broken > > > > Other files in /usr/bin have the same timestamp but those I've tried > > seem to work just fine. > > > > To get me moving I've simply recompiled wc.c, but I'd like to know > > what's going on here. Did the rolled-back upgrade to 14 not roll back > > fully, and what's the "official" solution? > > > I think you'll need to provide more information before people can help you. > > > How did you perform the upgrade from 13.2-RELEASE to 14.0-RELEASE? > freebsd-update, build from source? > > How and at what point did the upgrade fail? > > How did you revert your system back to 13.2-RELEASE? > > I'm guessing you have a mixed userland right now where there are some > binaries that are linked against incorrect libraries. IMHO I would try > to complete the upgrade to 14.0-RELEASE as solving for that would ensure > you can update the future releases. > > -pete > > -- > Pete Wright > pete@nomadlogic.org > > > I did a update from source (using git). I compiled world, kernal. Before to do a restart, I update and upgrade all packages (pkg utility). Everything went fine. My best wishes Eduardo -- Eduardo Lemos de Sa Professor Titular Dep. Quimica da Universidade Federal do Paraná fone: +55(41)3361-3300 fax: +55(41)3361-3186 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr">Dear</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 24, 2024 at 3:08 PM Pete Wright <<a href="mailto:pete@nomadlogic.org">pete@nomadlogic.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> On 1/24/24 04:20, Frank Leonhardt wrote:<br> > This may have a simple fix, but it involves binary packages and these <br> > aren't my thing...<br> ><br> > This is a plain machine I keep as a reference for the latest version <br> > of FreeBSD. In December I tried to "upgrade" it 14, but the result <br> > didn't work out so I reverted to 13.2. All seemed okay.<br> ><br> > Except "wc" now barfs with 'ld-elf.so.1: Shared object <br> > "libcap_fileargs.so.1" not found, required by "wc"'<br> ><br> > libcap_fileargs.so.1 is present and correct, as far as I can tell:<br> ><br> > -r--r--r-- 1 root wheel 12684 Dec 8 17:23 <br> > /usr/lib32/libcap_fileargs.so.1<br> > -r-xr-xr-x 1 root wheel 13744 Dec 8 17:23 /usr/bin/wc.broken<br> ><br> > Other files in /usr/bin have the same timestamp but those I've tried <br> > seem to work just fine.<br> ><br> > To get me moving I've simply recompiled wc.c, but I'd like to know <br> > what's going on here. Did the rolled-back upgrade to 14 not roll back <br> > fully, and what's the "official" solution?<br> ><br> I think you'll need to provide more information before people can help you.<br> <br> <br> How did you perform the upgrade from 13.2-RELEASE to 14.0-RELEASE? <br> freebsd-update, build from source?<br> <br> How and at what point did the upgrade fail?<br> <br> How did you revert your system back to 13.2-RELEASE?<br> <br> I'm guessing you have a mixed userland right now where there are some <br> binaries that are linked against incorrect libraries. IMHO I would try <br> to complete the upgrade to 14.0-RELEASE as solving for that would ensure <br> you can update the future releases.<br> <br> -pete<br> <br> -- <br> Pete Wright<br> <a href="mailto:pete@nomadlogic.org" target="_blank">pete@nomadlogic.org</a><br> <br> <br> </blockquote></div><br clear="all"><div>I did a update from source (using git). I compiled world, kernal. Before to do a restart, I update and upgrade all packages (pkg utility).</div><div>Everything went fine.</div><div><br></div><div>My best wishes</div><div><br></div><div>Eduardo</div><div><br></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eduardo Lemos de Sa<br>Professor Titular<br>Dep. Quimica da Universidade Federal do Paraná<br>fone: +55(41)3361-3300<br>fax: +55(41)3361-3186<br></div></div></div></div></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BnjGkvpnpy3DcXiKCwx3wa0EHn7pA163OgPSc_FGFztMHTU4w>