"libssl.so.8" not found

[Brad Davis]

On Wed, Dec 16, 2015 at 11:00:19AM +0100, Willem Jan Withagen wrote:
> On 14-12-2015 16:35, Brad Davis wrote:
> > On Mon, Dec 14, 2015 at 06:03:25AM -0700, Warner Losh wrote:
> >> On Mon, Dec 14, 2015 at 2:21 AM, Ronald Klop <ronald-lists at klop.ws> wrote:
> >>
> >>> On Mon, 14 Dec 2015 10:11:35 +0100, Ronald Klop <ronald-lists at klop.ws>
> >>> wrote:
> >>>
> >>> On Mon, 14 Dec 2015 08:18:40 +0100, Matthias Apitz <guru at unixarea.de>
> >>>> wrote:
> >>>>
> >>>> El d??a Sunday, December 13, 2015 a las 10:40:22PM -0800, Russell Haley
> >>>>> escribi??:
> >>>>>
> >>>>> Hi There,
> >>>>>>
> >>>>>> I am trying to bring up an Arm image off the FreeBSD website for my
> >>>>>> hummingboard. The problem seems to be when I run pkg the system installs
> >>>>>> the latest version - 1.6.2, and then fails with:
> >>>>>>
> >>>>>> Shared object "libssl.so.8" not found, required by "pkg"
> >>>>>>
> >>>>>> I've seen this in NextBSD, and DesktopBSD and even on my previous arm
> >>>>>> image
> >>>>>> but I was able to get around the problem by creating links from
> >>>>>> libssl.so.7
> >>>>>> to libssl.so.8.
> >>>>>>
> >>>>>
> >>>>> I have had the same issue on r285885 with ports as well from July this
> >>>>> year and pkg 1.5.5 ... I accidently updated pkg to 1.6.x which could not
> >>>>> find libssl.so.8; I forced back to 1.5.5 with an older pkg-static and
> >>>>> now pkg
> >>>>> complains about it database, but still works:
> >>>>>
> >>>>> $ pkg info pkg
> >>>>> pkg: warning: database version 32 is newer than libpkg(3) version 31,
> >>>>> but still compatible
> >>>>> pkg-1.5.5
> >>>>>
> >>>>> I don't know why pkg 1.6.2 was produced with this recent libssl.so.8; it
> >>>>> should have been done more conservative, IMHO
> >>>>>
> >>>>>         matthias
> >>>>>
> >>>>>
> >>>> I had the same problem on my amd64 laptop. Your FreeBSD version is too
> >>>> old. Upgrading the FreeBSD base will give you the new libssl version. After
> >>>> that you can upgrade your packages.
> >>>>
> >>>> What version of FreeBSD is running on this hummingboard? I guess
> >>>> 11-CURRENT. Probably ssl was upgraded in FreeBSD and the new packages are
> >>>> build on this newer version. In 10-STABLE this is kept backwards
> >>>> compatible, but in 11-CURRENT you have to keep up yourself.
> >>>>
> >>>> Regards,
> >>>>
> >>>> Ronald.
> >>>>
> >>>
> >>> It has to do with this message in /usr/src/UPDATING:
> >>>
> >>>
> >>> https://svnweb.freebsd.org/base/head/UPDATING?r1=290206&r2=290207&pathrev=292177&
> >>
> >>
> >> As a temporary measure, for bootstrapping or installing packages, you can
> >> also
> >> use libmap.conf to map libssl.so.7 to libssl.so.8. There's a second library
> >> that
> >> you'll find you need to map too. This will get you over the hump. However,
> >> once you do upgrade, you'll need to remove the lines because slogin and such
> >> have a check for the right version of openssl, and will give an error
> >> message if
> >> you try to use them cross-threaded.
> > 
> > Or just use pkg-static. :)
> 
> Cool trick, never though about that.
> However that does not help with auxilary tools that are code to use pkg. :(
> 
> So in the end I just manually build the pkg port, which will compile
> against whatever is available as ssl-lib. Not the best solution, since
> next time Bapt releases a new version, the game starts again.

No.  This was caused by ssl being bumped, not pkg.  Pkg is updated
regularly without this issue.

> perhaps in this case it is best to move pkg-static to pkg?
> and always use a static linked version. It is not like a deamon running
> for ever. So the temporary overhead of 4Mb <> 150K code space would be
> acceptable.

There is talk about making the static version the default.


Regards,
Brad Davis