BRL-CAD

I'm trying to get the DocBook tool chain to work but am having
problems.  A typical error:

/usr/bin/xsltproc -nonet -xinclude -o system/mann/en/wire.fo
../../doc/docbook/resources/standard/xsl/fo/docbook.xsl
system/mann/en/wire.xml
Making portrait pages on USletter paper (8.5inx11in)
system/man3/en/Makefile.am \
	system/man5/CMakeLists.txt \
	system/man5/en/CMakeLists.txt \
	system/man5/en/Makefile.am \
	system/mann/CMakeLists.txt \
	system/mann/en/CMakeLists.txt \
	system/mann/en/Makefile.am \
	system/mann/mged_cmd_template.xml
/bin/bash: line 1: system/man3/en/Makefile.am: Permission denied
make[2]: *** [system/mann/en/wire.fo] Error 126

When I use the "-n" option to make I see some erroneous mkdir commands
(file name instead of a directory).

Is it supposed to work and I'm doing something stupid?  Or is it known
to be broken?

I'm happy to try to fix it if it's broken.

Thanks.

-Tom

P.S.  I'm using the GNU auto tools build system.

Re: [brlcad-users] DocBook problems From: Christopher Sean Morrison <brlcad@ma...> - 2011-09-13 13:53 On Sep 13, 2011, at 9:35 AM, Tom Browder wrote: > I'm trying to get the DocBook tool chain to work but am having > problems. A typical error: > > /bin/bash: line 1: system/man3/en/Makefile.am: Permission denied > make[2]: *** [system/mann/en/wire.fo] Error 126 Quite odd! > Is it supposed to work and I'm doing something stupid? Or is it known > to be broken? It's not known to be broken that I'm aware of, but then it's been several months (since before cmake migration) since I last built the pdf docs. I presume you ran configure with --enable-documentation and with 'fop' installed? It should work, but something may have changed too. > I'm happy to try to fix it if it's broken. That'd be great. ;) > P.S. I'm using the GNU auto tools build system. Might want to try the cmake build too. There's an option under advanced (if you run ccmake) that toggles generation of the PDF docs. If the failure is build system-related, then cmake may get past it. Cheers! Sean

Re: [brlcad-users] DocBook problems From: Tom Browder <tom.browder@gm...> - 2011-09-14 16:46 On Tue, Sep 13, 2011 at 08:35, Tom Browder <tom.browder@...> wrote: > I'm trying to get the DocBook tool chain to work but am having > problems. Another thing that confused me until a bit ago was the presence of some old directories that are no longer in the trunk tree. I thought svn update would take care of that, but I've had no warnings about existing dirs now deleted. -Tom

Re: [brlcad-users] DocBook problems From: brlcad <brlcad@ma...> - 2011-09-14 17:52 Attachments: Message as HTML      On Sep 14, 2011, at 12:46 PM, Tom Browder <tom.browder@...> wrote: On Tue, Sep 13, 2011 at 08:35, Tom Browder <tom.browder@...> wrote: > I'm trying to get the DocBook tool chain to work but am having > problems. Another thing that confused me until a bit ago was the presence of some old directories that are no longer in the trunk tree. I thought svn update would take care of that, but I've had no warnings about existing dirs now deleted.   If you run svn update and a directory is deleted, svn will remove all of the svn files and the directory but not if you've added any files.  Since it won't delete your files, it can't remove the directory.  The directory turd is left around for you to decide what to do with those files. After running autogen.sh and configure in the source tree, there will potentially be Makefile.in and other files scattered throughout the hierarchy that svn knows nothing about.  They're the usual culprit. 'svn status' for the win. ;) Cheers! Sean

Re: [brlcad-users] DocBook problems From: Tom Browder <tom.browder@gm...> - 2011-09-14 18:16 On Wed, Sep 14, 2011 at 12:52, brlcad <brlcad@...> wrote: > On Sep 14, 2011, at 12:46 PM, Tom Browder <tom.browder@...> wrote: ... > Another thing that confused me until a bit ago was the presence of > some old directories that are no longer in the trunk tree. I thought > svn update would take care of that, but I've had no warnings about > existing dirs now deleted. > > > If you run svn update and a directory is deleted, svn will remove all of the > svn files and the directory but not if you've added any files.  Since it > won't delete your files, it can't remove the directory.  The directory turd > is left around for you to decide what to do with those files. > After running autogen.sh and configure in the source tree, there will > potentially be Makefile.in and other files scattered throughout the > hierarchy that svn knows nothing about.  They're the usual culprit. That was probably it. > 'svn status' for the win. ;) Yep, when a working directory has been around a long time with so much activity in the repo one needs to do that at least once a year! Best regards, and thanks. -Tom

1 message has been excluded from this view by a project administrator.