#asahi-alt · 2025-11-06 13:06
n3phnevertheless, my intention was more like a heads-up #asahi-alt · 2025-11-06 13:06
chaos_princessfair. but that is a generic-gentoo issue#asahi-alt · 2025-11-06 13:06
n3phchaos_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") #asahi-alt · 2025-11-06 13:04
chaos_princessi do have checkreqs in fex to maybe prevent it#asahi-alt · 2025-11-06 13:04
chadmedi 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#asahi-alt · 2025-11-06 13:04
n3phAnd there is also the approach of `PORTAGE_TMPDIR="/var/tmp/notmpfs"` additionally #asahi-alt · 2025-11-06 13:03
chadmedespecially when people like to use cheap ssds :p #asahi-alt · 2025-11-06 13:03
chadmed\/var/tmp/portage being a tmpfs is not an uncommon setup #asahi-alt · 2025-11-06 13:02
n3phchaos_princess: yes, saw it in the ebuild #asahi-alt · 2025-11-06 13:02
chaos_princesswell, it shouldn't be a tmpfs either#asahi-alt · 2025-11-06 13:02
n3phI have one on /var/tmp/portage #asahi-alt · 2025-11-06 13:02
n3phchaos_princess: I haven't said I have a tmpfs on /var/tmp#asahi-alt · 2025-11-06 13:02
chaos_princessin case of fex it is that it brings an entire x86 rootfs with it#asahi-alt · 2025-11-06 13:01
chadmedand like, yeah it would. fex is quite a large cpp project and an ~allmodconfig kernel is huge too#asahi-alt · 2025-11-06 13:00
chaos_princess/var/tmp is not supposed to be a tmpfs#asahi-alt · 2025-11-06 12:56
n3phEmerging kernel and FEX at the same time in parallel fills up an 8gb tmpfs on /var/tmp/portage.. #asahi-alt · 2025-11-05 15:37
edogrooveoh sorry for multiline, just do a copy-paste. No problem, going on matrix :)#asahi-alt · 2025-11-05 15:32
chaos_princessso, 1. please do not paste long multiline messages into irc. 2. this channel is for "alt-distros", which in this case is "everything that is not fedora.". 3. Mind also reporting it in #asahi:fedoraproject.org on matrix? more likely for someone involved to see it#asahi-alt · 2025-11-05 15:31
edogrooveProduct Name: Apple MacBook Pro (13-inch, M1, 2020)#asahi-alt · 2025-11-05 15:31
edogrooveGraphics Processor 3: Apple M1#asahi-alt · 2025-11-05 15:31
edogrooveGraphics Processor 2: Apple M1#asahi-alt · 2025-11-05 15:31
edogrooveGraphics Processor 1: Apple M1#asahi-alt · 2025-11-05 15:31
edogrooveMemory: 7.3 GiB of usable RAM#asahi-alt · 2025-11-05 15:31
edogrooveProcessors: 4 × Apple Firestorm (M1), 4 × Apple Icestorm (M1)#asahi-alt · 2025-11-05 15:31
edogrooveGraphics Platform: Wayland#asahi-alt · 2025-11-05 15:31
edogrooveKDE Frameworks Version: 6.19.0#asahi-alt · 2025-11-05 15:31
edogrooveKernel Version: 6.16.8-400.asahi.fc42.aarch64+16k (64-bit)#asahi-alt · 2025-11-05 15:31
edogrooveQt Version: 6.9.3#asahi-alt · 2025-11-05 15:31
edogrooveKDE Plasma Version: 6.5.1#asahi-alt · 2025-11-05 15:31
edogrooveOperating System: Fedora Linux Asahi Remix 42#asahi-alt · 2025-11-05 15:30
chaos_princessand if so - witch one?#asahi-alt · 2025-11-05 15:30
chaos_princessis it fedora or altdistro?#asahi-alt · 2025-11-05 15:30
edogroove(you can't see the password you wrote)#asahi-alt · 2025-11-05 15:29
edogrooveBefore I discovered "reboot" I reinstalled 3 times, because if you don't try the keyboard to verify, in the next step you set a new wrong password#asahi-alt · 2025-11-05 15:28
edogrooveI was trying to set up an Italian keyboard with an Apple layout (not aluminum), and whatever I chose, it didn't change anything. It always typed the wrong characters. I solved the problem by restarting without completing the initial setup, so I could redo it. That solved the problem.#asahi-alt · 2025-11-05 15:28
edogrooveIt was a mix of English and French :)#asahi-alt · 2025-11-05 15:22
chaos_princessnon-english keyboards are weird#asahi-alt · 2025-11-05 15:16
edogrooveHi everyone, I wanted to report a bug regarding the keyboard during installation. I don't know if it's a known issue. It's a problem that prevents the desired layout from being set correctly. Before I explain, are you aware of this?#asahi-alt · 2025-11-03 10:57
chadmedyeah okay i think im getting it now. we need to build the arm64ec objects _and_ straight aarch64 then make the linker put them together#asahi-alt · 2025-11-03 09:15
chaos_princessand, well, if they did it mach-o style, it would be easy with a post-processing step, but arm64x means we need to glue them together during the link phase#asahi-alt · 2025-11-03 09:12
chaos_princessarm64x - you will either need custom cc/ld wrappers, or do something similar to how multilib wine worked, where you build it twice and then glue it together, kinda #asahi-alt · 2025-11-03 09:12
chadmedfun fun fun #asahi-alt · 2025-11-03 09:12
chadmedso, manual flag setting in the meson config files etc#asahi-alt · 2025-11-03 09:12
chadmedright okay now its making more sense#asahi-alt · 2025-11-03 09:11
chaos_princessarm64ec is easy, thats just a cross file#asahi-alt · 2025-11-03 09:11
chaos_princess't do arm64x#asahi-alt · 2025-11-03 09:11
chaos_princessmeson can#asahi-alt · 2025-11-03 09:11
chadmedor is that just for building the arm64ec binaries with no arm64x#asahi-alt · 2025-11-03 09:11
chadmeddo we need to do more than just add a cross file for it? i thought meson could deal with it now#asahi-alt · 2025-11-03 09:10
chaos_princessimo, the path forward is to reach to dxvk upstream and the arm64 valve people and ask them if they are open to making a hash of their meson build files to add arm64x support