Gentoo On arm - Currently compiling gnome -

[Gentobobbyuk]

Hey guys and its me again .
I have lots of loverly questions to ask today .

I have really been struggling to get the Gentoo 2 image to work ive been stcuk on it for weeks , I decided to get a multiple pi 4s an 3s I have 26 all together.

I really want to help the arm community, by using my spare time and pis to try compiling multiple things n different ways .

I document every single Gentoo i get working on had problems with or a forum member has helped me with I have massive amount of guides which i have simplified for other users all coming very soon.

My first question guys is why is arn so awkward ?

There are no guides available but im sure they used to be ?

All the guides for the pis are so different i dont even mean by a few commands they all seem to be doing things complete diff,
I really cant get my head around the 32 bits currently.

IS there something about arm that makes the install process so complicated , Like spark amd64 x86 and i believe a few others pretty much the install process for getting Gentoo base onto the system is pretty straight forward . Ok i have had problems on others before but not to this extent .

I sometimes sit here for hours recompiling things differently withdiff flags and so on to get different results , I found lots of flags for old apple macs need to been changed snd things like no -pipe for machiens with less gb of ram and so.

Im looking for some help on finding out more about arm i have searched the web and there many results but its all abit mind blowing .


I used to genpielite image and tried to emerge gnome-light .
Emerge --sync first tells me that the it has not been synced for 256 days . After a sync it stays stuck hasent synced for 114 days . Even after a oneshot portage no futher results on fixing this .

Irt has been very very very hard trying to emerge gnome .

having eselect set to rpi64 makes things very hard to emerge

I have lower makeopts set and ive tried to edit my make.conf so it kind of doesnt look like the onerovided by genpie.

Because there is little to no documentation i dont have the slightest clue at all that it is going to work after finishing .

Ive had to update the world and spend ages trying to unmask certainly applications .

The genpie feel when using Gentoo doesnt feel so Gentooish .

For one where is the kernel stored here it says there i no /usr/src/linux .
Can i use Gentoo-sources ?

Gnome-ight is tell me it cant find a kernel source blah blah Im alone on this one .

So im guessing it wont work haha,

How do i edit my current kernel on the pi4 ?
Im guessing it just goes into the boot loader of the sdd card .


Is there a way i can make this feel like a normal sort of Gentoo feel .

Everything feels complicated getting packages just seems a ball ache.

Im trying to figure this all out and its so frustrating

If someone could explain to me how portage is working on this Genpie64 it seems to be working differently .

Gnome is not far of being fully emerged it doesnt no where the kerel source is can someone help me with this 2

I just want to get some nice easy to follow step byt step guides together so we can get more users using the pis .

im happy to try out or do any test that Gentoo team may need i have thee time , im finding so hard to get info online . #

Apricate it , cant thank everyone who is alays offering a hand or bit of advice .

I apricate all the hard work everyone puts in .

[Gentobobbyuk]

dev-lang rust are not nuice to compile on arm , 'No cross compiling either i like to spend the time physically doing it I believe all packages until known stable should not be cross compiled , because i can run the same command corss compiled or not and sometimes not always but it does happen and it doesnt work . Im really just looking for as much help so i can then repay the help test as much and get nice written documentation together .

The pis might as well be doing as much testing as they can if it benefits the community ,


B

[ShorTie]

Personally, I think "All the guides for the pis" or wiki's need balled up and thrown AWAY !!
Not a single one is valid any more !!

Just about finished to a release point of piGentoo you might be interested in.

[NeddySeagoon]

[Gentobobbyuk]

Well from nearly having nothing workting to gnome is nearly fully compiled.
Can you help me get it back to a normal make.conf for the pi4 .

I have tried for weeks to get suppourt i dont like other distros and its really upsetting not be able to use gentoo.
NOw i have gentoo working finally on arch its all mess because i can only het saski stuff to work .

I have spent day and days following each guide litterally copying and pasting . Doesnt work .



I no the method very well neddy but i cant for the life of me getting it working 32 bit
I do sparc amd64 and x86 with barley any issues ever.

This is mind blowing me.


I just want one simple basic guide or to no how to do it and write one my self .

Does anyone actually chekc them after writing them .
Key factors missed on everyone.


I have updated all the use flags and tried to delete as much as saksi stuff as possible but i dont no what i am doing on arm .

I have no default arms make.conf to work with.

Gnome hss taken days and days to compile i no its not going to work due there not even being a usr/src/linux ,

I have google for weeks guys im really not getting any help its so frustrating ,

[Gentobobbyuk]

If we could hel clear out saski crap and get it back to normal .

Can i use gentoo -sources .

Not even able to emerge raspberry-sources due t saski

[NeddySeagoon]

Gentobobbyuk,

Its going to be very messy because you are a long way out of date.

The steps are

1. Switch to the ::gentoo repository
2. Choose a profile from the main repo.



Code:

Pi4_~arm64 /usr/portage # eselect profile list Available profile symlink targets:   [1]   default/linux/arm64/17.0 (stable)   [2]   default/linux/arm64/17.0/desktop (stable) *   [3]   default/linux/arm64/17.0/desktop/gnome (stable)   [4]   default/linux/arm64/17.0/desktop/gnome/systemd (stable)   [5]   default/linux/arm64/17.0/desktop/plasma (stable)   [6]   default/linux/arm64/17.0/desktop/plasma/systemd (stable)   [7]   default/linux/arm64/17.0/desktop/systemd (stable)   [8]   default/linux/arm64/17.0/developer (stable)   [9]   default/linux/arm64/17.0/systemd (stable)   [10]  default/linux/arm64/17.0/big-endian (exp)   [11]  default/linux/arm64/17.0/musl (exp)   [12]  default/linux/arm64/17.0/musl/hardened (exp)   [13]  genpi:default/linux/arm64/17.0/desktop/rpi3 (exp)   [14]  genpi:default/linux/arm64/17.0/desktop/genpi64 (exp)



3. fix what breaks

Along the way, install a suitable kernel but that's well down the list.

Do not choose a systemd profile as that would be another complication that you don't need.

The hard bit is 3. fix what breaks.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[Gentobobbyuk]

Ok needy im going to explain everything I've done and maybe you can understand bit more.

First thing i did remember im using the Saki because i cant get anything else to work,


Was install saki light .

emerge --sync this has not been synced for 250 days like ok jeus.
after the merge sync is compete it then tells me emerge sync has not been updated for 114 days bloody odd.

I then emerge --oneshot portage as it told me to.
Still 114 days old
emerge --sync again no difference .


So i opened up /etc/make.conf

I add some use flags X gnome , -qt4 -qt5 puleaudio , -kde and elogind -systemd and a few more.

Tried to emerge -avuND . Ends up been masked and even trying to unmask the usual way didnt work as saki has everything moved around .

I basically then did various things trying to figure stuff out for myself i started to un emerge the things that where causing conflicts . for example glibc because i uninstalled them and then remerged them sometimes serpatley it kind of got things rolling .

With various , etc-updates multiple --autounmask-write options followed by etc-update source /etc/profile dispatch-confs unmerging remerging . deepcleans revdep rebuilds

I have now successfully unmerged everything i needed to and the complete world set has nearly finished updating . im on gcc atm package 351 of 668 . for gnome light on the pi 4.

The problem is i no its not going to work it told me at the start of compiling that i have no usr src linux directory and to make sure its pointing to my linux kernel and so fourth .

it would be loverly if we could find out how to sort this kerel issue out .

Maybe after all the apps have updated i may now be able to finally emerge raspberry-sources .

I have as said above over 30 pis i dont like other os but for some reason i am just struggling with gentoo on arm ,

It would be so bice to get this fuigured out and hae some nice stable desktops image pre done for pis .

I suppose i am alot futher than i was 2 3 weeks ago .

So hopefully everything is now going to be uptodate .

Lets fix this kernel . There is no /usr/src/linux and I would love to get my make.conf looking like normal arm make.conf


i hope that heekps explain kind of where i am .

I think ive manged to disabled some of saski stuff in make.

Im not comfortable on writing this file myself . I only no how to do this for my x86 and amd64 and sparc , but even with them i only no how to use the defaults and add to them as makeopts vide cards blah via handbook

[Gentobobbyuk]

just switching eselect from saksi is not easy brother . im not sure if its so out of date when u emerge it causes conflicts but its not easy .
Its a complete mess i did try that first although i did have to switch profile to do this i had to do what i mentioned above try trick uninstall reinstall.

So by the end of today gnome0kight will be compiled

Just the kernel thing to fix i believe

[NeddySeagoon]

Gentobobbyuk,

I've not tried switching a Sakaki binary install over to pure Gentoo. I agree its unlikely to be easy.
Its six months out of date. That makes it difficult alone. Never mind not being Gentoo to start with.

For kernel sources, use

[ShorTie]

Sakaki was the Queen of ebuilds.

If you make an image or work off of a usb device, you can build any thing on any thing.

See everyone wants to Upgrade/Fix Sakaki's genpi64.

Which is the wrong approach to me.
She has so many Custom ebuilds, that is like Impossible, imho.

Plus she has everything locked into a version, not a general emerge xxxx.
Which makes Updating a real PIA to me.
She had too, I guess, not much Twas arm64 when she started right NeddySeagoon ??
Still needed stuff missing, got an emerge -pv you might be able to help on NeddySeagoon.
And stuff like sys-kernel/raspberrypi-sources still don't work right, imho.

There is more to sys-boot/raspberrypi-firmware then just emerge.
You must also redo root= in cmdline.txt, then save it off into portage/savedconfig, imho.

I'm trying to come up with a image maker that works from the ground Up.
Using a Cross chroot for making arm images on a arm64.
Just need to get raspberrypi-sources to link and configure Properly, lol.

[NeddySeagoon]

ShorTie,

Sakakis repo was primarily aimed at supporting the Genpi64 binary Gantoo disto.
Many of the ebuilds were generally useful, most of which have been taken up into the ::gentoo repo.
A few apply arm64 or even Pi specific patches. They are harder to update and/or get into Gentoo.

The GenPi64/Build.Dist project is worth a look.

If you have a problem with a packace in the ::gentoo repo, feel free to open a bug.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.