Marcin or Kurt, Can one of you please try using our most current shar to do a pkg build so I can test? I’d like to eliminate any weirdness with my own poudriere setup. I have a dell machine and can test on either 14 or 15 amd64.
-Dan > On Sep 2, 2025, at 18:21, Dan Mahoney (Ports) <[email protected]> wrote: > > > >> On Sep 2, 2025, at 18:05, Marcin Cieslak <[email protected]> wrote: >> >> On Tue, 2 Sep 2025, Dan Mahoney (Ports) wrote: >> >>> >>> >>>> On Sep 2, 2025, at 17:15, Marcin Cieslak <[email protected]> wrote: >>>> >>>> find /compat/linux -name 'libssl*' -ls >>> >>> root@poudriere-pkb:/home/dmahoney # find /compat/linux -name 'libssl*' -ls >>> 227550 1201 -rwxr-xr-x 1 root wheel >>> 957488 Feb 11 2025 >>> /compat/linux/usr/lib64/libssl.so.3.2.2 >>> 227549 1 lrwxr-xr-x 1 root wheel >>> 15 Feb 11 2025 >>> /compat/linux/usr/lib64/libssl.so.3 -> libssl.so.3.2.2 >>> 226805 1 lrwxr-xr-x 1 root wheel >>> 15 Feb 11 2025 >>> /compat/linux/usr/lib/libssl.so.3 -> libssl.so.3.2.2 >>> 226806 1305 -rwxr-xr-x 1 root wheel >>> 1023516 Feb 11 2025 >>> /compat/linux/usr/lib/libssl.so.3.2.2 >>> 241928 1 lrwxr-xr-x 1 root wheel >>> 83 Sep 2 23:17 >>> /compat/linux/opt/dell/srvadmin/lib64/openmanage/private/libssl.so -> >>> ../../../../../../../../../../../../../../../compat/linux/usr/lib64/libssl.so.3.2.2 >> >> And it does not stat? Maybe there is some another symbolic link accross the >> tree... >> What does the realpath say> > > Realpath works: > > root@poudriere-pkb:/etc/pkg # realpath > /compat/linux/opt/dell/srvadmin/lib64/openmanage/private/libssl.so > /compat/linux/usr/lib64/libssl.so.3.2.2 > > And again, if I use something like md5 (ignoring weaknesses in md5) it shows > the same checksum as /compat/linux/usr/lib64/libssl.so.3.2.2 > > Here’s my current mysteries: > > 1) Why am I hitting this and you aren’t? > > 2) Why does the hard link work and this not? > > 3) Why does it work if I add the *correct* number of ../? > > -Dan
