[Octave-bug-tracker] [bug #47832] build fails with read-only source tree when generating DOCSTRINGS

[John W. Eaton]

Follow-up Comment #8, bug #47832 (project octave):

Can the rule be rewritten so that it puts the temporary file in the build
tree?  That should fix the problem if there really is no change in the
generated DOCSTRINGS file because the move-if-change script will just delete
the tmp file if it is the same as the DOCSTRINGS file from the tarball.

There is no hope of making this work correctly if there is something that
requires building the docs because the rules that automake generates will
write to the source tree.

And, as I said, I tried the automake option to place the info files in the
build tree, but that fails for some other reason that I can't remember
exactly, but I think it still tries to write something in the source tree (tmp
directory when running makeinfo?).


    _______________________________________________________

Reply to this item at:

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

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