this post was submitted on 26 Oct 2025
48 points (100.0% liked)

Linux

59312 readers
516 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
48
Building from source - disadvantages? (slrpnk.net)
submitted 6 days ago by oeuf@slrpnk.net to c/linux@lemmy.ml
30 comments fedilink hide all child comments
 

Are there any risks or disadvantages to building software from source, compared to installing a package? Can it mess with my system in any way?

I usually avoid it because I've found it to be a faff and often doesn't work anyway but in a couple of cases it has been necessary.

you are viewing a single comment's thread
view the rest of the comments
[–] Aiwendil@lemmy.ml 22 points 6 days ago* (last edited 6 days ago)

Gentoo user....but assuming now it's about building on distributions that don't automate it like gentoo.

Disadvantages:

  • No easy way to uninstall again. Some build systems generate lists of files that were installed or even some uninstall rules but that requires to either keep the build directory with the source-code around or to make backups of the necessary build files for proper uninstall. And in some build systems there are no helpers for uninstalling at all.
  • Similar...updating doesn't guarantee to remove all traces of the previous version. If the new build overwrites every file of the previous version...fine. But if an update version doesn't need files anymore that were installed in previous versions those will usually not get remove from your system and stick around.
  • In general lack of automatism for updates
  • Compiling takes time
  • You are responsible for dealing with ABI breakages in dependencies. In most cases the source-code you compile will depend on other libraries. Either those come from your distro or you also build them from source...but in both cases you are responsible for rebuilding a package if an update to one of the dependencies breaks the ABI.
  • You need build-time dependencies and depending on your distro also -devel packages installed. If source-code you install needs an assembler to build you have to install that assembler which wouldn't be necessary if you installed the binary (You can remove those build-dependencies again of course until you need to rebuild). Similar for -devel packages for libraries from your distro....if the source-code depends on a library coming from your distro it also needs the header files, pkgconfig files and other development relevant files of that library installed which many distros split out in own -devel packages and that aren't necessary for binaries.
  • You have to deal with compile flags and settings. It's up to you to set the optimization level, architecture and similar for your compiler in environment variables. Not a big deal but still something someone has to look into at the start.
  • You have to deal with compile-time options and dependencies. The build-systems might tell you what packages are missing but you have to "translate" their errors into what to install with your package manager and do it yourself. Same for the detection of the build systems...you have to read the logs and possibly reconfigure source-code after installing some dependencies if he build systems turned off features you want because of lacking dependencies.
  • Source-code and building need disk space so make sure you have enough free. Similar with RAM...gentoo suggests 2GB of ram for each --job of make/ninja but that's for extreme cases, you usually can get away with less than 2GB per job.

Of course you also gain a lot of advantages...but that wasn't asked ;)

You can "escape" most of the mentioned disadvantages by using a distro like gentoo that automates much of this. It's probably worth a look if you plan on doing this regularly.

edit:typos