this post was submitted on 23 Nov 2024
670 points (89.2% liked)

linuxmemes

21393 readers
1345 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
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    670
    Windows VS Linux (part 2) (lemmy.world)
    submitted 1 day ago* (last edited 1 day ago) by trespasser69@lemmy.world to c/linuxmemes@lemmy.world
    217 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] TunaCowboy@lemmy.world 3 points 22 hours ago

    Most of the time you can just download a release and place the binary in path (or a symlink).

    Compiling it yourself should not 'messing up' anything, it should build locally:

    ./configure
make -j$(nproc)

    Now it's just built, nothing on your system has changed. make install will place requisite files where they need to go, but this generally configurable via prefix or equivalent. You may need to install dependencies, but that's usually a simple exercise in reading the output from the configuration step.

    Compiling software is easy as fuck and is incredibly flexible.