pfft. ln -s new_library.4.4.7 old_library.4.2.8
all done!
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.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 remove France.
pfft. ln -s new_library.4.4.7 old_library.4.2.8
all done!
I wish Lemmy was able to have emoji reactions to comments just so I could react with a horrified face to this comment.
In lieu of that, I'll just have to put it here: π±
If it would be that easy. The problem I had was, that I installed a dependency using my package manager, but to compile my originally wanted software I had to provide a cmake file (of the dependency I installed via my package manager) to the compiler, which I of course did not have.
This often comes with the *-dev version of the dependency. The normal one contains the binaries, the dev version includes headers and often the FindPackage
The last picture in the meme always bothered me, because the sequence doesn't make any sense physically. (Popping the rake from mid air and doing the wrong flip and such)
So, I went on to find the sequence that I believe it was drawn from.
make: error: libX11.so permission denied or not found make: failed, something something finishing remaining jobs.
dear god what does it mean
I get that your issue was probably more nuanced than that, but what's so confusing about inatalling missing build dependencies? If projects have a build guide sometimes they'll straight up give you an install command for your distribution. If not, it's up to you to find the package names corresponding to what you need to install since they can differ from distro to distro.
LMAO, back in my Slackware days (3.4, 3.6, 4.0, 7.0), If I had to build from source, which was most things, step1: ./configure step2: install the missing package step3: goto step1 until no missing packages identified step4: make step5: make install
Sometimes my packages were too old, So I would just go to step1 for each package that also needed to be newer. I'm not even a Linux Expert, and I definitely wasn't a Linux Expert then. All the building from source helps me jump into software projects and become productive real quick though.
More like:
No system package -> installing from user repos -> appimage -> flatpak -> creating your own package -> using a VM with a distro that has the package -> not installing package
If after that you still don't have it, ~~it wasn't meant to be~~ it's probably just not very good software.
Personally go: Flatpak (I like easily controlling an apps premissions) -> flatpak version is broken... Try system package -> distrobox -> compiling -> appimage -> not installing a package
Distrobox/containerd is so nice since a lot of the niche tools I use require Debian or Ubuntu dependency versions, but I'd be lying if I said everything "just works"
*Laughs in Nix
*accidentally uninstalls python base package trying to fix dependency conflicts in apt
All these different package manager systems.
I think we just need to consolidate and make a standard one
nix-shell is great too. sort of like a "demo" of something before actually committing to it or if you just want to use something one off without adding it to your config and rebuilding.
As a dev it's fantastic for testing also. can just try something on a bunch of browsers without actually installing the browser. love it.
I installed Rocky linux on my new server instance today and I found out that vnstat is not available as a package in the repos. It used to be available on the older versions. π It's been a while since I got back to Linux for my personal use.
Bruh just use nix, flatpak or appimage πΏ (we don't talk about snaps)
There should be some kind of automated certification for git repos, where if the described install process does not complete on a default install of the most popular OS, the software gets a big red "does not work" label.
Me on gentoo with my fucked up GCC and python versions. I must have spent so many hours compiling trying to get this shit to the right versions on a Chromebook with very little disk space.
Its cooked, I know its cooked but i dont want to go through the effort of reinstalling.