this post was submitted on 21 Dec 2023
3 points (100.0% liked)

linuxmemes

21210 readers
57 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!

    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

    top 8 comments
    sorted by: hot top controversial new old
    [–] [email protected] 2 points 10 months ago* (last edited 10 months ago)

    what if I wanted to laugh at a funny Linux meme, but see a whingefest with a screenshot of a terminal

    [–] [email protected] 0 points 10 months ago* (last edited 10 months ago) (1 children)

    Look at the build output for the error. Run the build again with "-j1" if neccessary.

    Also, try searching the web before crying on social media. If you can't solve your problems without being spoon-fed then GNU/Linux probably isn't for you.

    [–] [email protected] 0 points 10 months ago (1 children)

    Also, try searching web before crying on social media. If you can't solve your problems by searching the web then GNU/Linux probably isn't for you.

    Sheesh, let them be frustrated already. Besides, asking for help is totally valid.

    [–] [email protected] 0 points 10 months ago (1 children)

    Yeha, but you can ask for help without taking a shit on the effort of thousands of engineers.

    If you're using a whole kernel for free, at least be nice when very deep technical things that you clearly don't understand don't go as you expected.

    It's called having etiquette

    [–] [email protected] 0 points 10 months ago (1 children)

    Yeha, but you can ask for help without taking a shit on the effort of thousands of engineers.

    I doubt OP thought, 'I'm going to take a shit on thousands of engineers.' It's okay to not know what to do, including asking for help. If they don't know what to do with "error 2," they're obviously lost. This unwelcoming attitude to newcomers is a big problem, and in my opinion, it's probably best not to contribute to it.

    You can rephrase what you're saying and provide better help to someone who's completely lost in a much more polite and informative way. It's better for everyone.

    [–] [email protected] 1 points 10 months ago

    Did you not read his post? He is absolutely taking a shit on all the engineers. You can ask for help without cursing at and insulting the work of the engineers.

    [–] [email protected] 1 points 10 months ago* (last edited 10 months ago)

    There is always more information. Error 2 just means the make script couldn't finish I think. Scroll up :)

    [–] [email protected] 1 points 10 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).