Hm. Interesting. Can you provide more than that? I'm assuming yo have cmake installed already
#Error when emerging on setup
wild echo
rose sentinel
I've seen this when env was out of whack and or profile wasnt correct - been some long time tho 🤔
plucky cipher
probably not
rose sentinel
no, cmake is required for QT
wild echo
Cmake is the build system.
If you're on amd64 you can try and break this with a binpkg.
plucky cipher
emerge -g cmake
rose sentinel
you can attempt to emerge -1 cmake prior to get cmake installed and then do the rest
wild echo
Or just emerge cmake by itself
plucky cipher
emerge wgetpaste and run wgetpaste -c "type the command here that failed"
wild echo
Yes that.
coarse haven
This really reads like its not in the chroot but let's see
plucky cipher
emerge wgetpaste
wgetpaste -c "emerge --pretend --verbose --update --deep --newuse @world"
ls / and see if there is a stage3 there
wild echo
```
emerge wgetpaste
wgetpaste -c "emerge --pretend --verbose --update --deep --...
Drop ask, add pretend
plucky cipher
Drop ask, add pretend
ok
wild echo
(it will never send output because it's hanging waiting for you to hit 'y' or 'n'
rose sentinel
ask will autodeny on non-tty
plucky cipher
use new message
coarse haven
Send wgetpaste -I too please
wild echo
ask will autodeny on non-tty
It should, but there's no guarantee.
rose sentinel
true true
plucky cipher
ok send the link it gave you
coarse haven
It _should_, but there's no guarantee.
I've never seen it drop but thats not an issue right now 🙂
wild echo
Quite possibly, that's a full DE. I'll leave you to handle this one 😦
plucky cipher
we make it say chroot manually
its not something the system detects
export PS1="(chroot) $PS1" only says change the prompt to write chroot
its got nothing to do with whether you are actually in chroot
plucky cipher
not at all
i ran emerge on a live iso once and got a simillar result so thats how i found out
repeat the chroot steps
and share any errors other than already mounted
coarse haven
Might be easier to start over just to be sure
But you OK with this from here?
(Ping me if you need me)
plucky cipher
Might be easier to start over just to be sure
it feels like he extracted a arm64 stage
and the chroot failed
coarse haven
What's the error?
coarse haven
(Was mine too but I was waiting for more info)
plucky cipher
how big the iso would be if it had build tools not removed
i guess i can build one myself to find out
coarse haven
@plucky cipher start over please and grab the amd64 desktop stage3 for either operc or sysyemd
Should solve everything
plucky cipher
and dont rm -rf /mnt/gentoo
just reboot the computer
also make sure its amd64 and not arm64
arm64 is for ARM devices like the raspberry pi
coarse haven
how big the iso would be if it had build tools not removed
We'll discuss this outside of here
plucky cipher
no we continue here
yes
oh true
go through the handbook again
share any errors
gparted
device>make partition table
did you rm -rf /mnt/gentoo?
after mounting
reboot then
you deleted the literal /dev/sda file
making the disk inaccecible
lemme learn about bind mounts real quick
rose sentinel
mount --rbind /from /to (rbind adds all submounts as well)
if that helps @plucky cipher
didnt read up
plucky cipher
mount --rbind /from /to (rbind adds all submounts as well)
no i mean i wanted to explain what it does
plucky cipher
it makes the files in /dev also available in /mnt/gentoo/dev
rose sentinel
bind mounts basically pretend like that same FS is mounted elsewhere; it doesnt need to be a whole FS either, you can bind mount folder-trees and subpaths
plucky cipher
have a nice day