cmake-follow "sudo make install" does not produce executable binary

Bugzilla Link	1188
Created on	Jan 16, 2017 20:46
Version	svn
OS	Linux
Architecture	PC

Extended Description

See Bug #1184 for background on this.
The cmake-follow "sudo make install" script does not update the
exectable sac2c (etc.) binary in /usr/local/bin (or wherever
it is supposed to be). I consider this to be wrong, because
the "standard" method of installing applications is generally
something like:
  ./configure
  make 
  sudo make install
After these steps, you have a working app.
The current sac2c approach does not do this. Hence, newcomers
to SAC will likely be confused. The current sac2c approach
appears to cater, instead, to people doing compiler development
under a particular workflow.
I recommend that "sudo make install" operate in such a way
as to minimize confusion for The Great Unwashed, by ensuring
that updated sac2c/sac2c_d,sac2c_r... appear in /usr/local/bin.
If developers want some other behavior, e.g., so as to be able to
execute back levels of the compiler, then we might have a
"sudo make developerinstall" or similar target.