[ntp:questions] Unexpected executable locations from "sudo make install" on RPi Linux

Rob nomail at example.com
Sat Nov 16 11:58:44 UTC 2013

David Taylor <david-taylor at blueyonder.co.uk.invalid> wrote:
> I'm going to try an upgrade on the 3.2.27+ RPi to 3.6.11 and see what 
> changes.  I was surprised that using the same NTP source, using the same 
> "sudo make install" command, put binary files which I had just compiled 
> using make in different locations.  I had hoped that NTP might be 
> consistent, but presumably if the underlying OS differs the results from 
> "make install" will differ.

Merely upgrading the kernel from 3.2.27 to 3.6.11 will not cause such
a change.  However, it is always risky to do so because there may be
dependencies between the kernel and other parts of the system, like

So what people usually do is use "apt-get upgrade" to perform such an
update, and of course it may change a lot of other things.

Installation locations are normally determined by "configure" scripts
that are part of downloaded packages, and use very complicated mechanisms
to determine the best installation location for programs.  They can
also be directed using options to the "configure" script.  Finally
a Makefile is written that normally is quite static.  I would not
expect a "make install" to install to a different location when the
system is changed and "./configure" has not been run again, but
who knows...

More information about the questions mailing list