"Ian D. Stewart" <[EMAIL PROTECTED]> writes:
> I've noticed that when running autoheader for the first time on CVS
> source, you receive an error message "mv: cannot move 'autoh8323' to
> 'include/config.h.in': no such file or directory".
>
> I would like to write a patch to fix this, but am wondering what be the
> "more correct" approach: to test for 'include', and then create it if it
> doesn't exist, something like:
>
> if [ ! test -d include ]; then mkdir include
>
> or to use 'mkdir -p', which, as I understand it, creates a directory if
> it doesn't exist and does nothing if it does.
>
Maybe we should just add an empty include directory to CVS? Changing
autoheader to essentially ignore this error (by creating the specified
directories first) may be worse than the alternative.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
