Release 14 libssl.so.111

ajzimme

ajzimme

Code: 
root@bsdmac:~ # pkg-static install -f pkg
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
    pkg-1.19.1_1

Number of packages to be reinstalled: 1

Proceed with this action? [y/N]: y
[1/1] Reinstalling pkg-1.19.1_1...
[1/1] Extracting pkg-1.19.1_1: 100%
root@bsdmac:~ # pkg upgrade -f
ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pkg"
root@bsdmac:~ #

Currently running: 14.0-CURRENT

Code: 
 git clone https://git.freebsd.org/ports.git /usr/port
Cloning into '/usr/port'...
ld-elf.so.1: Shared object "libssl.so.111" not found, required by "libcurl.so.4"

So, I can't use pkg.
I can't use port snap. Supposedly deprecated.
I can't install ports with git.
Any threads about this error say "we don't support pfsense" but I'm not running pfsense, I'm running regular Current FreeBSD downloaded from this site.

Code: 
root@bsdmac:~ # pkg-static install -f libssl.so
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg-static: No packages available to install matching 'libssl.so' have been found in the repositories

I'm not sure if Current is usable?
Not to mention this is a PPC Mac, but I didn't really have these issues on 13.2; I just wanted to try it.
 
ajzimme said:
I'm not sure if Current is usable?
Click to expand...
It is a development version and especially given the fact, that it is currently undergoing a lot of changes due to the transition to OpenSSL3, breakage like the one you are seeing are to be expected.
If you run a development version, you are expected to be able to fix such problems. If you actually hit some kind of bug or regression, use the developer mailing list, as that is the place where devs hang around.
For that reason, development versions (-CURRENT or -HEAD) aren't supported here on the forums:
forums.freebsd.org

Topics about unsupported FreeBSD versions

The FreeBSD Forums cater primarily to end-users and systems administrators. As such, the Forums focus almost exclusively on FreeBSD versions that are officially supported according to the official FreeBSD website. Since resources are scarce, the FreeBSD Forums strongly suggest that anyone asking...
forums.freebsd.org forums.freebsd.org
 
And regarding the thread title, there is no "Release 14" yet, that's the whole point of -CURRENT being a development snapshot. There's almost never any reason to run -CURRENT other than doing some actual FreeBSD development (which is btw why the snapshots you can download are built with all sorts of debugging options enabled, making them pretty slow compared to -RELEASE builds).
 
ajzimme said:
I'm not sure if Current is usable?
Click to expand...
It always is.

ajzimme said:
Not to mention this is a PPC Mac
Click to expand...
Which is Tier-2, so don't (always) expect up to date packages (could be wrong here though, but the version of pkg it's trying to install shows).
ajzimme said:
So, I can't use pkg.
Click to expand...
You can once you build it for your system.
ajzimme said:
I can't install ports with git.
Click to expand...
You can once you build it for your system.
ajzimme said:
root@bsdmac:~ # pkg-static install -f libssl.so
Click to expand...
That doesn't make sense.

And there is always a way to get ports tree without using any fancy tools like portsnap or git, e.g. just fetch https://github.com/freebsd/freebsd-ports/archive/refs/heads/main.zip (tar should be able to uncompress it).
 
I was just making jollies.
Yes in an extremely dire situation you would pkg-static packages. Not a library kernel module.
 
Actually I got the pkg-static command from a SirDice post towards someone with the same error in 2018. I just wasn't going to bring that thread back from the dead. Thanks guys I really don't like making threads and bothering you over dumb stuff like this, I just couldn't find it... I will just go back to 13.2. ;)
 
Time's change. Nowadays I would probably recommend doing pkg bootstrap -f. Won't solve the problem you're facing now though.

Code: 
     pkg [-46] bootstrap [-fy] [-r reponame]
             Attempt to bootstrap and do not forward anything to pkg(8) after
             it is installed.  With -4 and -6, pkg will force IPv4 or IPv6
             respectively to fetch pkg(8) and its signatures as needed.  If
             the -f flag is specified, then pkg(8) will be fetched and
             installed regardless if it is already installed.  If the -y flag
             is specified, no confirmation will be asked when bootstrapping
             pkg(8).

             If a reponame has been specified, then the configuration for that
             repository will be used.
This is from pkg(7) (/usr/sbin/pkg), not to be confused with pkg(8) (/usr/local/sbin/pkg{,-static}).
 
Well even worse. I'm doing PPC, but I am a masochist and I do not expect any support over the dead platform... it is mainly out of boredom. I'm going to mess with a Nintendo Wii here pretty soon too.
I have noticed though that the pkg install has worked for a lot of stuff on 13.2. I have setup poudriere on a amd64 BSD server and I was going to cross compile on there for some stuff.
 
If this is all of "experimental" nature, maybe you WANT to use -CURRENT (maybe just to get into FreeBSD development?). But then for the very least, you should build/install it from source, so you don't have all the debugging stuff enabled you probably won't use (and you should update it from source somewhat regularly). Then you'll need poudriere to build your own package repository for sure, and to "bootstrap" that, as already suggested, get a ports tree as a simple archive. You should always be prepared for things breaking, so you should learn how to deal with it (having a simple rollback by using e.g. boot environments is recommendable!).

Anyways, -CURRENT won't be supported on these forums, as it really isn't meant for end users. You might want to subscribe to a few mailing lists (freebsd-current@ and maybe also freebsd-ports@ or even freebsd-hackers@ if you want to get into coding).
 
Yeah that's what this machine is for. I am not in a hurry to finish it. And I have settled on BSD for the OS. I am just figuring out how I want to deal with ports and stuff. I have found 13.2 easier for me to deal with. I already have (a separate) poudriere build a lot of ports, but I'm finding out that it is limited on some stuff. I think I will end up sharing that ports dir via NFS. I believe this is what some people do. I also think that this method of jail building is the way forward anyway for making things not break on port upgrade. I am still not sure if poudriere & static qemu is sufficient, or if I should be full scale VM'ing ppc and building that way. I read here that it is much slower that way though. Currently I'm just trying to get xfce4 to work via ports, after I've already built most of the dependencies via pkg.
I am learning now that building dependencies from pkg's is not a great idea.

This is a good way to learn though...doing this on a machine that doesn't matter and I can just mess with it.

Thanks for the suggestions on mailing list. I will join now.
 
You must log in or register to reply here.
Back
Top