<sad_plan>
riteo: i tried to build the oasis part of my system with -pedantic-errors, to see which packages doesnt fully comply with the ISO C standard. out of 102 packaged, around 30 failed. which is better than I anticipated :p
<sad_plan>
phinxy: isnt trim a kernel module thing? in which case youd have to enable it. kiss doesnt blacklist anything, but it does happen thay things are broken on musl and/or busybox
fitrh has joined #kisslinux
fitrh has quit [Quit: fitrh]
fultilt has quit [Quit: Leaving]
<sad_plan>
I would say pdpmake is fairly compatible https://github.com/hovercats/oakiss/issues/3 midfavila sewn. 68/90 so far. only fix that Ive done more or less is fixing the 'missing' file, complaining about about autotool related stuff missing
<sad_plan>
appart from that, it seems to error on either a macro or separator
<sad_plan>
which should be rather simple to fix. I just havent looked too much into it. just wanted to run through them quickly, to figure out what builds ootb or not
zlg has joined #kisslinux
zlg has quit [Ping timeout: 255 seconds]
<sewn>
oakiss
<sad_plan>
yes
<midfavila>
fwah i still haven't gotten gcc to build reliably. there's always something going wrong on the r01...
<midfavila>
real pita
<midfavila>
sad_plan fair
<midfavila>
if i knew more i would pitch in to help with development
<midfavila>
maybe in the future
<sewn>
i wonder why people still use makefiles
<sewn>
its not 1988 anymore and we have flexible systems!
<sad_plan>
midfavila: havd you tried another compiler instead? i was looking at stage0 to bootstrap from a measly 256bit seed. which sounds ridiculus. also, help is always welcome if you ever find the time :p
<sad_plan>
sewn: what do you propose insted? samurai?
<sewn>
muon
<sad_plan>
figured as much :p
<sewn>
samurai is just a more modern implementation of Make
<sewn>
same shit different name basically
<sad_plan>
pretty much
<sewn>
also hey whats wrong with muon
<sewn>
you get really good pkgconf and easy software build systems in c99
<sad_plan>
nothing? i ported it to oasis' buildsystem, and im working on using muon instead of meson
<sewn>
ok yippeee yayy
<sad_plan>
yeah. i got almost all of them done, but still had some issues. im retracing my steps again though, hoping to either avoiding them, or fixing them along the way.
<sewn>
i hope my gnome impl in muon helped a lil bit
<sad_plan>
i seem to recall i had more issues last time, so yeah, I suppose so
<midfavila>
sewn because make is fine
<midfavila>
and it's standard
<midfavila>
if it's standard and it does the job there's no need to rip it out
<midfavila>
there's no real reason to replace make.
<midfavila>
sad_plan i was considering qbe/cproc
<midfavila>
tcc was my standby but it doesn't target riscv afaik
fultilt has joined #kisslinux
<midfavila>
well, not 64 anyway
<midfavila>
the problem is that there's software i need that's written in CXX...
<sad_plan>
i kinda agree. make is the standard, and if I could choose, I choose that ovef everything else most of the time.
<sad_plan>
I see. my only complaint with cproc is the lack of a pre-processor really..
<sad_plan>
so it doesnt work standalone..
<midfavila>
cpp is always separate
<sewn>
midfavila: make's standard is shit
<sewn>
it was designed back then and it reflects that
<midfavila>
sewn, standardisation is what drives progress
<midfavila>
having 20 different "better" build systems doesn't
<sewn>
so you really think most projects use POSIX make
<sewn>
and not something like GNU make or BSD make because regular make is obviously not flexible enough to meet the needs of projects
<sewn>
there is more advanced dependency tracking nowadays, more needs for feature flags and such
<sewn>
you cant do that in Makefile without breaking 'standards'
<midfavila>
i mean my honest contrarian opinion is that most technology is misapplied
<midfavila>
drastically
<midfavila>
whether in the computer industry or outside
<sewn>
also at the same time makefile has no better target tracking than just files
<sewn>
custom targets basically are impossible
<midfavila>
ngl i don't super care.
<sewn>
without just assuming itd be there
<sewn>
midfavila: i mean its sort of evident since you dont deal with software that needs more features and rules than just 'compile this'
<sewn>
make is great but it doesnt work for most
<sewn>
infact i still use make for basically all of my project because it suffices just enough for what i am trying to achieve for that particular project
<sewn>
oh man wayland protocol generation is a pain in the ass, duplicate Make code everywhere because there is no custom targets in Make
<midfavila>
sewn, don't presume things about me. i've written my own projects. i just don't see a need for anything i deal with to use other build systems.
<sewn>
i tried to get around it by utilizing non-standard undefined %, but it didnt work with GNU for some reason
<sewn>
midfavila: yeah youre proving my point lol
<sewn>
its great, just doesnt have the features or needs of modern developers aka "doesnt work for most"
<midfavila>
my opinion is that modern developers are a net negative, my dude
<midfavila>
you should know this by now
<sewn>
its apparent we both have different definitions of what a modern developer is
<midfavila>
i'm just not going to have this conversation :v
<sewn>
yeah its fine its going bumfuck nowhere and its not solving any problems other than "we both have very different views on what software should be"
<sewn>
mfw i have to wait two months before i can get back into kiss because DHL
<sad_plan>
midfavila: wym cpp is always separate? doesnt other compilers come with its own preprocessor? like tcc or scc or others?
<midfavila>
sad_plan: tcc does have an integrated cpp, yeah, but most compilers can just use whatever
<midfavila>
even tcc can use an external cpp
<midfavila>
i guess i could have phrased it better
<midfavila>
they're not joined at the hip
<midfavila>
cpp is one thing, c is another, afaik
<midfavila>
i dunno
<midfavila>
ive been up late for weeks on end now, practically
<midfavila>
i need more tea
<midfavila>
i've had my fill of democracy for the next four years
<midfavila>
xwx
<sad_plan>
thats what I was thinking. do you have a recommendation for a separate cpp btw? i know of a couple, but I have no idea wether theyre any good at all..
<sad_plan>
been following the us election or something? :p
zlg has joined #kisslinux
<thomas_adam>
sad_plan: What is it you’re trying to do?