#archlinux32 | Logs for 2018-12-28
Back
[00:33:27] -!- ofara_ has joined #archlinux32
[01:21:14] -!- ztrawhcse has quit [Ping timeout: 250 seconds]
[01:34:17] -!- ztrawhcse has joined #archlinux32
[03:22:54] -!- ztrawhcse has quit [Ping timeout: 246 seconds]
[03:37:38] -!- ztrawhcse has joined #archlinux32
[05:10:58] -!- NoobAlice has quit [Quit: Leaving.]
[05:24:07] -!- ztrawhcse has quit [Ping timeout: 240 seconds]
[05:38:26] -!- ztrawhcse has joined #archlinux32
[07:25:15] -!- ztrawhcse has quit [Ping timeout: 250 seconds]
[07:39:17] -!- ztrawhcse has joined #archlinux32
[07:47:15] -!- DCyrax has joined #archlinux32
[08:34:42] -!- miique has joined #archlinux32
[09:25:53] -!- ztrawhcse has quit [Ping timeout: 245 seconds]
[09:41:04] -!- ztrawhcse has joined #archlinux32
[09:52:55] -!- woshty has joined #archlinux32
[11:17:16] -!- miique has quit [Ping timeout: 252 seconds]
[11:17:33] -!- woshty has quit [Ping timeout: 245 seconds]
[11:27:20] -!- ztrawhcse has quit [Ping timeout: 272 seconds]
[11:41:27] -!- ztrawhcse has joined #archlinux32
[13:27:08] -!- ztrawhcse has quit [Ping timeout: 245 seconds]
[13:42:00] -!- ztrawhcse has joined #archlinux32
[15:14:19] -!- NoobAlice has joined #archlinux32
[15:28:53] -!- ztrawhcse has quit [Ping timeout: 250 seconds]
[15:32:44] -!- girls has quit [Ping timeout: 250 seconds]
[15:34:02] -!- tyzoid has quit [Ping timeout: 250 seconds]
[15:39:29] -!- tyzoid has joined #archlinux32
[15:39:30] <buildmaster> Hi tyzoid!
[15:39:30] <buildmaster> !rq tyzoid
[15:39:30] <phrik> buildmaster: <tyzoid> mpan: I'm bad at trolling because I'm not trolling.
[15:43:33] -!- ztrawhcse has joined #archlinux32
[16:34:44] -!- MrBIOS has joined #archlinux32
[17:29:21] -!- ztrawhcse has quit [Ping timeout: 250 seconds]
[17:41:38] <buildmaster> i686/electron is broken (says nlopc46) - as usual.
[17:44:09] -!- ztrawhcse has joined #archlinux32
[18:03:17] <buildmaster> i686/electron2 is broken (says nlopc46) - as usual.
[18:12:31] -!- girls has joined #archlinux32
[18:12:32] <buildmaster> Hi girls!
[18:12:32] <buildmaster> !rq girls
[18:12:32] <phrik> buildmaster: <girls> I'm married, I don't cook
[18:13:07] <girls> elibrokeit: at least, I repaired that error message ^
[18:13:19] <elibrokeit> \o/
[18:13:30] <elibrokeit> Baby steps1
[18:25:58] <girls> there is a residual anki in community-x86_64, can you please clean that up, elibrokeit ?
[18:26:16] <buildmaster> i686/deepin-control-center is broken (says nlopc46).
[18:30:37] <buildmaster> i686/startdde is broken (says nlopc46).
[18:31:04] <elibrokeit> done
[18:31:09] <girls> thanks :-)
[18:32:31] <thePiGrepper> hi, anyone can help me with this? Im trying to build systemd with tcc instead of gcc. anyone with meson experience?
[18:34:15] <girls> thePiGrepper: maybe ask in #systemd?
[18:34:26] <girls> or is that channel only for systemd users?
[18:35:44] <thePiGrepper> well, what I *actually* want to do is build systemd with musl... so I dont think they will be eager to help
[18:37:29] <elibrokeit> why would they be hateful about it?
[18:37:54] <girls> well, it's worth a trial
[18:38:16] <elibrokeit> wait hmm
[18:39:13] <thePiGrepper> elibrokeit: apparently there's some history regarding that. musl ppl(or somebody else who tried) had PRs on systemd I believe to allow it to compiled against musl, but they were rejected uptream
[18:39:28] <thePiGrepper> I think that happen a few years ago, so I dont really know the current state
[18:39:38] <thePiGrepper> *happened
[18:39:39] <rcf> I highly doubt they'd have changed their minds on that.
[18:40:00] <girls> isn't it a sign of quality, that one can link against different libraries?
[18:40:17] <thePiGrepper> girls: I'd think that as well..
[18:42:33] <rcf> Not necessarily. If they want explicitly glibc-specific functionality, they'd have to add in portability code that they themselves would never use.
[18:44:45] <elibrokeit> https://lists.freedesktop.org
[18:44:46] <phrik> Title: [systemd-devel] [RFC 00/25] Compile against the musl libc (at lists.freedesktop.org)
[18:44:53] <elibrokeit> a bunch of these patches were accepted
[18:45:31] <elibrokeit> then there was https://lists.freedesktop.org
[18:45:32] <phrik> Title: [systemd-devel] [RFC 00/25] Compile against the musl libc (at lists.freedesktop.org)
[18:45:53] -!- woshty has joined #archlinux32
[18:48:23] <elibrokeit> prognosis looks something like: they're not against musl per se, because why not be more standards-compliant when it's The Right Thing™, but some glibc extensions are simply too useful and they'd rather not reimplement everything
[18:48:33] <elibrokeit> so I dunno
[18:49:03] <elibrokeit> I mean, that being said I like musl for static compilation
[18:49:32] <elibrokeit> but I wouldn't have any personal interest in using it as the default libc
[18:50:42] <elibrokeit> muh disappoint, new pacman release from 3 days ago and Arch is not updating yet.
[18:54:00] <thePiGrepper> elibrokeit: Im interested in your opinion, do you think musl doesnt have any benefit performance-wise or maybe using less resources?
[18:56:01] <elibrokeit> Well, its development model is that when speed and minimalism comes into conflict with rich functionality, just opt for supporting POSIX and strip down the rest.
[18:56:48] <elibrokeit> It's the same reason I use GNU coreutils or bash instead of SUSv4 utils and busybox ash as my interactive terminal
[18:57:26] <elibrokeit> glibc is an extremely reasonable libc if you're not in the embedded market, and I'm not in the embedded market.
[19:00:43] <elibrokeit> unfortunately glibc is completely unacceptable at statically compiling anything.
[19:18:53] <thePiGrepper> I see, so you really dont see a benefit in performance or resource when it comes to musl vs glibc. I ask this, because all the info I have regarding that is one damn table in the musl website, which obviously isnt enough to get a clear idea
[19:19:15] <buildmaster> i686/haskell-yesod-static is broken (says nlopc46) - I rescheduled: haskell-yesod-test.
[19:29:26] <elibrokeit> thePiGrepper: the chart points out things like the time to self-exec dynamically being, for glibc, 864µs and for musl, 446µs
[19:29:36] <elibrokeit> I'm 100% sure this is truthful
[19:30:04] -!- ztrawhcse has quit [Ping timeout: 246 seconds]
[19:30:28] <elibrokeit> supporting the kitchen sink is just more valuable for the average use case, assuming you're not running a specifically resource-constrained system.
[19:31:15] <thePiGrepper> apparently, according to musl devs in the musl channel, there are patched for this used by yocto..
[19:31:33] <thePiGrepper> *patches
[19:32:26] <elibrokeit> I'm completely not surprised, I'd assume at least someone would build it with musl anyway.
[19:44:32] -!- ztrawhcse has joined #archlinux32
[20:13:25] -!- woshty has quit [Ping timeout: 268 seconds]
[21:30:28] -!- ztrawhcse has quit [Ping timeout: 245 seconds]
[21:43:17] -!- ztrawhcse has joined #archlinux32
[22:14:06] -!- woshty has joined #archlinux32
[22:40:00] <buildmaster> i686/vivid is broken (says nlopc46).
[22:58:47] -!- alexandre9099 has quit [Quit: ZNC 1.7.1 - https://znc.in]
[23:00:00] -!- alexandre9099 has joined #archlinux32
[23:20:52] -!- MrBIOS has quit [Quit: MrBIOS]
[23:30:53] -!- ztrawhcse has quit [Ping timeout: 245 seconds]
[23:45:18] -!- DepositePirate has quit [Remote host closed the connection]
[23:45:56] -!- DepositePirate has joined #archlinux32
[23:46:07] -!- ztrawhcse has joined #archlinux32
[23:49:13] -!- woshty has quit [Ping timeout: 245 seconds]