Good ${greeting_time}, Anna!

08 Feb 2021 15:37:00, you wrote to me:

 MS>>>> 1) Any one possibly tell me why everytime I try to "make" I get
 MS>>>> errors, snap, flatpack, appimage, .deb and rpm work fine but if I
 MS>>>> have to try to "make" it fails.  Any suggestions..?
 ACN>>> When make fails, you should be able to see an error message that
 ACN>>> could tell you "why" it failed. If some .h files are missing, you
 ACN>>> could search for the corresponding -dev package and install it.
 AV>> In a properly designed systems you'd never need to install the
 AV>> development packages: they should be installed only inside of a
 AV>> clean build environment.
 ACN> ?!?!?!?
 ACN> The original poster wants to install software via "make" and I
 ACN> guess this means to compile the program which indeed needs
 ACN> development programs.

Any and all software should (as in FTA-1006 and RFC-2119) be built as the packages and installed with a package management system. Otherwise your favourite system would turn into a Slackware regardless of your will.

 ACN> What you do on your systems was not the question - or do you have a
 ACN> better solution with your "properly designed system"?

Yes, two. First is "hasher", which prepares a clean build environment and runs it in a container using unshare() system call. Second is "gear", which solves the compile-time dependencies, installs them into a build container, creates source package from a git commit-id and feeds all this stuff to the hasher.

So the rebuild becomes as simple as

alias gh 'time gear-hsh --commit --verbose'

running as an unprivileged user, and the result is the RPM packages.

 ACN>>> Also, the meta-package "build-essential" is helpful when compiling
 ACN>>> packages.
 AV>> I'd never use the system where such package does really exist...
 ACN> Then stay away from everything that is derived from Debian GNU/Linux.

I do (and recommend) that since CVE-2008-0166 :-)


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
--- /bin/vi