phoebos changed the topic of #kisslinux to: Unofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://yewtu.be/watch?v=S81bNIK4MaE
Den4ikRus has quit [Ping timeout: 245 seconds]
<midfavila> oh my god why do people use meson to build C projects with like 5 files and zero complicated shit going on
<jason123onirc> I tried to install glasnost but its failing on llvm so I don't think it works
<sewn> midfavila: because of complicated dependencies
<sewn> and advanced file generation
<sewn> OTHERWISE it doesn't really make sense to use meson
dilyn has joined #kisslinux
<dilyn> what's llvm failing on, jason123onirc?
<dilyn> wak is adorable. also
<dilyn> > #!/usr/local/bin/tcc -run -funsigned-char
<dilyn> I love putting compilers in my shebangs
<dilyn> I've written a handful of scripts in golang just to meme on my coworkers
fitrh has joined #kisslinux
<riteo> lmao I just realized that we have a saying in neapolitan that's so italian-sounding
<riteo> I can't seriously think right now of a more idiomatic translation but it goes roughly as follows: "with the mouth you eat pasta"
<riteo> which means basically "talk is cheap"
fitrh has quit [Ping timeout: 240 seconds]
fitrh has joined #kisslinux
fitrh has quit [Remote host closed the connection]
fitrh has joined #kisslinux
<riteo> fellas, is it worth it to get a domain?
<riteo> looks like I can get one for a buck a month which might be doable
<riteo> and I wanna make a blog
fitrh has quit [Ping timeout: 244 seconds]
<phoebos> do it
<riteo> nice
<riteo> my mama said that I can!!!!1!11!!111!
<riteo> wahoo I'm gonna get my own personal bloggy
fitrh has joined #kisslinux
<sewn> yyipeye iey epe yipe ye
<sewn> whatru gonna put it on it riteo
fitrh has quit [Quit: fitrh]
<riteo> sewn I'm gonna put it up on codeberg pages for now
<riteo> because I don't wanna ask mama and papa too many recurring payments
<riteo> im bby
<riteo> wait I might've mis-parsed the message
<riteo> I'm gonna mainly put ramblings on there :P
<riteo> like, as you might know I'm a godot maintainer and I do a lot of wayland things, some of which will need quite a bit of work, so I want to put my plans there too
<riteo> maybe stuff about my projects or even my notes in HTML form i dunno
<sewn> wayland things?? woa
<sewn> what do u do
<sewn> i was told before to make blog posts about how to deal with wl_shim boilerplate and making applications (including boiletplate) but too much wor
<jason123onirc> dilyn: I don't even remember
<midfavila> sewm this is for chimera's portable freebsd diff
<midfavila> sewn
<midfavila> literally like five files with no deps other than libc
<midfavila> just astonishing
<sewn> good or bad
dilyn has quit [Quit: Client closed]
<riteo> sorry sewn I was too excited setting things up
<riteo> also life
<riteo> btw, I'm working on the godot wayland backend
<riteo> it's already usable in the latest release but it's not up to parity to the X11 backend, especially since the Godot windowing API is obviously very different from the wayland stuff
<riteo> Things are slowly getting into place and I'm sure I can add the missing stuff but now I don't have a lot of time, hence my need for better planning
* riteo screams very lightly inside
<riteo> also, now there's a new feature that allows embedding of the running game in the editor and it's apparently more important so I'll move all my efforts to it
<riteo> double the reason for making nice notes since it will be very painful although perfectly doable
<riteo> like, client embedding is a design strenght of wayland, since everything is a nice asynchronous protocol. The solution is to literally make a stripped-down sub-compositor and put it into a surface
<riteo> that's something that web browsers do too apparently, which is super cool
<riteo> fellas, I'm proud to announce that I have finally a space, courtesy of codeberg pages: riteo.dev
<riteo> (there's only a placeholder page for now)
examors has quit [Quit: WeeChat 4.4.3]
<sewn> are you getting paid for thise
<sewn> what does ur pfp mean btw
<riteo> sewn no I'm not getting paid for this
<riteo> it's all voluntary work
<riteo> the advantage is that I can work on my own terms since, well, I don't have any obbligations :P
<riteo> would love to do this as my dayjob though
<riteo> my pfp is linked to my name
<riteo> basically this fella I know made a conlang, along with an alphabet. My name is a distortion of a word from there and the pfp is a "simplification" of the "R" character from said alphabet
<riteo> like an abstract interpretation, you could say
<sewn> riteo??27;2;13~
<riteo> what
<sewn> thats the story??
<sewn> so cool
<sewn> what was your name before that then
<sewn> atleast on the internet
<riteo> oh I can tell you if you want, it's not that cool actually lol
<sewn> when did chagne and what was it
<riteo> my original name was... well, who cares I was a kid lol, DiamondMinerITA
<riteo> since, well, I wanted to play minecraft and I was literally 10 years old
<riteo> eventually all my friends called me "diamond"
<riteo> and since I wanted something more cool-sounding I looked the dictionary and, after some thinking, settled on "liteo", which means "diamond" in this conlang
<riteo> liteo was too... weird so I simply changed the first letter lol
<sewn> chinese pronounciation of riteo i see
<riteo> more like japanese translitteration lol
<sewn> oh right
<riteo> and well that's it really
<sewn> ok but wen was c hange
<riteo> quite a few years ago
<riteo> I think 2018?
<riteo> 2020 tops
<sewn> very coo
<midfavila> hey, having a weird issue bootstrapping gcc (again)...
<midfavila> using 14.2.0 with only CFLAGS being -L/usr/lib -I/usr/include to override internal paths and point at the system's libs
<midfavila> fails when building libgcc because ld can't find the C library
<midfavila> i've already run a sanity test even assuming the rest of the builds i've run weren't good enough, aka literally everything for a core kiss install excepting gcc
<midfavila> ld can very much find the C library, both shared and static, and link without issue. i've tried setting LD_LIBRARY_PATH as well as setting ldflags and i'm honestly not sure where to go from here
<midfavila> i can't wait until i can write gcc off for the core system...
<sewn> llvm :3
<ukky> midfavila: take a look at https://github.com/apexrtos/musl-cross-make
<ukky> there is also clang branch for cross-clang-musl
<midfavila> i'm not building a cross compiler
<midfavila> i mean i guess i could give a different toolchain a shot but ughhhhh
<midfavila> i want this to be over already
<riteo> mid you like my domain
<riteo> I seriously thought I'd be ripping my hair off to get it or something
<riteo> I just... Told some basic-ish info about me, paid actually very little money and waited a few minutes for the dns to propragate
<ukky> midfavila: what is the 'ld' library search path?: ld --verbose | grep SEARCH_DIR
<midfavila> SEARCH_DIR("=/riscv64-linux-musl/lib64/lp64d"); SEARCH_DIR("=/riscv64-linux-musl/lib64"); SEARCH_DIR("=/riscv64-linux-musl/lib6464/lp64d"); SEARCH_DIR("=/usr/local/lib64/lp64d"); SEARCH_DIR("=/usr/local/lib64"); SEARCH_DIR("=/lib64/lp64d"); SEARCH_DIR("=/lib64"); SEARCH_DIR("=/usr/lib64/lp64d"); SEARCH_DIR("=/usr/lib64"); SEARCH_DIR("=/riscv64-linux-musl/lib"); SEARCH_DIR("=/usr/local/lib");
<midfavila> SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib");
<midfavila> ukky
<midfavila> this is in a chroot and it's the only toolchain in PATH so there should be no reason it can't find the C library
<midfavila> especially considering like i said i was able to build every other package under repo/core
<midfavila> the toolchain is the riscv64-linux-musl-14.2.0 one from skarnet
<midfavila> it's, aside from that, a vanilla KISS env built by hand following the buildscripts exactly
<ukky> midfavila: You said it is not a cross-compiler. But your 'ld' was built with '--with-sysroot' parameter. You should not do that for native toolchain.
<ukky> All your search path locations are relative to sysroot. That's why you have '=' sign in front of every location.
<midfavila> no, what i mean is that i'm not building one
<midfavila> but yes i'm aware that they're relative to sysroot. i don't see why that would be relevant only halfway through building gcc. like i said, i can build everything else under repo/core without trouble. i suppose if that was potentially causing the problem though, is there a way to change what's considered the sysroot for ld's purposes?
<midfavila> furthermore wouldn't that be irrelevant when specifying paths using -L and LD_LIBRARY_PATH?
<midfavila> legitimately curious
<ukky> I think LD_LIBRARY_PATH is not used by ld(1). LD_LIBRARY_PATH is used by ld.so
ehawkvu has joined #kisslinux
<ehawkvu> phoebos: any reason we don't have kisslinux's `init` repo forked? I was going to hack on it to add GNU shepherd support
<ehawkvu> at least using shepherd as the service manager ^^
<midfavila> shit you're right ukky
<midfavila> i don't know why i thought bfd used it
<ukky> midfavila: For failing build, try adding this to CFLAGS: -Wl,--verbose <= This might display in which directories 'ld' looks for libc.a
<midfavila> nothin' different
<midfavila> alas
<midfavila> it seems like when libgcc's build invokes mkinstalldirs that's when it loses it...
* midfavila groans, rubs at his temples
<midfavila> wow this fucking blows.
<midfavila> i honestly just want to give up for now and wait until i get my workstation
<midfavila> i've wasted weeks on this
<ehawkvu> midfavila: I know the pain
<ehawkvu> Java 8 still eludes me
<midfavila> i just
<midfavila> like
<midfavila> bro holy shit i understand that a compiler is complex okay
<midfavila> but my god
<midfavila> navigating gcc is like trying to escape a labyrinth
<jason123onirc> what init systems does kiss support?
<midfavila> i mean officially it's just busybox
<midfavila> but it's not hard to swap it out
<phoebos> ehawkvu: we have it forked
<ehawkvu> phoebos: sorry i was on the github repo and saw it archived and figured we left it when we left github
<ehawkvu> phoebos: it seems like the one on codeberg does not have the recent commits though?
<ehawkvu> like we are missing kall.c & the updated readme
<ehawkvu> wait - why do we ship kall.c in our baseinit?
<ehawkvu> we are missing respawn.c
<ehawkvu> we would likely need these commits?
<phoebos> check the branch
<phoebos> I can't remember why there are 2 branches though
<ehawkvu> interesting
<ehawkvu> should we change the master branch to reflect the current 'master'
<ehawkvu> i don't remember the exact git terminology