soliwilos_ has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
<testuser[m]12>
Hi
<ioraff>
hi
<virutalmachineus>
hi
soliwilos has quit [Remote host closed the connection]
soliwilos_ has joined #kisslinux
soliwilos has joined #kisslinux
soliwilos_ has quit [Remote host closed the connection]
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
soliwilos_ has joined #kisslinux
soliwilos has quit [Ping timeout: 258 seconds]
ehawkvu` has quit [Remote host closed the connection]
soliwilos_ has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
<wael[m]>
hi
dotkwa[m] has quit [Quit: You have been kicked for being idle]
<testuser[m]12>
ioraff: are u ok with adding pipewire as a mandatory build (not runtime, dlopen'd) dependency for chromium? it can probably save a few hrs if someone decided that they need screen sharing
<testuser[m]12>
ofc they'd need dbus and stuff too
ioraff has quit [Ping timeout: 252 seconds]
chomwitt has joined #kisslinux
cennedy has joined #kisslinux
cennedy has quit [Client Quit]
cennedy has joined #kisslinux
phinxy has quit [Quit: WeeChat 3.5-dev]
cennedy has quit [Ping timeout: 252 seconds]
cennedy has joined #kisslinux
cennedy has quit [Quit: Ping timeout (120 seconds)]
<wael[m]>
cant pipewire be built without dbus
<testuser[m]12>
i meant screen casting
<wael[m]>
so screen casting needs dbus 100%
<testuser[m]12>
yeah cuz browsers communicate to abstraction layer over ayyland compositor's cast implementation which also communicates via dbus, via dbus
<testuser[m]12>
u can write another webrtc backend that skips all this abstraction
<wael[m]>
its sad to see that dbus is needed
<wael[m]>
i hope there is a backend yea
<testuser[m]12>
it's not gonna appear by itself lol
<testuser[m]12>
alternatively u can cast to v4l2 camera via wf-recorder and use that as a webcam in firefox
<testuser[m]12>
and do whatever config to pass speaker to mic device
<testuser[m]12>
but then obv u cant use either of those with real defices
<wael[m]>
software is magic it'll appear and save ur life
<macslash1[m]>
hey uh is there any way to test if my pc could realistically compile a kernel, I want my own custom kernel for KISS but I really don't know if my system could compile it
<raph_ael>
macslash1[m]: i compiled my kernels back in 2001, the thing is time
<macslash1[m]>
Yeah true
<macslash1[m]>
also just remembered I'm gonna have to use GKISS for this too
ioraff has joined #kisslinux
<ioraff>
testuser[m]12: hm. not sure
<wael[m]>
@raph_ael poor guy's 4g ram laptop couldn't compile it in a chroot
<wael[m]>
probably because of systemd oomd moment
<raph_ael>
oh
<raph_ael>
some dev should get rpi to dev and taste most people real life computing feeling
<ioraff>
testuser[m]12: I'm holding off on llvm 15 as rust can't build against it yet
<macslash1[m]>
wael: well I'm compiling on a 16gig ram pc now
<macslash1[m]>
quadcore AMD smth CPU I forget
<testuser[m]12>
ioraff: ok
<testuser[m]12>
a new rust release should be coming in few days anyway so no point in bumping old ver
<macslash1[m]>
rust linux my beloved
<ioraff>
1.64 is due on 9/22. maybe there'll be a 1.63.1
an3223 has quit [Ping timeout: 258 seconds]
an3223 has joined #kisslinux
an3223 has quit [Remote host closed the connection]
an3223 has joined #kisslinux
an3223 has quit [Remote host closed the connection]
<macslash1[m]>
Hello, so I'm trying to update glibc 2.36-1 => 2.36-3 and whenever I do it always gets stuck at a line with the error (.text+0xe5e9): undefined reference to `strcpy'
<macslash1[m]>
this is the whole log file
<testuser[m]12>
macslash1: cflags?
<testuser[m]12>
env
<macslash1[m]>
okay weirdly whenever I try `echo $CFLAGS` it doesn't output anything I'll try fix it and retry
<testuser[m]12>
maybe u didn't set any then
<testuser[m]12>
It should work fine
<testuser[m]12>
Hmm
phinxy has joined #kisslinux
<macslash1[m]>
I added it maybe it'll work now
<wael[m]>
what CFLAGS did you set?
<macslash1[m]>
should be okay on 16 gigs
<macslash1[m]>
-O3 -pipe -march=native
<wael[m]>
yep
<testuser[m]12>
macslash1: can u tell the exact steps u used before rebuilding glibc
<macslash1[m]>
that's probably why it was so damn slow it was all on one core before
<testuser[m]12>
you need to set MAKEFLAGS=-j$(nproc) for slowness
<macslash1[m]>
yeah ik I set it to 8 threads
<macslash1[m]>
8 is output by nproc so
<macslash1[m]>
testuser[m]12: I just exported CFLAGS, CXXFLAGS, and MAKEFLAGS
<macslash1[m]>
CFLAGS with `export CFLAGS="-O3 -pipe -march=native",
<macslash1[m]>
`export CXXFLAGS=$CFLAGS` and
<macslash1[m]>
`export MAKEFLAGS="-j8"
<macslash1[m]>
arg weird codeblocks
<macslash1[m]>
> <@testuser:matrix.pratham.cc> macslash1: can u tell the exact steps u used before rebuilding glibc
<macslash1[m]>
* I just exported CFLAGS, CXXFLAGS, and MAKEFLAGS
<macslash1[m]>
CFLAGS with `export CFLAGS="-O3 -pipe -march=native"`, `export CXXFLAGS=$CFLAGS`and`export MAKEFLAGS="-j8"`
<macslash1[m]>
it's working now anyway
<macslash1[m]>
ty btw
<macslash1[m]>
* ty
<midfavila>
fwiw you should avoid O3
<midfavila>
O2 is enough
<midfavila>
O3 can cause subtle errors because it enables unsafe optimizations
<macslash1[m]>
sorry forgot this was an IRC with the reply lmao
<macslash1[m]>
I see, I'll probably change it then
<midfavila>
probably a good idea
<midfavila>
O3 can also cause binaries to actually be larger and slower
<midfavila>
it enables a lot of weird tricks
<midfavila>
if you want to fiddle with CFLAGS, it's best to read the GCC manual and look at what Red Hat and Debian set
<macslash1[m]>
really?
<midfavila>
yes
<macslash1[m]>
did not know that ty
<midfavila>
O2 with a handful of hardening options is really all you need tbqh
<midfavila>
alternatively if you were a based cool kid like me you would just use a non-optimizing compiler
<macslash1[m]>
partition and HDD, I also need to get an SSD at some point
<midfavila>
did you make sure your swap partition was the first one?
<macslash1[m]>
lol
<midfavila>
it's important = w=
<macslash1[m]>
Uh im not sure, cant fix it rn im about to eat
<midfavila>
np
<midfavila>
anyway yeah for future reference: keep in mind that the lower a track is, the higher its angular velocity and the lower the latency to seek is
<midfavila>
so by placing your swap partition at the start of your partition table, you minimize the time necessary to complete a full rotation of the track(s) it's on
<midfavila>
thereby increasing performance when swapping
<midfavila>
(you might have already known that though idk)
<macslash1[m]>
6.0 is shaping up to a quite nice kernel update
<midfavila>
doesn't it have rust?
<macslash1[m]>
yes.
<midfavila>
i'm sticking with 5.10 = w=
<midfavila>
hBSD can't come soon enough
<macslash1[m]>
:)
<ioraff>
I don't think that patchset was merged yet
<testuser[m]12>
midfavila: h what
<midfavila>
HyperbolaBSD
<macslash1[m]>
I wonder how many will actually move to BSD because of rust in the linux kernel
<midfavila>
probably not many
<ioraff>
probably 0
<testuser[m]12>
0 unless it's hard dep for common modules
<macslash1[m]>
Personally I don't see an issue in it and a version of the gnu coreutils has been created in rust and it's actually faster than the current implementation
<testuser[m]12>
Few decades left for that
<midfavila>
that's irrelevant, macslash1[m]
<macslash1[m]>
idk but I've seen some people who really hate rust and I can't understand it
<midfavila>
rust is a poorly-defined and non-portable language with licensing flaws and really shitty build UX
<midfavila>
do they even have a spec yet?
<midfavila>
or is it still "the compiler is the spec"?
<midfavila>
is the opinion on PPC still "get fucked nerds"?
<midfavila>
do you still need to either rely on binaries or bootstrap literally years' worth of compilers?
<midfavila>
etc
<midfavila>
these are all massive issues
<testuser[m]12>
Firefox constantly needs small patches for rust breakage every 2 major releases
<midfavila>
and all for what - so people can think a little less when writing programs?
<macslash1[m]>
midfavila: huh.
<midfavila>
like don't get me wrong, C is a pain in the ass
<midfavila>
the syntax is obtuse compared to Scheme
<midfavila>
and all the bullshit people do with pointers and casting is sinful
<macslash1[m]>
Scheme?
<midfavila>
minimalist Lisp implementation
<midfavila>
very portable, very efficient, very easy to understand, and very easy to use
<midfavila>
but, it also doesn't really have a standard library
<midfavila>
(they're working on that though)
<macslash1[m]>
sounds cool
<midfavila>
it's very cool
<macslash1[m]>
ohhh the (((((((()))))))))
<midfavila>
although some of the stuff you can do with it is a little mind-bending at first
<macslash1[m]>
I forgot about that
<midfavila>
and yes, it uses parentheses for its primary punctuation
<macslash1[m]>
lol, a little too much if you ask me
<midfavila>
compared to <>{}[]();+-=/*==|&~||&&! and so on and so forth?
<macslash1[m]>
oh yeah shellscript is weird like that I don't know too much about it
<midfavila>
C has a bunch of grammatical rules to memorize that can act in unusal ways and the language itself for better or worse forces you to think about implementation more than the program itself
<midfavila>
shell, I don't even care about
<midfavila>
i use rc
<midfavila>
but, point is,
<midfavila>
replacing C with "C but handholding" doesn't really improve the situation much
<midfavila>
and by adding a bunch of caveats to rust,
<midfavila>
it's overall a much worse situation
<midfavila>
like,
<midfavila>
i could write in rust,
<midfavila>
or i could write a program in scheme and transpile it to C and know that it'll be as fast or faster than rust, yet have all the niceties of scheme
<midfavila>
or, if I needed something that would absolutely *not* fuck up *ever*, I could use haskell, or if I was concerned about space, FORTH... there are a bunch of languages that do what rust is trying to do but better
<midfavila>
and they also don't have shitty communities
<midfavila>
and they're also, you know, portable to more than x86, x86-64 and ARM
<ioraff>
testuser[m]12: instead of shipping a pc file with llvm, should we instead try to add llvm-config support to muon?
<ioraff>
tt
ioraff has quit [Ping timeout: 268 seconds]
an3223 has quit [Remote host closed the connection]
an3223 has joined #kisslinux
an3223 has quit [Remote host closed the connection]
an3223 has joined #kisslinux
akspecs_ has quit [Remote host closed the connection]
akspecs has joined #kisslinux
an3223 has quit [Remote host closed the connection]
an3223 has joined #kisslinux
ioraff has joined #kisslinux
midfavila has quit [Remote host closed the connection]
midfavila has joined #kisslinux
soliwilos_ has joined #kisslinux
an3223 has quit [Ping timeout: 258 seconds]
soliwilos has quit [Ping timeout: 258 seconds]
an3223 has joined #kisslinux
geekthattweaks has quit [Quit: Updating details, brb]
geekthattweaks has joined #kisslinux
soliwilos_ has quit [Remote host closed the connection]
an3223 has quit [Remote host closed the connection]
an3223 has joined #kisslinux
soliwilos has joined #kisslinux
geekthattweaks has quit []
midfavila has quit [Quit: Leaving.]
soliwilos has quit [Remote host closed the connection]