💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-11-21.txt captured on 2021-12-17 at 13:26:06.
-=-=-=-=-=-=-
2020-11-21T00:42:54 #kisslinux <nerditup> Arch is very much bloated these days
2020-11-21T00:43:03 #kisslinux <nerditup> Everything depends on all the things
2020-11-21T00:44:18 #kisslinux <E5ten> mcpcpc: iirc -W is like an obsolete-ish synonym for -Wextra nowadays
2020-11-21T00:44:41 #kisslinux <E5ten> (probably also wanna have -Wall if you're already using -Wextra, considering it has more useful warnings)
2020-11-21T00:47:17 #kisslinux <mcpcpc[m]> E5ten: hmm ok. i was using this article (https://nullprogram.com/blog/2017/08/20/) for reference, which is from 2017. i should probably find something more recent. lol.
2020-11-21T00:48:15 #kisslinux <E5ten> oh I think the -W being an old synonym for -Wextra is older than 2017, I think they probably just weren't aware
2020-11-21T00:48:56 #kisslinux <E5ten> also -O is -O1, which you probably don't want (imo -O2 or -O3)
2020-11-21T00:49:55 #kisslinux <E5ten> although if it was me I'd probably do like ALL_CFLAGS = -Wall -Wextra $(CPPFLAGS) $(CFLAGS), or whatever warning flags you want, and leave optimization up to what the user wants
2020-11-21T00:50:08 #kisslinux <mcpcpc[m]> would it make sense to just drop the CFLAGS line? same for CC?
2020-11-21T00:50:37 #kisslinux <mcpcpc[m]> ah. ok.
2020-11-21T00:50:44 #kisslinux <E5ten> CC I'd definitely drop, I'd probably do the ALL_CFLAGS thing so you have warnings enabled
2020-11-21T00:51:23 #kisslinux <E5ten> shouldn't do any harm to the user, and they still get the CFLAGS they expect (because they set them)
2020-11-21T00:51:36 #kisslinux <mcpcpc[m]> kk
2020-11-21T00:51:39 #kisslinux <E5ten> and if they really don't want warnings for some reason they can override ALL_CFLAGS
2020-11-21T00:52:30 #kisslinux <E5ten> but I assume whatever changes you'd push would have any warnings they create fixed before you push them, so shouldn't really be any reason for the user to have a problem with them being enabled
2020-11-21T00:54:38 #kisslinux <mcpcpc[m]> alrighty. makes sense.
2020-11-21T00:55:38 #kisslinux <sh4rm4^bnc> <nerditup> Everything depends on all the things
2020-11-21T00:55:44 #kisslinux <sh4rm4^bnc> the result of popularity
2020-11-21T00:56:12 #kisslinux <sh4rm4^bnc> one of out thousand users wants software X with feature Y, so you got to toggle it on for everybody
2020-11-21T01:02:35 #kisslinux <TAAPArthur> It wouldn't be that bad if it was just a toggle. You know something that could easily be toggled off instead of deeply integrated into everything
2020-11-21T01:32:57 #kisslinux <himmalerin> Does anyone have a working build of p7zip handy?
2020-11-21T01:37:31 #kisslinux <himmalerin> I unfortunately need to unzip a .7z archive and can't get p7zip to actually build
2020-11-21T01:43:39 #kisslinux <clauia> himmalerin: There was a working build inside kiss-games, if you are lucky to search the git history.
2020-11-21T02:02:31 #kisslinux <sh4rm4^bnc> himmalerin, http://tar.sabo.xyz/p7zip/p7zip_x86_64_2.tar.gz
2020-11-21T02:02:57 #kisslinux <sh4rm4^bnc> built on sabotage, but should be compatible to kiss
2020-11-21T02:26:01 #kisslinux <himmalerin> clauia: Same error as before, unfortunately. Throwing the log out here in case anyone has a moment: http://0x0.st/i5FQ.txt
2020-11-21T02:26:37 #kisslinux <himmalerin> sh4rm4^bnc: It's looking for a file in someone's home dir? `./bin/7z: line 2: /home/rofl/x-prefix/x86_64/opt/p7zip/lib/p7zip/7z: not found`
2020-11-21T02:27:59 #kisslinux <sh4rm4^bnc> hurr, why do they hardcode absolute paths in build
2020-11-21T02:28:11 #kisslinux <sh4rm4^bnc> well i guess thats a shellscript and you can just fix the path
2020-11-21T02:28:49 #kisslinux <sh4rm4^bnc> just point it to the lib dir in the extracted dir structure
2020-11-21T02:37:22 #kisslinux <himmalerin> Oh, so it is, the file in the lib dir works fine after chmod'ing it. Works fine for my quick needs, thank you!
2020-11-21T02:37:58 #kisslinux <sh4rm4^bnc> yw
2020-11-21T04:36:52 #kisslinux <sgnix> Hi. What's the recommendation for init? I installed runit and it has no initializations. Same for baseinit.
2020-11-21T04:37:21 #kisslinux <midfavila> the standard init in KISS is busybox-init
2020-11-21T04:37:25 #kisslinux <midfavila> which functions similarly to sysvinit
2020-11-21T04:38:14 #kisslinux <sgnix> ok, I'll give it a try. thanks!
2020-11-21T05:29:46 #kisslinux <dylanaraps> https://lists.webkit.org/pipermail/webkit-dev/2020-November/031604.html
2020-11-21T05:30:15 #kisslinux <dylanaraps> > Google will attempt to block logins from "CEF-based apps and
2020-11-21T05:30:25 #kisslinux <dylanaraps> > other non-supported browsers." Presumably "non-supported browsers"
2020-11-21T05:30:31 #kisslinux <dylanaraps> > likely includes non-Safari WebKit,
2020-11-21T05:30:34 #kisslinux <dylanaraps> > ...
2020-11-21T05:31:50 #kisslinux <dylanaraps> Basically, from Jan 4 2021 Google /may/ start blocking all cef, webkit, etc browsers.
2020-11-21T05:32:07 #kisslinux <dylanaraps> This may also include qt-webengine though I'm not sure.
2020-11-21T05:33:22 #kisslinux <sginx> Noob question: I boot with busybox-init, but the default configuration provides no initialization of modules, etc. What is the recommendation do use for this?
2020-11-21T05:37:13 #kisslinux <dylanaraps> See: https://k1ss.org/wiki/init/busybox
2020-11-21T05:38:01 #kisslinux <sginx> thanks
2020-11-21T11:05:03 #kisslinux <claudia02> himmalerin: mind to share your p7zip fix?
2020-11-21T11:27:26 #kisslinux <testuser[m]> You just need to use the `7z` binary from `p7zip/lib/p7zip/7z`
2020-11-21T11:27:33 #kisslinux <testuser[m]> claudia02:
2020-11-21T12:00:06 #kisslinux <claudia02> testuser[m] : This is my build failing https://0x0.st/iRsi.txt . But I cant really tell whats error message .
2020-11-21T12:03:20 #kisslinux <testuser[m]> Weren't you asking about using 7z from the tarball send above?
2020-11-21T12:03:39 #kisslinux <claudia02> naah :)
2020-11-21T12:03:43 #kisslinux <testuser[m]> I think i got p7zip to build a few weeks back, will let you know in some time
2020-11-21T12:03:54 #kisslinux <claudia02> build it myself.
2020-11-21T12:04:10 #kisslinux <claudia02> ah
2020-11-21T12:04:23 #kisslinux <claudia02> The fix was to use the tarball..^^
2020-11-21T12:05:24 #kisslinux <claudia02> ++
2020-11-21T12:06:50 #kisslinux <claudia02> gtg, be on later.
2020-11-21T12:34:06 #kisslinux <testuser[m]> Just need this patch https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/p7zip/trunk/gcc10-conversion.patch
2020-11-21T14:43:57 #kisslinux <claudia02> many thx tesuser[m] . I was blind to it.
2020-11-21T14:44:02 #kisslinux <claudia02> *testuser[m]
2020-11-21T14:44:41 #kisslinux <claudia02> himmalerin: reuploaded a working package to kiss-games
2020-11-21T16:30:48 #kisslinux <testuser[m]> claudia02 There were a few CVE patches too, i think you should include those
2020-11-21T16:45:14 #kisslinux <claudia02> Has somebody recently build fzf? The build is failing on my end because the install option about the manpage does not work.
2020-11-21T16:45:35 #kisslinux <claudia02> When I change directly in the directory the insall command works as expected. Strange
2020-11-21T16:46:00 #kisslinux <claudia02> *install
2020-11-21T17:08:52 #kisslinux <aarng> building a newer kernel and I just checked the kiss wiki
2020-11-21T17:09:01 #kisslinux <aarng> > The following options are mandatory (when using busybox) (=n). CONFIG_IKHEADERS
2020-11-21T17:09:46 #kisslinux <aarng> totally unclear what that means. Should that option be enabled or not?
2020-11-21T17:10:52 #kisslinux <testuser[m]> claudia02 fzf from community builds fine for me
2020-11-21T17:11:47 #kisslinux <aarng> ok, for the in kernel config it says "The following options are recommended (=y)."
2020-11-21T17:11:54 #kisslinux <aarng> So I assume CONFIG_IKHEADERS has to be =n
2020-11-21T17:12:43 #kisslinux <testuser[m]> aarng You need to turn off that option cuz it probably uses some command with extra flags which busybox doesn't have
2020-11-21T17:12:52 #kisslinux <testuser[m]> * aarng You need to turn off that option cuz it probably uses some command with extra flags which busybox doesn't have in it's utilities
2020-11-21T17:13:09 #kisslinux <aarng> yeah, makes sense
2020-11-21T17:13:24 #kisslinux <aarng> was off by default in 5.9 anyway
2020-11-21T17:34:58 #kisslinux <claudia02> re fzf fails: It seems while building the install command is not calling /usr/bin/install but something from go? -> fzf Build failed
2020-11-21T17:35:33 #kisslinux <claudia02> *oops
2020-11-21T17:35:35 #kisslinux <claudia02> http://ix.io/2EYC
2020-11-21T17:35:55 #kisslinux <claudia02> When it replace install with '/usr/bin/install' it works
2020-11-21T17:43:30 #kisslinux <testuser[m]> Maybe something in your `PATH` is interfering?
2020-11-21T17:48:39 #kisslinux <claudia02> Hm, it seems like something like that. I have tested other gopackages which work fine, and also packages which call "install -DmXXX" .
2020-11-21T17:49:03 #kisslinux <claudia02> Its not that important though..
2020-11-21T17:56:55 #kisslinux <sh4rm4^bnc> claudia02, what's the issue with gcc10 in p7zip ?
2020-11-21T18:25:49 #kisslinux <mcpcpc[m]> E5ten: to enforce c99 compliance, would it make sense to specify CC=c99? i understand this is “standard” when specifying the POSIX target. just thinking of “edge” cases... https://clbin.com/CtgP2
2020-11-21T18:36:28 #kisslinux <claudia02> sh4rm4^bnc: The isse was https://0x0.st/iRsi.txt . This patch fixed it. https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/p7zip/trunk/gcc10-conversion.patch
2020-11-21T18:52:05 #kisslinux <sh4rm4^bnc> ../../../../CPP/Common/MyWindows.h:83:40: error: narrowing conversion of '-2147467263' from 'LONG' {aka 'int'} to 'unsigned int' [-Wnarrowing]
2020-11-21T18:52:05 #kisslinux <sh4rm4^bnc> 83 | #define E_NOTIMPL ((HRESULT)0x80004001L)
2020-11-21T18:52:05 #kisslinux <sh4rm4^bnc> | ^
2020-11-21T18:52:05 #kisslinux <sh4rm4^bnc> ../../../../CPP/Windows/ErrorMsg.cpp:18:10: note: in expansion of macro 'E_NOTIMPL'
2020-11-21T18:52:06 #kisslinux <sh4rm4^bnc> 18 | case E_NOTIMPL : txt = "E_NOTIMPL"; break ;
2020-11-21T18:52:21 #kisslinux <sh4rm4^bnc> oh, i guess then the right fix would be to remove the L suffix from the constant
2020-11-21T18:53:27 #kisslinux * sh4rm4^bnc wonders whether using -std=c++03 would fix it
2020-11-21T20:25:50 #kisslinux <E5ten> mcpcpc: if you wanna do that just use -std=c99 in ALL_CFLAGS
2020-11-21T20:31:03 #kisslinux <mcpcpc[m]> E5ten: but that’s implicit by `.POSIX:`special target, right?
2020-11-21T20:33:23 #kisslinux <E5ten> you mean -std=c99 or CC = c99? either way, I don't think either are necessarily specified to be true when .POSIX: is used, definitely not -std=c99
2020-11-21T20:33:40 #kisslinux <E5ten> imo just don't touch CC, and use -std=c99 in ALL_CFLAGS (before the user's CPPFLAGS and CFLAGS)
2020-11-21T20:38:31 #kisslinux <mcpcpc[m]> i thought CC=c99 was the same thing as adding -std=c99? also, CC=c99 seems to be the default for a POSIX compliant makefile (https://pubs.opengroup.org/onlinepubs/009695299/utilities/make.html).
2020-11-21T20:39:50 #kisslinux <mcpcpc[m]> i guess i am confused whether specifying “POSIX” as the special target changes CC
2020-11-21T20:39:57 #kisslinux <E5ten> I don't think so
2020-11-21T20:40:17 #kisslinux <E5ten> at least, it doesn't in practice
2020-11-21T20:41:03 #kisslinux <E5ten> and CC=c99 is the same as -std=c99, but what if c99 is like a script that calls gcc but the user also has clang or something, and that's what they have CC set to?
2020-11-21T20:41:22 #kisslinux <E5ten> just causes less problems to use -std=c99 directly imo
2020-11-21T20:42:54 #kisslinux <mcpcpc[m]> i think that makes sense. not sure why makefiles confuse me. lol. guess i need to mess around a bit more.
2020-11-21T20:43:04 #kisslinux <E5ten> Understandable lol
2020-11-21T22:39:16 #kisslinux <E5ten> dylanaraps: for the kill issue, would saving $ in the main she'll to a variable and using that variable with kill in the subshell work?