September 2013 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] man mpich-3.0.4
by Julio Henrique 30 Sep '13

30 Sep '13

Thank's Jeff. I configured MANPATH=/opt/mpich/share/man:$MANPATH export MANPATH in ~/.bashrc and called 'man mpicc' for man1 e 'man MPI_Barier' for man3. For the version I call 'mpirun --version' or 'mpiexec --version' Thank's again. From: jeff.science(a)gmail.com Date: Sat, 28 Sep 2013 20:19:54 -0500 To: discuss(a)mpich.org Subject: Re: [mpich-discuss] man mpich-3.0.4 I struggled with this just the other day. I could not get the build system to install the man pages despite many attempts. I gave up and just did a manual install by copying the man subdirectory of the source into my install directory. In any case, I don't know why "man mpich" should work. What would that tell you? Try "man mpicc" or "man MPI_Barrier", for example. Perhaps with "man mpich" you are looking for something like the following? > mpichversionMPICH Version: 3.1b1MPICH Release date: Thu Aug 8 10:41:27 CDT 2013 MPICH Device: ch3:nemesisMPICH configure: CC=clang CXX=clang++ FC=/bin/false --disable-fc --disable-f77 --enable-threads --enable-g --with-pm=hydra --prefix=/opt/mpich/3.1b1/clang MPICH CC: clang -g -O2MPICH CXX: clang++ -g -O2MPICH F77: no -g MPICH FC: no -g Jeff On Sat, Sep 28, 2013 at 8:13 PM, Julio Henrique <juliohenrique(a)msn.com> wrote: How do I set the MANPATH mpich-3.0.4 on Debian Wheezy? The installation location is /opt/mpich. I tried in ~/.bashrc: MANPATH = /opt/mpich/share/man:$MANPATH export MANPATH but not work. I call 'man mpich', or is not that what you call the man of mpich? I researched and not found. However, PATH=/opt/mpich/bin:$PATH export PATH worked. _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond jeff.science(a)gmail.com _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] distributing MPICH Windows binaries
by Jayesh Krishna 30 Sep '13

30 Sep '13

Please see http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can… -Jayesh ----- Original Message ----- From: "Michael Colonno" <mcolonno(a)stanford.edu> To: discuss(a)mpich.org Sent: Monday, September 30, 2013 4:13:08 PM Subject: Re: [mpich-discuss] distributing MPICH Windows binaries Make that 3.0.4 (not 3.0.2). -----Original Message----- From: discuss-bounces(a)mpich.org [mailto:[email protected]] On Behalf Of Michael Colonno Sent: Monday, September 30, 2013 2:12 PM To: discuss(a)mpich.org Subject: Re: [mpich-discuss] distributing MPICH Windows binaries Hi ~ Following up from the below, we (the SU^2 development at Stanford, an open-source CFD project) would like to distribute some of the MPICH2 1.4.1 binaries and libraries packaged in our Windows installer to simplify deployment and reduce user questions. We'd like the blessing of your team before doing so of course. On a related note, is an unofficial Windows binary of version 3.0.2 coming? If not, is it a Windows (32-bit and 64-bit) build straightforward from the source? Thanks, ~Mike C. -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Monday, September 30, 2013 9:17 AM To: Michael Colonno Subject: Re: distributing MPICH Windows binaries Hi, I don't think there should be any issues from our side. However I would recommend that you to send an email to discuss(a)mpich.org so that the other MPICH folks can also respond to your question. Regards, Jayesh ----- Original Message ----- From: "Michael Colonno" <mcolonno(a)gmail.com> To: jayesh(a)mcs.anl.gov Sent: Friday, September 27, 2013 5:57:04 PM Subject: distributing MPICH Windows binaries Hi ~ I’m contacting you on behalf the SU^2 development team at Stanford. SU^2 is an open-source CFD tool that is now widely used by the aerospace community. I’m responsible for the Windows distributions and I build the code against MPICH2 1.4.1 for parallel Windows support. We get a lot of questions from users who skip the documentation and just try to run the parallel versions without installing / configuring MPICH2 (many of them have never even heard of MPI). Hence, I’d like permission to distribute the MPICH2 for Windows installer files and / or libraries and executables with SU^2 (packaged into our installer). We feel this would simplify the installation quite a bit an probably reduce support questions for both of us. Please let me know if you have any objection or licensing issue with this. Thanks, ~Mike C. _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] distributing MPICH Windows binaries
by Michael Colonno 30 Sep '13

30 Sep '13

Make that 3.0.4 (not 3.0.2). -----Original Message----- From: discuss-bounces(a)mpich.org [mailto:[email protected]] On Behalf Of Michael Colonno Sent: Monday, September 30, 2013 2:12 PM To: discuss(a)mpich.org Subject: Re: [mpich-discuss] distributing MPICH Windows binaries Hi ~ Following up from the below, we (the SU^2 development at Stanford, an open-source CFD project) would like to distribute some of the MPICH2 1.4.1 binaries and libraries packaged in our Windows installer to simplify deployment and reduce user questions. We'd like the blessing of your team before doing so of course. On a related note, is an unofficial Windows binary of version 3.0.2 coming? If not, is it a Windows (32-bit and 64-bit) build straightforward from the source? Thanks, ~Mike C. -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Monday, September 30, 2013 9:17 AM To: Michael Colonno Subject: Re: distributing MPICH Windows binaries Hi, I don't think there should be any issues from our side. However I would recommend that you to send an email to discuss(a)mpich.org so that the other MPICH folks can also respond to your question. Regards, Jayesh ----- Original Message ----- From: "Michael Colonno" <mcolonno(a)gmail.com> To: jayesh(a)mcs.anl.gov Sent: Friday, September 27, 2013 5:57:04 PM Subject: distributing MPICH Windows binaries Hi ~ I’m contacting you on behalf the SU^2 development team at Stanford. SU^2 is an open-source CFD tool that is now widely used by the aerospace community. I’m responsible for the Windows distributions and I build the code against MPICH2 1.4.1 for parallel Windows support. We get a lot of questions from users who skip the documentation and just try to run the parallel versions without installing / configuring MPICH2 (many of them have never even heard of MPI). Hence, I’d like permission to distribute the MPICH2 for Windows installer files and / or libraries and executables with SU^2 (packaged into our installer). We feel this would simplify the installation quite a bit an probably reduce support questions for both of us. Please let me know if you have any objection or licensing issue with this. Thanks, ~Mike C. _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] distributing MPICH Windows binaries
by Michael Colonno 30 Sep '13

30 Sep '13

Hi ~ Following up from the below, we (the SU^2 development at Stanford, an open-source CFD project) would like to distribute some of the MPICH2 1.4.1 binaries and libraries packaged in our Windows installer to simplify deployment and reduce user questions. We'd like the blessing of your team before doing so of course. On a related note, is an unofficial Windows binary of version 3.0.2 coming? If not, is it a Windows (32-bit and 64-bit) build straightforward from the source? Thanks, ~Mike C. -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Monday, September 30, 2013 9:17 AM To: Michael Colonno Subject: Re: distributing MPICH Windows binaries Hi, I don't think there should be any issues from our side. However I would recommend that you to send an email to discuss(a)mpich.org so that the other MPICH folks can also respond to your question. Regards, Jayesh ----- Original Message ----- From: "Michael Colonno" <mcolonno(a)gmail.com> To: jayesh(a)mcs.anl.gov Sent: Friday, September 27, 2013 5:57:04 PM Subject: distributing MPICH Windows binaries Hi ~ I’m contacting you on behalf the SU^2 development team at Stanford. SU^2 is an open-source CFD tool that is now widely used by the aerospace community. I’m responsible for the Windows distributions and I build the code against MPICH2 1.4.1 for parallel Windows support. We get a lot of questions from users who skip the documentation and just try to run the parallel versions without installing / configuring MPICH2 (many of them have never even heard of MPI). Hence, I’d like permission to distribute the MPICH2 for Windows installer files and / or libraries and executables with SU^2 (packaged into our installer). We feel this would simplify the installation quite a bit an probably reduce support questions for both of us. Please let me know if you have any objection or licensing issue with this. Thanks, ~Mike C.

1 0

Re: [mpich-discuss] discuss Digest, Vol 11, Issue 22
by Pavan Balaji 30 Sep '13

30 Sep '13

On Sep 30, 2013, at 9:06 AM, Tabrez Ali wrote: > Thanks for the reply. What exactly is the purpose of the following files? > > hydra_pmi_proxy This is required for forwarding internal messages to the MPI processes for coordination. This is always used in conjunction with mpiexec. > hydra_nameserver This is only required when you use name publishing in dynamic processes (MPI connect/accept). Most people don't care about it. > hydra_persist This is our own persistent daemon for platforms where one is not available (e.g., ssh or slurm). There was only one platform where this was true (Windows) and we dropped support for it, so we'll likely be removing this in the future. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] discuss Digest, Vol 11, Issue 22
by Tabrez Ali 30 Sep '13

30 Sep '13

Thanks for the reply. What exactly is the purpose of the following files? hydra_pmi_proxy hydra_nameserver hydra_persist They are all in the 'bin' directory. T On 09/29/2013 08:38 PM, discuss-request(a)mpich.org wrote: > Message: 2 > Date: Sun, 29 Sep 2013 09:51:44 -0500 > From: Pavan Balaji<balaji(a)mcs.anl.gov> > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] packaging mpiexec with static binaries > Message-ID:<843D7292-950D-4528-B370-9189FF919544(a)mcs.anl.gov> > Content-Type: text/plain; charset=us-ascii > > > On Sep 29, 2013, at 9:24 AM, Tabrez Ali wrote: >> Now if I create a static binary of my code for users who find compiling from source daunting (dont ask why) then they can easily run in serial as there is no need for mpiexec but then they cant utilize the extra cores on their PCs. >> >> Is there a way to package mpiexec along with the static binary? From testing it seems that if I ship along mpiexec.hydra and hydra_pmi_proxy then it appears to work as follows: >> >> ./mpiexec.hydra -n X ./mycode >> >> But I am not sure if it is the right approach. Any tips/advice on packaging mpirun/mpiexec along (if possible) is highly appreciated. > > Depends on what all features in mpiexec you are using. Typically shipping the contents of the bin and lib directories in your install path should be sufficient, but it assumes that your customers have the same dependency libraries as you (e.g., libc). > > Alternatively, you could ask them to do an "apt-get/port/brew/yum install" of mpich on their platform. It'll either automatically build mpich on their machine or download binaries. > > http://www.mpich.org/downloads/ > > -- Pavan > > -- > Pavan Balaji > http://www.mcs.anl.gov/~balaji > > ------------------------------

1 0

Re: [mpich-discuss] man mpich-3.0.4
by Jeff Hammond 29 Sep '13

29 Sep '13

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 <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> >> To: discuss(a)mpich.org >> 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 >> <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> >> >> To: discuss(a)mpich.org >> >> 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 >> >> <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> >> >> >> To: discuss(a)mpich.org >> >> >> 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 >> >> >> jeff.science(a)gmail.com >> >> >> _______________________________________________ >> >> >> discuss mailing list discuss(a)mpich.org >> >> >> To manage subscription options or unsubscribe: >> >> >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> >> > _______________________________________________ >> >> > discuss mailing list discuss(a)mpich.org >> >> > To manage subscription options or unsubscribe: >> >> > https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> >> >> >> >> -- >> >> Jeff Hammond >> >> jeff.science(a)gmail.com >> >> _______________________________________________ >> >> discuss mailing list discuss(a)mpich.org >> >> To manage subscription options or unsubscribe: >> >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> > _______________________________________________ >> > discuss mailing list discuss(a)mpich.org >> > To manage subscription options or unsubscribe: >> > https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond jeff.science(a)gmail.com

1 0

Re: [mpich-discuss] man mpich-3.0.4
by Ken Raffenetti 29 Sep '13

29 Sep '13

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" <jeff.science(a)gmail.com> > To: discuss(a)mpich.org > 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 > <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> > >> To: discuss(a)mpich.org > >> 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 > >> <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> > >> >> To: discuss(a)mpich.org > >> >> 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 > >> >> jeff.science(a)gmail.com > >> >> _______________________________________________ > >> >> discuss mailing list discuss(a)mpich.org > >> >> To manage subscription options or unsubscribe: > >> >> https://lists.mpich.org/mailman/listinfo/discuss > >> >> > >> > _______________________________________________ > >> > discuss mailing list discuss(a)mpich.org > >> > To manage subscription options or unsubscribe: > >> > https://lists.mpich.org/mailman/listinfo/discuss > >> > >> > >> > >> -- > >> Jeff Hammond > >> jeff.science(a)gmail.com > >> _______________________________________________ > >> discuss mailing list discuss(a)mpich.org > >> To manage subscription options or unsubscribe: > >> https://lists.mpich.org/mailman/listinfo/discuss > >> > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > jeff.science(a)gmail.com > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss >

1 0

Re: [mpich-discuss] man mpich-3.0.4
by Jeff Hammond 29 Sep '13

29 Sep '13

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 <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> >> To: discuss(a)mpich.org >> 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 >> <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> >> >> To: discuss(a)mpich.org >> >> 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 >> >> jeff.science(a)gmail.com >> >> _______________________________________________ >> >> discuss mailing list discuss(a)mpich.org >> >> To manage subscription options or unsubscribe: >> >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> > _______________________________________________ >> > discuss mailing list discuss(a)mpich.org >> > To manage subscription options or unsubscribe: >> > https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond jeff.science(a)gmail.com

1 0

Re: [mpich-discuss] man mpich-3.0.4
by Ken Raffenetti 29 Sep '13

29 Sep '13

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" <jeff.science(a)gmail.com> > To: discuss(a)mpich.org > 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 > <raffenet(a)mcs.anl.gov> 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" <jeff.science(a)gmail.com> > >> To: discuss(a)mpich.org > >> 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 > >> jeff.science(a)gmail.com > >> _______________________________________________ > >> discuss mailing list discuss(a)mpich.org > >> To manage subscription options or unsubscribe: > >> https://lists.mpich.org/mailman/listinfo/discuss > >> > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > jeff.science(a)gmail.com > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss >

1 0