[Octave-bug-tracker] [bug #46063] Build system re-makes certain files 2 or even 3 times

[John W. Eaton]

Follow-up Comment #11, bug #46063 (project octave):

Yes, the current build system tries to do the right thing if someone attempts
something like


make some_conf_var="new value"


because the configuration variables are stored in the Makefile and many are
substituted into source files.

I don't really care about changing the configuration variables on the make
command line, so simply removing the Makefile from the dependency chain
wouldn't bother me much.  But is there a reliable way we can detect this
situation and refuse to continue building?  I guess I'd like to see something
like


make some_conf_var="new value"
ERROR: The value of "some_conf_var" differs from the
ERROR: value set by configure.  You must run the
ERROR: configure script again to change this value.


The reason for making this an error rather than just a warning is that things
will not work if Octave has one value for something like "fcnfiledir" built in
to it but the Makefile used another value as the location for installing .m
files.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46063>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/