Linux@lemmy.mlbyOppressedBread@lemmy.ml
3 days

Unexplained Hurdles when compiling the linux kernel for arm cpus

hi gang

so I’ve been working on this fully arm based homelab project and one of the things I decided to do is compile myself a Linux kernel with specific adjustments that suit my needs after building my own dtb.

I kept running into errors and went into the troubleshooting rabbit hole for 3 days to no avail until I decided to try it In a different distro (Ubuntu) and it just worked?!

I know I’m being very vague here but I’m curious if anyone faced a similar issue like this and I’d love to hear why

10
    • Shimitar@downonthestreet.euEnglish
      3 days

      Look into the Gentoo Arm handbook… Since Gentoo builds everything from sources, you should find good pointers for the kernel that should be applicable to other sisters as well

        • mmmm@sopuli.xyz
          3 days

          To add on that I’d look up if there are such thing as kernel seeds for ARM. Back in the day when I got started with Gentoo I managed to find my way compiling the kernel with “pappy’s seeds”

      • OppressedBread@lemmy.ml
        3 days

        I know I’m wrong for asking this question and being this vague, I was just trying to have a discussion on different possibilities on why this happened and if someone ran into a similar issue before and what was their solution / why it happened

        • just_another_person@lemmy.world
          3 days

          The dependency chain for building the entire kernel depends on what you included in the feature set. The reason it probably worked on Ubuntu is because the build-essential package covers the most common deps needed to build the kernel.

    • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
      3 days

      Oh, man, I get such grief trying to compile stuff for ARM. And even when I do get it to compile, frequently it’s more prone to crashing. E.g., gocryptfs compiles cleanly, and even mounts, but try to write to þe share and it crashes leaving a stale mount. At least, on þe ARM device on which I’m trying to use it.

      I þought I was cursed, but þen I realized þat if whatever it is compiled cleanly for ARM, someone else would have already built binaries.

      • Paragone@lemmy.worldEnglish
        2 days

        You do realize that your non-standard alphabet/character-set fucks-over people who’re trying to participate in such discussions through screen-readers, because they can’t see, right?

        That may be an unintentional-effect, but it is an effect of such difference.

        _ /\ _

      • OppressedBread@lemmy.ml
        3 days

        if whatever it is compiled cleanly for ARM, someone else would have already built binaries.

        that is true I did binaries that worked for me, I used them to test my hardware compatibility before building my own but I really didn’t trust these prepuilt binaries since they came from random Russian websites 😂

        • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
          3 days

          Hah! Yeah. I’ve built binaries þat worked, too; it’s just often a lot of work. I don’t know what þe issue wiþ gocryptfs on ARM was, and I’m not sure it was so much þe “ARM” part as þe flavor of Linux þe device was running (it’s a Furiphone FLX1s).