New answers tagged

0

Consider using the undocumented --version-control none option. That option is documented for the FreeBSD variant of patch.


1

None that I'm aware of. Most of the error messages spewed by configure scripts are easy to understand and act upon. When I don't understand what it's complaining about (happened maybe once or twice during my entire life) I google it up. Again, none that I'm aware of. You can use rpm -qf /path/file in Fedora and dpkg-query -S /path/file in deb based distros ...


Top 50 recent answers are included