On Thursday 17 March 2011, Stefano Lattarini wrote: > > On Thursday 17 March 2011, Maynard Johnson wrote: > > Hello, > > I have installed a version of aclocal into /usr/local that's newer > > than my distro's version (I needed a fix from the newer version). > > But then I ran into a problem recently where the build of some > > package was failing because aclocal was not finding the pkgcfg.m4 > > file in /usr/share/aclocal. > > I created a dirlist in /usr/local/share/aclocal and added > > /usr/share/aclocal to it. That did indeed resolve the problem. > > But is that the best way to resolve this problem? > > > IMO, if you have control on the installation of the aclocal you are > using, this is the right fix (and the one I'd suggest and use in your > situation). > > > Maybe this is documented somewhere, > > > Yep: > > <http://www.gnu.org/software/automake/manual/html_node/Macro-Search-Path.html> > > If you think that's not clear enough, remember that suggestions and > costructive criticism are always welcome! > > But then I have to say, the page above is admittetdly not easy to find, > being indexed with the incompete title "Scanning configure.ac or > configure.in". Ralf, what about the attached patch (for maint)? > Maynard, are you OK with being added to the THANKS file? > > > and I just didn't see it, but it took me longer than I care to > > admit to resolve this. Seems like it could be a fairly common > > problem. Have others solved it in a more clever way rather > > than telling system owners they need to create a new dirlist > > if they've installed aclocal in a non-standard location? > > > Well, you could always resort to adding proper `-I' option to > you aclocal calls. Also, in the next automake release, aclocal > will probably support a new 'ACLOCAL_PATH' environment variable > that would help solving this kind of problems > > Regards, > Stefano > Ping on this? I'll push in 72 hours if there is no objection.
Regards, Stefano
