<dilyn>
go is an uncomfortable language syntactically sometimes
<noocsharp>
bruh where is libc.so when you compile musl
<noocsharp>
nvm
<noocsharp>
i'm dumb
<dilyn>
it's in the build root:P
<phoebos>
ooh it's in __memcpy_fwd () at src/string/x86_64/memset.s:55
<phoebos>
src/string/x86_64/memset.s: No such file or directory.
<phoebos>
you guys familiar with musl, go figure
<dilyn>
checks out
<phoebos>
mhmhm
<dilyn>
that's odd that you would just... not have memset
<dilyn>
and also NOT have problems
<phoebos>
i mean line 55 is just a mov
<phoebos>
like
<noocsharp>
i think the problem would be in ldso/dynlink.c
<noocsharp>
wait phoebes, did you end up figuring it out?
<noocsharp>
phoebos
<op_4>
would someone be willing to talk me through using tinyramfs? I can't seem to find any docs, and after extracting a config from the test files in the repo, it runs ("creating ramfs structure ..." etc) but doesn't seem to produce anything .. ?
<op_4>
or perhaps point me to somewhere where its usage is outlined
<phoebos>
noocsharp: nope. i don't really have any idea what to do.
<phoebos>
op_4: illiliti is your guru
<op_4>
phoebos: thanks
<noocsharp>
i found the line where it calls memset, now i need to figure out exactly why it's segfaulting
<phoebos>
oh nice
<phoebos>
do you know how to make an object file without an interpreter to test if its just that?
<noocsharp>
patchelf would probably do it, good point, i'm gonna do that myself
<op_4>
hmm, maybe my problem is that i don't have cryptsetup/lvm2 installed
<noocsharp>
it's line 783 of ldso/dynlink.c if you're wondering
<phoebos>
did you find that from printfs
<noocsharp>
indeed
<phoebos>
i am impressed
<noocsharp>
“The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.”
<noocsharp>
– Brian W. Kernighan
<acheam>
when did he say that?
<acheam>
1975 vs 2019 is a big difference
<acheam>
but I agree with the sentiment
humky has quit [Quit: Leaving]
<testuser[m]>
Hi
<midfavila>
nuclear take but if your project is large/complex enough that such a thing is inadequate you're doing something wrong
<midfavila>
also
<midfavila>
late to the punch but yeah fuck mozilla on every level
<midfavila>
they waste their money on political pandering and pay their board way too fucking much all while ignoring what users actually want
<midfavila>
they should have died a while ago
<midfavila>
also hi again op_4
<midfavila>
how's the install going
<noocsharp>
phoebos: it's segfaults because it's trying to memset memory that comes from an mmap without a write flag
<phoebos>
that definitely sounds like a bug
midfavila has quit [Remote host closed the connection]
phinxy has joined #kisslinux
<op_4>
so tinyramfs *almost* works now, except that it's not happy with proc as the device manager or something
notbaby has quit [Quit: Ping timeout (120 seconds)]
notbaby has joined #kisslinux
notbaby has quit [Quit: Client closed]
<dilyn>
^
<dilyn>
specifically (hopefully you check the logs...) you add a white space at the end of that package's version file
<dilyn>
or if a whitespace already exists, you remove it :v
ZombieChicken has joined #kisslinux
<ZombieChicken>
Hello. I'm currently installing kiss in a chroot, but keep getting "Using /usr/bin/su (to become 1000)\nsu: unknown user 1000". I get that the user isn't there, but why that specific user ID number?
Ralph1977 has joined #kisslinux
Guest9227 has joined #kisslinux
illiliti has joined #kisslinux
<illiliti>
ZombieChicken: extract chroot archive as root
<ZombieChicken>
illiliti: That would make sense. Thanks
Ralph1977 has left #kisslinux [#kisslinux]
illiliti has quit [Quit: leaving]
Ralph1977 has joined #kisslinux
tink has joined #kisslinux
<tink>
tip: don't compile your kernel back to back multiple times on your laptop while lying in your bed with it on your lap, this is true especially if the laptop is a modern "ultra-thin" model and has been known for years to have heating issues.
<sad_plan>
yeah, its not on the.. web per say, as no regular browser can access it :')
<midfavila-laptop>
sounds like you're using a pretty crap browser t b q h
<midfavila-laptop>
simply plain http my good man
<sad_plan>
lol, im using lynx atm, so im good too :D
<midfavila-laptop>
hmm
<midfavila-laptop>
looks like they wrote a package manager too
<midfavila-laptop>
"""package manager"""
<midfavila-laptop>
might have to study that
<midfavila-laptop>
then I shall be free from the terrible reign of kiss
<phoebos>
acheam, noocsharp: does IPv6 work for you on obsd? ping6 <a site> doesn't work on the server, and i can't get pf.conf to let me ping6 my server or anything X|
dilyn has joined #kisslinux
<midfavila-laptop>
reading the source code of glazier rn and man, what is it with people and multi-line function declarations?
<midfavila-laptop>
like void\nfunc(int param); instead of just void func(int param);
<sad_plan>
yeah, z3bra wrote an implementation of a package manager. iirc its was for his project of making a distro
<sad_plan>
whats wrong with kiss?
<midfavila-laptop>
it's becoming too...
* midfavila-laptop
shudders
<midfavila-laptop>
dare I say it...
<midfavila-laptop>
mainstream
<sad_plan>
i dont know C, so that doesnt really tell me anything tbh
<sad_plan>
aah
<midfavila-laptop>
once kiss had a reddit I knew it was over
<dilyn>
the ruby tarball makes pax a little mad
<dilyn>
pretty sure you need gnutls sad_plan
<sad_plan>
lol, why?
<midfavila-laptop>
because you can never have enough tls libraries
<sad_plan>
I do have gnutls installed. else icu-networking doesnt build, iirc? its listed as a dep iirc
<dilyn>
hmm
<dilyn>
idr how i fixed this last...
<dilyn>
nothing is different in KISS-kde's ruby. weird
<dilyn>
ignore me I suppose
<sad_plan>
now things got a little messed. mid: why did you *knew* it was over for kiss when got a reddit page?
<noocsharp>
phoebos: i tried ping6ing google, doesn't work
<sad_plan>
dilyn: it builds inside a fresh chroot, but not on my build using xorg, for some reason. I managed to build it semi statically aswell, with libressl
<midfavila-laptop>
that's a complicated question and to answer it we first need to talk about parallel universes, sad_plan
<sad_plan>
^ lol
<sad_plan>
do you belive in paralell universes?
<midfavila-laptop>
alternatively I can just say that I disdain the sort of behavior reddit encourages and don't want to see it in any communities i'm involved in
<dilyn>
testuser[m]: do you happen to know HOW to make pipewire justwerk(tm) as the thing controlling audio devices? it doesn't seem to respect asoundrc, and I have absolutely no clue on how to change the default audio output device...
<sad_plan>
mid: thats fair
<dilyn>
sad_plan: now that is interesting...
<midfavila-laptop>
as for parallel universes, they're certainly an interesting concept, but whether or not I believe in them is not only irrelevant but also a pointless thing to consider since I'll never be able to know if they do or do not exist
<sad_plan>
dilyn: i knoow.. mid: sadly, we're born in the wrong era. too late to discover earth, too early to discover space
<midfavila-laptop>
just in time to BTFO reddit soydevs and save computing
<sad_plan>
yep
<sad_plan>
lol, I was reading the manifesto of bitreich, and it had a section on suckless. and it only says; 'suckless failed'
<midfavila-laptop>
i mean, they did
<midfavila-laptop>
too little activity and not in many areas that matter
<noocsharp>
also phoebos, i just sent an email to the musl mailing list with my diagnosis of the issue
<noocsharp>
the segfaulting one
<sad_plan>
sure. Ive noticed it myself, developement is moving along very slowly.
<sad_plan>
wait, is sfeed made by bitreich? I didn know
<dilyn>
interestingly ruby fails to build on my own machine with kiss but succeeds without kiss :v
<dilyn>
what version of kiss is your chroot using vs your host?
mahmutov has quit [Ping timeout: 240 seconds]
<sad_plan>
uh, lemme check. but I belive its latest on all of them
<sad_plan>
in static build, its 5.5.28
<dilyn>
f
<sad_plan>
what? isnt that the latest?
<dilyn>
yeah
<dilyn>
i'm using 5.5.27 tho
<dilyn>
:P
<sad_plan>
ah. same in my chroot
<sad_plan>
yep, same on all of them
<phoebos>
noocsharp: cool
<sad_plan>
dilyn: why do you use the earlier version anyway?:p
<dilyn>
dylan has a tendency to rework a variable number of things when he updates kiss
<dilyn>
and maintaining two patches for kiss... I don't feel like updating them to conform to whatever he's changed
<dilyn>
for instance he changed that git sources are cached; which means he probably modified chunks of source retrieval. I don't feel like rereading a fair bit of shell just to ensure all the variables line up properly etc
<dilyn>
i'm fine where I am :v
<dilyn>
i'll update after a new release which incorporates all the stuff done between september and now tho
<sad_plan>
I get that. maintaining patches can at times get tedious if the source changes all the time, especially drastically
phinxy has joined #kisslinux
Ralph1977 has quit [Remote host closed the connection]
Guest9227 has quit [Quit: Client closed]
sad_plan has quit [Quit: nyaa~]
ZombieChicken has quit [Quit: WeeChat 3.4]
freem has left #kisslinux [Parting joining some party.]