#
…

2025-11-06

00:04zumi_ has joined #asahi-alt
00:08zumi has quit [Ping timeout: 480 seconds]
00:09zumi_ is now known as zumi
00:25mixi has quit [Ping timeout: 480 seconds]
00:35mixi has joined #asahi-alt
01:30n3ph has quit [Ping timeout: 480 seconds]
02:29hightower3 has joined #asahi-alt
02:35hightower4 has quit [Ping timeout: 480 seconds]
03:10hightower2 has joined #asahi-alt
03:13hightower3 has quit [Ping timeout: 480 seconds]
03:15Calandracas_ has quit [Ping timeout: 480 seconds]
03:16DannyBee has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
03:17tobhe has joined #asahi-alt
03:20DannyB has joined #asahi-alt
03:21Calandracas has joined #asahi-alt
03:23tobhe_ has quit [Ping timeout: 480 seconds]
06:33chadmed has quit [Read error: Connection reset by peer]
06:33chadmed has joined #asahi-alt
06:37chadmed has quit [Read error: Connection reset by peer]
06:37chadmed has joined #asahi-alt
06:44seb__ has quit [Quit: Konversation terminated!]
06:49sam_ has quit [Remote host closed the connection]
06:53sam_ has joined #asahi-alt
07:48Retr0id3 has joined #asahi-alt
07:48Retr0id has quit [Read error: Connection reset by peer]
07:48Retr0id3 is now known as Retr0id
07:56seb__ has joined #asahi-alt
08:15vimproved has quit [Ping timeout: 480 seconds]
08:17john-cabaj has joined #asahi-alt
08:19vimproved has joined #asahi-alt
08:19seb__ has quit [Quit: Konversation terminated!]
09:27seb__ has joined #asahi-alt
09:33seb__ has quit [Quit: Konversation terminated!]
09:35seb_ has joined #asahi-alt
10:08n3ph has joined #asahi-alt
10:16n3ph has quit [Ping timeout: 480 seconds]
10:52CookieCutter has joined #asahi-alt
11:01n3ph has joined #asahi-alt
11:20CookieCutter has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
11:34john-cabaj has quit [Ping timeout: 480 seconds]
11:42CookieCutter has joined #asahi-alt
12:06john-cabaj has joined #asahi-alt
12:07john-cabaj has quit []
12:07john-cabaj has joined #asahi-alt
12:27john-cabaj has quit [Ping timeout: 480 seconds]
12:52CookieCutter has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
12:54hightower3 has joined #asahi-alt
12:56n3phEmerging kernel and FEX at the same time in parallel fills up an 8gb tmpfs on /var/tmp/portage..
12:57hightower4 has joined #asahi-alt
13:00chaos_princess/var/tmp is not supposed to be a tmpfs
13:01hightower2 has quit [Ping timeout: 480 seconds]
13:01chadmedand like, yeah it would. fex is quite a large cpp project and an ~allmodconfig kernel is huge too
13:02chaos_princessin case of fex it is that it brings an entire x86 rootfs with it
13:02n3phchaos_princess: I haven't said I have a tmpfs on /var/tmp
13:02n3phI have one on /var/tmp/portage
13:02chaos_princesswell, it shouldn't be a tmpfs either
13:02n3phchaos_princess: yes, saw it in the ebuild
13:03chadmed\/var/tmp/portage being a tmpfs is not an uncommon setup
13:03chadmedespecially when people like to use cheap ssds :p
13:04n3phAnd there is also the approach of `PORTAGE_TMPDIR="/var/tmp/notmpfs"` additionally
13:04chadmedi still think this is a common sense situation. like what do you do with firefox et al that need like 12-16gb on /var/tmp/portage
13:04chaos_princessi do have checkreqs in fex to maybe prevent it
13:04hightower3 has quit [Ping timeout: 480 seconds]
13:06n3phchaos_princess: the thing is, I don't think that will help if you run emerge in parallel mode (e.g. EMERGE_DEFAULT_OPTS="--jobs 3")
13:06chaos_princessfair. but that is a generic-gentoo issue
13:06n3phnevertheless, my intention was more like a heads-up
13:07* leiojust has PORTAGE_TMPDIR="/tmp" instead
13:09* chadmedhas Data Units Written: 66,962,638 [34.2 TB]
13:09n3ph🙀13~
13:09chadmedwe go through macs like copy paper
13:10chaos_princessoops Data Units Written: 132,622,691 [67.9 TB]
13:11n3phI would assume, this isn't very much healthy for the SSD - But I really don't know about lifetime expectations TBH
13:11chadmedassuming the smart data is correct ive only allocated 1% of the available spare capacity so
13:11n3phOh interesting, how much spare does your ssd have?
13:11chadmedthe nvme drives in our prod server at work have less than 10% of the TBW, are a third of the age, and have already exhausted almost half of their spare capacity
13:11chadmedjust... dont use shit drives
13:12chadmedidk how much the macs actually provision, they only report the percentages
13:12n3phok, I have trust issues
13:13chadmedbut ive got 40ish TBW on my studio and 30 or so on the mini
13:13chaos_princesshigh quality dc ssds can be fully overwritten 10-ish times every day for 5 years or so
13:13chaos_princessso, it is fine
13:13chadmedthe fear comes from sandforce era drives when MLC NAND was new
13:14chadmedand of course all the modern cheapo nvme drives that drive the nand super hard
13:14n3phBut what about bandwidth? compiling from tmpfs should be much faster for sure..
13:14chadmedjust buy decent drives and theyll last longer than any spinning rust
13:14chaos_princessor the stupid sd cards, which ime rarely survive 2 overwrites
13:14chaos_princessn3ph: page cache exists
13:15n3phtrue that
13:15chadmedand the drives are fast enough that it really doesnt matter that much
13:15chadmedi dont think my m2 air is gonna build llvm any faster regardless of io bandwidth
13:16n3phyeah, I am using tmpfs on /var/tmp/portgae for almost more than 15 years now, so it's more like a habbit - maybe something to chnage
13:16chadmedsd cards are for digital cameras and letterbombing wiis
13:20n3phOther topic, yesterday I was about to quickly compile some rust code and got "feature `edition2024` is required"
13:20n3phI do understand that most people use rustup and have there home installation added with precedence in their PATH.
13:20n3phBut I am wondering why this feature flag isn't enabled in the systems toolchain.
13:21n3phs/there/their/'
13:22n3phTBH, I would always prefer to use the systems toolchain instead of having a dedicated one for my user..
13:23chaos_princessi don't think that is how editions work, mind showing the full error
13:23chadmedi only let rustup take over when i need a special sauce toolchain (basically just m1n1) so theres probably something else going on
13:24n3phThat's `cargo build --release`
13:24chaos_princessi have cargo 1.91.0 as system toolchain
13:24n3phme too
13:24chadmedwell its pulling 1.81 from your PATH somewhere
13:25n3phah, 🤔 that was yesterday
13:26chadmedplease make sure your depcleaning after updates and such, there should be absolutely nothing still depending on 1.81
13:26chadmed1.89 is in stable
13:26chadmeds/your/youre
13:27chaos_princessyea, system cargo is not complaining about that on that project here
13:28n3phNVM, I _had_ a local rust toolchain in my PATH
13:28n3ph:facepalm:
13:29n3phYes, systems toolchain does have this feature enabled and `cargo build --release` executes successfully.
13:50minecrell has quit [Quit: Ping timeout (120 seconds)]
13:51minecrell has joined #asahi-alt
13:55LarstiQI have a x86_64 application that with qemu binfmt fails with `error while loading shared libraries: <internal-lib>: failed to map segment from shared object` and trying in muvm I get a SIGILL. Any idea how to debug that?
14:03john-cabaj has joined #asahi-alt
14:06chadmed has quit [Quit: Konversation terminated!]
14:06chadmed has joined #asahi-alt
14:56chadmed has quit [Read error: Connection reset by peer]
14:57chadmed has joined #asahi-alt
15:17n3ph has quit [Quit: WeeChat 4.5.2]
15:23n3ph has joined #asahi-alt
15:33john-cabaj has quit [Ping timeout: 480 seconds]
16:46CookieCutter has joined #asahi-alt
17:12CookieCutter has quit [Ping timeout: 480 seconds]
19:07n3ph has quit [Ping timeout: 480 seconds]
20:19hightower3 has joined #asahi-alt
20:23n3ph has joined #asahi-alt
20:25hightower4 has quit [Ping timeout: 480 seconds]
20:32n3phI've quickly tried app-emulation/wine-vanilla with arm64ec and got:
20:32n3ph0024:err:environ:init_peb starting L"Z:\\home\\n3ph\\Downloads\\SteamSetup.exe" in experimental wow64 mode
20:32n3phwine: failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
20:34n3phI do want to set ABI_X86, right?
20:36chaos_princessYou want USE=wow64
20:53n3phsteam progressed with downloading, suddenly regressed and finally froze with one thread constantly at 100%
20:57n3phrestarting it continues download and it seems it keeps downloading for some seconds after the progress dialog freezes
21:00n3phso with `killall steam.exe && wine64-vanilla-10.18 Downloads/SteamSetup.exe` it will get installed eventually after 50(?0 retries
21:02dcavalca8569797667 has joined #asahi-alt
21:03n3ph`wine-vanilla-10.18 "C:\\Program Files (x86)\\Steam\\Steam.exe"`
21:06n3ph[2025-11-06 22:03:24] Downloading update (31,955 of 284,694 KB)...
21:06n3ph[2025-11-06 22:04:58] Error: Download of package (public_all) failed after 0 bytes (0 : 200).
21:06n3ph[2025-11-06 22:04:58] Downloading update (19,601 of 284,694 KB)...
21:06n3ph[2025-11-06 22:05:09] Error: Download of package (steamui_websrc_all) failed after 0 bytes (0 : 200).
21:06n3ph[2025-11-06 22:05:09] Downloading update (10,431 of 284,694 KB)...
21:06n3ph[2025-11-06 22:05:58] Error: Download of package (bins_cef_win32_win7) failed after 0 bytes (0 : 0).
21:06n3ph[2025-11-06 22:06:09] Error: Download of package (bins_webhelpers_win32_win7-64) failed after 0 bytes (0 : 0).
21:08dcavalca856979766 has quit [Ping timeout: 480 seconds]
21:14n3ph has quit [Ping timeout: 480 seconds]
21:16chadmed has quit [Quit: Konversation terminated!]
21:16chadmed has joined #asahi-alt
21:18chadmed has quit [Read error: Connection reset by peer]
21:19chadmed has joined #asahi-alt
21:21chadmed has quit []
21:22chadmed has joined #asahi-alt
21:47vimproved has quit [Ping timeout: 480 seconds]
21:49john-cabaj has joined #asahi-alt
21:54vimproved has joined #asahi-alt
21:58n3ph has joined #asahi-alt
22:00n3phI've clicked cancel after 51 minutes: https://bpa.st/HTIQ
22:09n3ph has quit [Ping timeout: 480 seconds]
22:26john-cabaj has quit [Ping timeout: 480 seconds]
23:18n3ph has joined #asahi-alt
…