Re: cannot create directory `.am15097': Permission denied

[Bruce Korb]

Hi guys,

Wrong again.  It seems I am back to a dilemma I thought I had
kludged around a few years ago:  My doc depends upon the project
binaries because their usage text gets incorporated into it.
The texinfo macros were written with the presumption that the
.texi files are static, hand written things that must pre-exist
or else you must not have any documentation.  Completely bogus,
of course.  Anyway, to fool the foolish macros, I have to call
a file "autogen.texi" even though it is actually not that, but
a predecessor file used to create the real "autogen.texi".  That
bogus trickery has come back to bite.  I hate it.  Is there any
way to fix the texinfo automake macros so that they do not have
to make bogus assumptions about non-existence of documentation?
Please?  I have actually solved my problem by making the
distcheck source directories writable.  Not at all kosher, but
distcheck now passes.  Any thoughts or helps at all would be
sincerely appreciated.

Regards, Bruce

P.S. a couple of fix possibilities:

1) change the texi macros to create its products in the builddir
   instead of the srcdir

2) change the texi macros so that they would still incorporate
   themselves into the Makefile.in, even if they cannot seem to
   locate any .texi files at automake time.

3) create new texi macros going by new names that do these things.

Anything else at all that will let me glue together the docs
after binaries are built and before "make check" does its thing.

On Saturday 09 July 2005 02:44 pm, Bruce Korb wrote:
> It was the macros going into the *source* directory in order to
> build its products.  Bad.  But anyway, the cause was a minor
> misordering of build functions.  Thank you.  :)
> 
> On Saturday 09 July 2005 02:26 pm, Bruce Korb wrote:
> > Hi,
> > 
> > I am sure that this is some config issue, but Google gives no help
> > on this one.  "make" and "make check" are all happy, but when I
> > get to "make distcheck" it dies in the doc directory doing strange
> > things that I cannot even speculate about.
> > 
> > 
> > make[2]: Entering directory `/home/bkorb/ag/ag/autogen-5.7.1/_build/doc'
> > restore=: && backupdir=".am$$" && \
> > am__cwd=`pwd` && cd ../../doc && \
> > rm -rf $backupdir && mkdir $backupdir && \
> > for f in autogen.info autogen.info-[0-9] autogen.info-[0-9][0-9] \
> >    autogen.i[0-9] autogen.i[0-9][0-9]; do \
> >   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> > done; \
> > cd "$am__cwd"; \
> > if /bin/sh /home/bkorb/ag/ag/autogen-5.7.1/_build/config/missing \
> >    --run makeinfo-I../../autoopts -I../autoopts -I ../../doc \
> >  -o autogen.info autogen.texi; \
> > then \
> >   rc=0; \
> >   cd ../../doc; \
> > else \
> >   rc=$?; \
> >   cd ../../doc && \
> >   $restore $backupdir/* `echo "./autogen.info" | sed 's|[^/]*$||'`; \
> > fi; \
> > rm -rf $backupdir; exit $rc
> > mkdir: cannot create directory `.am15097': Permission denied
> > autogen.info: Permission denied
> > make[2]: *** [autogen.info] Error 1
> > make[2]: Leaving directory `/home/bkorb/ag/ag/autogen-5.7.1/_build/doc'
> > make[1]: *** [check-recursive] Error 1
> > 
> > 
> > So, it looks like it was trying to create a backup directory named,
> > ".am15097" but it could not.  However:
> > 
> > $ ls -dog /home/bkorb/ag/ag/autogen-5.7.1/_build/doc
> > drwxr-xr-x  2 845 Jul  9 14:13 /home/bkorb/ag/ag/autogen-5.7.1/_build/doc
> > 
> > it looks like it has permission to me.  What's going on?  :)