Re: [mpich-discuss] man mpich-3.0.4
Thanks. That fixed my problem. Ideally, the information provided here would be added to the documentation or some automation for TEXTFILTER_PATH and DOCTEXT_PATH added so that future users wouldn't have these issues. However, I recognize that the counter argument of "if you're pulling the git repo, you should be able to read the source and figure it out, hence need no documentation" has some validity. I would certainly make this argument before doing the associated work if I were an MPICH developer :-) I got 818KB of warnings/errors like the following but it doesn't seem to have any impact on the results. DOCTEXTMAN mpi-io/write_sh.man-phony Did not find definition for command section Did not find definition for command end_par Did not find definition for command section Did not find definition for command end_par Did not find definition for command section Did not find definition for command tt Did not find definition for command rm Did not find definition for command tt Did not find definition for command rm Did not find definition for command tt Did not find definition for command rm Did not find definition for command tt Did not find definition for command rm Did not find definition for command tt Did not find definition for command rm Did not find definition for command end_par Did not find definition for command tt Did not find definition for command rm Did not find definition for command tt Did not find definition for command rm Did not find definition for command tt Did not find definition for command rm Jeff On Sun, Sep 29, 2013 at 8:38 PM, Ken Raffenetti <[email protected]> wrote:
I can't speak to why, but I had to set these 2 variables like so to make doctext happy.
TEXTFILTER_PATH=/usr/local/share/doctext DOCTEXT_PATH=/usr/local/share/doctext
Ken
----- Original Message -----
From: "Jeff Hammond" <[email protected]> To: [email protected] Sent: Sunday, September 29, 2013 8:30:09 PM Subject: Re: [mpich-discuss] man mpich-3.0.4
You're right, I downloaded the 3.1b1 tarball specifically so I could get the man pages.
However, since my doctext business is in the default path, I fail to see why it is not found, nor why setting TEXTFILTER_PATH has no effect.
Jeffs-MacBook-Pro:build-clang jhammond$ ll /usr/local/share/doctext/nroff.def -rw-r--r-- 1 root wheel 1.3K Dec 4 2012 /usr/local/share/doctext/nroff.def
Jeffs-MacBook-Pro:build-clang jhammond$ export TEXTFILTER_PATH=/usr/local Jeffs-MacBook-Pro:build-clang jhammond$ make mandoc test -d /Users/jhammond/eclipse/MPICH/git/build-clang/man/man1 || mkdir -p /Users/jhammond/eclipse/MPICH/git/build-clang/man/man1 test -d /Users/jhammond/eclipse/MPICH/git/build-clang/man/man3 || mkdir -p /Users/jhammond/eclipse/MPICH/git/build-clang/man/man3 make mandoc-local DOCTEXTMAN src/mpi/attr/attr_delete.man-phony Error: Error reading nroff.def in path .:NONE/share or TEXTFILTER_PATH environment variable:-1 make[1]: *** [src/mpi/attr/attr_delete.man-phony] Error 1 make: *** [mandoc] Error 2
Jeffs-MacBook-Pro:build-clang jhammond$ TEXTFILTER_PATH=/usr/local make mandoc test -d /Users/jhammond/eclipse/MPICH/git/build-clang/man/man1 || mkdir -p /Users/jhammond/eclipse/MPICH/git/build-clang/man/man1 test -d /Users/jhammond/eclipse/MPICH/git/build-clang/man/man3 || mkdir -p /Users/jhammond/eclipse/MPICH/git/build-clang/man/man3 make mandoc-local DOCTEXTMAN src/mpi/attr/attr_delete.man-phony Error: Error reading nroff.def in path .:NONE/share or TEXTFILTER_PATH environment variable:-1 make[1]: *** [src/mpi/attr/attr_delete.man-phony] Error 1 make: *** [mandoc] Error 2
Jeff
On Sun, Sep 29, 2013 at 6:05 PM, Ken Raffenetti <[email protected]> wrote:
I'm surprised there were man pages to be copied. Did you build from a tarball? The make target uses the doctext and sowing packages to build man pages from comments in the mpich source. If your manpages are already built, you could use "make install-man-local" to copy them in place. The configure option to change their location is --mandir.
----- Original Message -----
From: "Jeff Hammond" <[email protected]> To: [email protected] Sent: Sunday, September 29, 2013 5:42:22 PM Subject: Re: [mpich-discuss] man mpich-3.0.4
Why is any of that required? I was able to install the man pages by hand with "/bin/cp -r". Why do I need doctext for "make mandoc" to work? Shouldn't "make mandoc" just do that?
Jeff
On Sun, Sep 29, 2013 at 5:17 PM, Ken Raffenetti <[email protected]> wrote:
You need to set that environment variable relative to your doctext installation. The default location is /usr/local/share/doctext.
----- Original Message -----
From: "Jeff Hammond" <[email protected]> To: [email protected] Sent: Sunday, September 29, 2013 1:51:37 PM Subject: Re: [mpich-discuss] man mpich-3.0.4
The target is "make mandoc". And yes, if you don't specify --manpage, it'll put it in your prefix path by default. You only need to provide the additional --manpage information if you want to install it in a different location. You never have to copy it manually.
What does this mean?
Jeffs-MacBook-Pro:build-clang jhammond$ make mandoc test -d /Users/jhammond/eclipse/MPICH/git/build-clang/man/man1 || mkdir -p /Users/jhammond/eclipse/MPICH/git/build-clang/man/man1 test -d /Users/jhammond/eclipse/MPICH/git/build-clang/man/man3 || mkdir -p /Users/jhammond/eclipse/MPICH/git/build-clang/man/man3 make mandoc-local DOCTEXTMAN src/mpi/attr/attr_delete.man-phony Error: Error reading nroff.def in path .:NONE/share or TEXTFILTER_PATH environment variable:-1 make[1]: *** [src/mpi/attr/attr_delete.man-phony] Error 1 make: *** [mandoc] Error 2
Thanks,
Jeff
-- Jeff Hammond [email protected] _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
-- Jeff Hammond [email protected] _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
-- Jeff Hammond [email protected] _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
-- Jeff Hammond [email protected]
participants (1)
-
Jeff Hammond