3 ms·
I get the distinct impression that the existing Linux package management ecosystem has evolved so thoroughly around C/C++'s complete lack of sane build tooling
by throwaway894345 5y ago
I get the distinct impression that the existing Linux package management ecosystem has evolved so thoroughly around C/C++'s complete lack of sane build tooling or package management, and it's ironically difficult for some reason to embrace languages like Go or Rust which make package management trivial. I don't know if it's a tooling issue or what, but this seems to be a common problem. I'd be really interested in opinions from people who know more about Linux package management from the maintainer side.
- cogman10 5y agoI think Linus really hits the nail on the head here. It's the fact that core libs, like glibc, are CONSTANTLY changing their ABI making it damn near impossible to ship a binary from one version of the platform to the next https://www.youtube.com/watch?v=Pzl1B7nB9Kc https://www.youtube.com/watch?v=Pzl1B7nB9Kc . You can still run windows 95 apps in windows 10. But running a ubuntu 12.04 binary in ubuntu 21.04? No way.
- AnIdiotOnTheNet 5y agoIt is so hilariously bad that Linux has an easier time running Windows applications than it does Linux applications from an older (or newer, or sideways) distro. It's been like this for decades, it has been complained about for decades, but there seems to be very little desire to fix it.
- zozbot234 5y agoThis is what containers are for. Wine is nothing special, it just installs a Windows userspace container alongside your existing system.
- ynik 5y agoglibc is perfectly backwards compatible. We still build software on Debian 7 (glibc 2.13 from 2011) and the binaries works just fine on Debian 11 (and also on most other glibc-based distributions). But you need to be careful to only use libraries that provide long-term binary compatibility. Most libraries you can find in the system package manager don't do this. Also, on Linux it's weirdly difficult to do it the other way around: use the current distribution to build binaries that also run on older distributions. On Windows this is trivial: I can develop on Windows 10, with the current VS2019 and the current Windows 10 SDK, and a simple "#define _WIN32_WINNT 0x600" is sufficient to make my binary work all the way to Windows Vista (2006). On Windows it's normal to ship libraries in the application directory instead of depending on a global /usr/lib/ installation; so non-Microsoft libraries that don't maintain a stable ABI are much less problematic. Also, good luck if you're on Linux and want to use an up-to-date gcc (e.g. gcc-8 for C++17 support) on an older distribution. Building gcc from source is easy, but the resulting gcc-8 will produce binaries that require symbols from libgcc-8, which the system libgcc won't have. We actually ended up patching gcc to disable the optimizations that introduce uses of new symbols not yet present in deb7 libgcc.
- diegocg 5y agoGlibc constantly changing their abi? Uh?