Pádraig Brady wrote: > Jim Meyering wrote: >> >> What do you think about suggesting with each how to install >> the missing package, e.g., >> >> You can install the required libgmp.* files >> via "yum install gmp-devel" on a fedora-based system, >> or "apt-get install gmp-devel" on a debian-based system. >> >> The easier we make it for people to discover which libraries are >> required/recommended and to install them, the more often people will use >> them. >> >> No big deal, though. > > I thought about it but didn't do that for 2 reasons. > > 1. It's not generic. What about archlinux, bsd, ...
It's your call. I figured that making it easier for the vast majority compensates for being less than perfectly generic. I suspect that targeting apt-based and yum-based distros would cover well over 80% of our audience. > 2. The package names might change on fedora, debian Unlikely, but as I said, no big deal. > Hmm maybe if I clarify the messages to the following: > > configure: WARNING: libacl development library was not found or not > usable. > configure: WARNING: GNU coreutils will be built without ACL support. > configure: WARNING: libselinux was found but selinux/selinux.h is missing. > configure: WARNING: GNU coreutils will be compiled without SELinux > support. > configure: WARNING: libattr development library was not found or not > usable. > configure: WARNING: GNU coreutils will be built without xattr support. > configure: WARNING: libcap development library was not found or not > usable. > configure: WARNING: GNU coreutils will be built without capability > support. > configure: WARNING: libgmp development library was not found or not > usable. > configure: WARNING: GNU coreutils will be built without GMP support Even better. Thanks!
