polarenviro.blogg.se

1. #REINSTALL MAC OS ERROR COULD NOT FIND INSTALLATION INFORMATION FOR THIS MACHINE INSTALL#
2. #REINSTALL MAC OS ERROR COULD NOT FIND INSTALLATION INFORMATION FOR THIS MACHINE PORTABLE#

In that case, you would indeed need to check out the original source, make appropriate changes to the Autotools-specific input files ( configure.ac, Makefile.am, etc.), and run the Autotools on them to generate a new configure file.

And even then, you probably won't need the Autotools unless you change the project's dependencies.

#REINSTALL MAC OS ERROR COULD NOT FIND INSTALLATION INFORMATION FOR THIS MACHINE INSTALL#

The only reason you should need to install and invoke the GNU Autotools yourself is if you want to do development work on a project built with Autotools.

#REINSTALL MAC OS ERROR COULD NOT FIND INSTALLATION INFORMATION FOR THIS MACHINE PORTABLE#

The distribution tarball contains a highly portable configure script that scans the build environment, checks for dependencies, and constructs a Makefile customized to your system. The reason that you, the user, don't need the GNU Autotools to compile an Autotools-packaged project is that the developer has already used the various Autotools programs to generate a "distribution tarball" that can be used to build the software on any Unix-like system. That's all you don't need to invoke any of the GNU Autotools, and don't even need to have the GNU Autotools installed on your system. configure & make & sudo make install incantation. You untar the package and utter some variant of the standard. For projects that are hosted entirely on GitHub, Savannah, or some similar hosting service, these tarballs will usually be found behind some link labelled "Download" or "Releases". These normally take the form of tarballs distributed on the project's website.

You should instead download the packaged source release provided by the developer. If all you want to do is compile and install a project released with the GNU Autotools, then you should not check it out from the source control system. In fact, in the case of the Erlang XMPP library mentioned by the OP, the misunderstanding appears to be on the part of the developers. This question, and most of the other answers here, arise from a misunderstanding of how projects using the GNU Build System (a.k.a.