this post was submitted on 21 Dec 2023
41 points (74.1% liked)

linuxmemes

21273 readers
1321 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     

    "Error 2", excuse me wtf am I supposed to do with this information?

    downloaded linux kernel and tried to compile, installed all the shit required but noooo error 2 who the fck come up with this shit

    you are viewing a single comment's thread
    view the rest of the comments
    [–] Willem@kutsuya.dev 7 points 11 months ago

    It's quite a bad UX, but generally error 2 from make means the called program resulted into an error.

    Usually this is accompanied with another error somewhere up the log. Multiple cores can make this a challenge to scan the log for however, so maybe try compiling without the -j argument, that should get the actual error closer to the end.

    From my experience, it's usually an outdated config for the kernel (like using a config for 5.1 while compiling 6.7) or a missing dependency. However the real error will be somewhere among the logs, who knows, maybe it's a missing processor instruction (it's really bad UX).