<r0ni>
the thing that really gets me is the trackpad. even with a firmware update, it's the worst i've ever used. thankful for things like sway that minimize my needs on the trackpad
guido_rokepo has joined #crux-arm
<r0ni>
few things been failing in all my update processing: nss, glibc, libdevmapper and perl
<r0ni>
I did, however, finally get crux-arm to boot on some hardware, rather than a VM after using a new rootfs with updated e2fsprogs I had made.
<beerman>
r0ni no idea if you happen to use gcc 12.3.0 for that, but i had a lot of core ports among others fail with it without the patch I attached to my pr for it
<r0ni>
gcc 12.2.0, which appears to be what's in ports. I see the PR tho, I'll take a look at it
<beerman>
no need, 12.2 didn't have that problem
<beerman>
shouldn't be it then
<r0ni>
nss error seems to be freebl
<beerman>
freebl?
<r0ni>
i'm not sure what/where that comes from
<r0ni>
libfreeblpriv3.so
<r0ni>
seems to me it's part of the nss source
<beerman>
yep
<r0ni>
i do recall something about this update but any other distro i use has stayed on 3.89.1
<beerman>
or haven't upgraded yet. iirc it was released yesterday
<r0ni>
hrm ok the more i dig, the more i see. i think the nss failure is caused by glibc, so if i figure out that, life goes on
<r0ni>
glibc seems to fail to make a dir with a unknown type name 'GNU' lol
<r0ni>
this all seems to stem from coreutils
guido_rokepo has quit [Quit: guido_rokepo]
<r0ni>
attempting to work around things, i've manually built libdevmapper and installed it and used prt-get to update perl, all thats left is glibc. tho prt-get still thinks I need to update libdevmapper
<r0ni>
waiting to see if glibc succeeds or not
<r0ni>
finally got glibc to upgrade! I may or may not have been building the x86 pkg all along, and now finally libdevmapper builds/installs correctly as well
<jaeger>
oops, heh
<r0ni>
hrm.. so installing bash-completion ends up causing footprint mismatches, in turn making pkgs fail to install
<r0ni>
p11-kit is one such package
<beerman>
if thats just new files, you are mostly fine
<beerman>
there is an option in pkgmk.conf/prt-get.conf to ignore only new footprint mismatches
<r0ni>
oh huh didn't know i had a setting i could change! but i just did a "pkgmk -i -if"
<r0ni>
i assume likely does the same thing, just manually
<jaeger>
They're similar but not exactly the same. "-in" ignores only NEW footprint mismatches. "-if" ignores any footprint mismatches.
<r0ni>
ahh so -in is what i should likely train myself to use over -if (in normal situations)