On 29 July 2015 at 23:15, Itamar Gal <itamarggal@xxxxxxxxx> wrote: > Hey autoconf folks, > > I'm following some outdated instructions in an attempt to compile some > proprietary, closed-source, unsupported, legacy code. Here is what a > typical shell session looks like: > > $ autoreconf -fi > > src/Makefile.am:7: error: 'pkglibexecdir' is not a legitimate > directory for 'PYTHON' > autoreconf: automake failed with exit status: 1 You need to use a trick to circumvent automake's policing: https://www.gnu.org/software/automake/manual/html_node/Uniform.html >>>>>>>>>>>>> This feature can also be used to override the sanity checks Automake performs to diagnose suspicious directory/primary couples (in the unlikely case these checks are undesirable, and you really know what you’re doing). For example, Automake would error out on this input: # Forbidden directory combinations, automake will error out on this. pkglib_PROGRAMS = foo doc_LIBRARIES = libquux.a but it will succeed with this: # Work around forbidden directory combinations. Do not use this # without a very good reason! my_execbindir = $(pkglibdir) my_doclibdir = $(docdir) my_execbin_PROGRAMS = foo my_doclib_LIBRARIES = libquux.a >>>>>>>>>>>>> _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
