How to overcome aclocal-1 15 is missing on your system warning

Question

Im trying to run a c   program on github   available at the following link https   github com mortehu text-classifier   I have a mac  and am trying to run it in the terminal  I think I have downloaded autoconf and automake but am not sure  To run the program I am going to the correct folder in terminal then running    configure  amp  amp  make    But I get the error      WARNING   aclocal-1 15  is missing on your system             You should only need it if you modified  acinclude m4  or             configure ac  or m4 files included by  configure ac              The  aclocal  program is part of the GNU Automake package             http   www gnu org software automake            It also requires GNU Autoconf  GNU m4 and Perl in order to run             http   www gnu org software autoconf            http   www gnu org software m4             http   www perl org  make       aclocal m4  Error 127   I have xcode and g   and all the things required to run c programs  but as is probably obvious  I have no idea what Im doing   What is the easiest  simplest way to run the program in the above link  I realise it comes with a readme and example usage but I can not get that to work

User · Answer

2018  yet another solution     https   github com apereo mod auth cas issues 97 in some cases simply running   autoreconf -f -i  and nothing else      solves the problem  You do that in the directory  pcre2-10 30   What a nightmare   This usually did not solve the problem in 2017  but now usually does seem to solve the problem - they fixed something  Also  it seems your Dockerfile should now usually start with  quot FROM ibmcom swift-ubuntu quot    previously you had to give a certain version dev-build to make it work

User · Answer

The problem is not automake package  is the repository  sudo apt-get install automake  Installs version aclocal-1 4  that s why you can t find 1 5  In Ubuntu 14 15   Use this script to install latest https   github com gp187 nginx-builder blob master fix aclocal sh

User · Answer

2017 - High Sierra It is really hard to get autoconf 1 15 working on Mac  We hired an expert to get it working  Everything worked beautifully  Later I happened to upgrade a Mac to High Sierra  The Docker pipeline stopped working  Even though autoconf 1 15 is working fine on the Mac  How to fix  Short answer  I simply trashed the local repo  and checked out the repo again  This suggestion is noted in the mix on this QA page and elsewhere  It then worked fine  It likely has something to do with the aclocal m4 and similar files   But who knows really   I endlessly massaged those files     but nothing  For some unknown reason if you just scratch your repo and get the repo again  everything works  I tried for hours every combo of touching deleting etc etc the files in question  but no   Just check out the repo from scratch

User · Answer

You can install the version you need easily   First get source     wget https   ftp gnu org gnu automake automake-1 15 tar gz   Unpack it     tar -xzvf automake-1 15 tar gz   Build and install     cd automake-1 15     configure  --prefix  opt aclocal-1 15   make   sudo mkdir -p  opt   sudo make install   Use it     export PATH  opt aclocal-1 15 bin  PATH   aclocal --version   aclocal  GNU automake  1 15  Now when aclocal is called  you get the right version

User · Answer

Before running   configure try running autoreconf -f -i   The autoreconf program automatically runs autoheader  aclocal  automake  autopoint and libtoolize as required   Edit to add  This is usually caused by checking out code from Git instead of extracting it from a  zip or  tar gz archive   In order to trigger rebuilds when files change  Git does not preserve files  timestamps  so the  configure script might appear to be out of date   As others have mentioned  there are ways to get around this if you don t have a sufficiently recent version of autoreconf   Another edit  This error can also be caused by copying the source folder extracted from an archive with scp to another machine  The timestamps can be updated  suggesting that a rebuild is necessary  To avoid this  copy the archive and extract it in place

User · Answer

The whole point of Autotools is to provide an arcane M4-macro-based language which ultimately compiles to a shell script called   configure  You can ship this compiled shell script with the source code and that script should do everything to detect the environment and prepare the program for building  Autotools should only be required by someone who wants to tweak the tests and refresh that shell script   It defeats the point of Autotools if GNU This and GNU That has to be installed on the system for it to work  Originally  it was invented to simplify the porting of programs to various Unix systems  which could not be counted on to have anything on them  Even the constructs used by the generated shell code in   configure had to be very carefully selected to make sure they would work on every broken old shell just about everywhere   The problem you re running into is due to some broken Makefile steps invented by people who simply don t understand what Autotools is for and the role of the final   configure script   As a workaround  you can go into the Makefile and make some changes to get this out of the way  As an example  I m building the Git head of GNU Awk and running into this same problem  I applied this patch to Makefile in  however  and I can sucessfully make gawk   diff --git a Makefile in b Makefile in  index 5585046  b8b8588 100644 --- a Makefile in     b Makefile in    -312 12  312 12    distcleancheck listfiles   find   -type f -print     Directory for gawk s data files  Automake supplies datadir   pkgdatadir     datadir  awk -ACLOCAL    ACLOCAL   ACLOCAL   true  AMTAR    AMTAR   AM DEFAULT VERBOSITY    AM DEFAULT VERBOSITY  -AUTOCONF    AUTOCONF  -AUTOHEADER    AUTOHEADER  -AUTOMAKE    AUTOMAKE   AUTOCONF   true  AUTOHEADER   true  AUTOMAKE   true  AWK    AWK   CC    CC   CCDEPMODE    CCDEPMODE    Basically  I changed things so that the harmless true shell command is substituted for all the Auto-stuff programs   The actual build steps for Gawk don t need the Auto-stuff  It s only involved in some rules that get invoked if parts of the Auto-stuff have changed and need to be re-processed  However  the Makefile is structured in such a way that it fails if the tools aren t present   Before the above patch       configure         make gawk CDPATH    ZSH VERSION       amp  amp  cd    amp  amp   bin bash  home kaz gawk missing aclocal-1 15 -I m4  home kaz gawk missing  line 81  aclocal-1 15  command not found WARNING   aclocal-1 15  is missing on your system           You should only need it if you modified  acinclude m4  or           configure ac  or m4 files included by  configure ac            The  aclocal  program is part of the GNU Automake package            lt http   www gnu org software automake gt           It also requires GNU Autoconf  GNU m4 and Perl in order to run            lt http   www gnu org software autoconf gt            lt http   www gnu org software m4  gt            lt http   www perl org  gt  make       aclocal m4  Error 127   After the patch       configure         make gawk CDPATH    ZSH VERSION       amp  amp  cd    amp  amp  true -I m4 CDPATH    ZSH VERSION       amp  amp  cd    amp  amp  true gcc -std gnu99 -DDEFPATH      usr local share awk   -DDEFLIBPATH     usr local lib gawk    -DSHLIBEXT    so    -DHAVE CONFIG H -DGAWK -DLOCALEDIR    usr local share locale   -I      -g -O2 -DNDEBUG -MT array o -MD -MP -MF  deps array Tpo -c -o array o array c        gcc -std gnu99  -g -O2 -DNDEBUG  -Wl -export-dynamic -o gawk array o awkgram o builtin o cint array o command o debug o dfa o eval o ext o field o floatcomp o gawkapi o gawkmisc o getopt o getopt1 o int array o io o main o mpfr o msg o node o profile o random o re o regex o replace o str array o symbol o version o      -ldl -lm     gawk --version GNU Awk 4 1 60  API  1 2 Copyright  C  1989  1991-2015 Free Software Foundation          There we go  As you can see  the CDPATH  command lines there are where the Auto-stuff was being invoked  where you see the true commands  These report successful termination  and so it just falls through that junk to do the darned build  which is perfectly configured   I did make gawk because there are some subdirectories that get built which fail  the trick has to be repeated for their respective Makefiles   If you re running into this kind of thing with a pristine  official tarball of the program from its developers  then complain  It should just unpack    configure and make without you having to patch anything or install any Automake or Autoconf materials   Ideally  a pull of their Git head should also behave that way

User · Answer

I think the touch command is the right answer e g  do something like  touch --date   date   aclocal m4 Makefile am configure Makefile in   before    configure  amp  amp  make    Sidebar I   Otherwise  I agree with  kaz   adding dependencies for aclocal m4 and or configure and or Makefile am and or Makefile in makes assumptions about the target system that may be invalid   Specifically  those assumptions are  1  that all target systems have autotools    2  that all target systems have the same version of autotools  e g  automake 1 15 in this case    3  that if either  1  or  2  are not true for any user  that the user is extracting the package from a maintainer-produced TAR or ZIP format that maintains timestamps of the relevant files  in which case all autotool configure Makefile am Makefile in dependencies in the configure-generated Makefile will be satisfied before the make command is issued   The second assumption fails on many Mac systems because automake 1 14 is the  latest  for OSX  at least that is what I see in MacPorts  and apparently the same is true for brew    The third assumption fails spectacularly in a world with Github   This failure is an example of an  everyone thinks they are normative  mindset  specifically  the maintainers  who are the only class of users that should need to edit Makefile am  have now put everyone into that class   Perhaps there is an option in autowhatever that keeps these dependencies from being added to Makefile in and or Makefile   Sidebar II  Why  kaz is right    of course it is obvious  to me and other cognoscenti  to simply try a sequence of  touch  commands to fool the configure-created Makefile from re-running configure and the autotools   But that is not the point of configure  the point of configure is to ensure as many users on as many different systems as as possible can simply do    configure  amp  amp  make  and move on  most users are not interested in  shaving the yak  e g  debugging faulty assumptions of the autotools developers   Sidebar III   it could be argued that   configure  now that autotools adds these dependencies  is the wrong build tool to use with Github-distributed packages   Sidebar IV   perhaps configure-based Github repos should put the necessary touch command into their readme  e g  https   github com drbitboy Tycho2 SQLite RTree

User · Answer

A generic answer that may or not apply to this specific case   As the error message hint at  aclocal-1 15 should only be required if you modified files that were used to generate aclocal m4   If you don t modify any of those files  including configure ac  then you should not need to have aclocal-1 15   In my case  the problem was not that any of those files was modified but somehow the timestamp on configure ac was 6 minutes later compared to aclocal m4    I haven t figured out why  but a clean clone of my git repo solved the issue for me  Maybe something linked to git and how it created files in the first place   Rather than rerunning autoconf and friends  I would just try to get a clean clone and try again    It s also possible that somebody committed a change to configure ac but didn t regenerate the aclocal m4  in which case you indeed have to rerun automake and friends

User · Answer

Often  you don t need any auto  tools and the simplest solution is to simply run touch aclocal m4 configure in the relevant folder  and also run touch on Makefile am and Makefile in if they exist   This will update the timestamp of aclocal m4 and remind the system that aclocal m4 is up-to-date and doesn t need to be rebuilt  After this  it s probably best to empty your build directory and rerun configure from scratch after doing this  I run into this problem regularly  For me  the root cause is that I copy a library  e g  mpfr code for gcc  from another folder and the timestamps change   Of course  this trick isn t valid if you really do need to regenerate those files  perhaps because you have manually changed them  But hopefully the developers of the package distribute up-to-date files     And of course  if you do want to install automake and friends  then use the appropriate package-manager for your distribution     Install aclocal which comes with automake   brew install automake            for Mac apt-get install automake         for Ubuntu   Try again     configure  amp  amp  make

[c++] How to overcome "'aclocal-1.15' is missing on your system" warning?

2018, yet another solution ...

Examples related to c++

Examples related to github

Examples related to makefile

Examples related to automake