Re: Irony in pod2man

Thanks for your responses. I tried installing it with the info in the link you posted and I'm still getting that pod2man error:

venus:/public_html/perl/Crypt-DES-2.03 > perl Makefile.PL PREFIX=/u/USERID/perl

Warning: I could not locate your pod2man program. Please make sure, your pod2man program is in your PATH before you execute 'make'

Writing Makefile for Crypt::DES

venus:/public_html/perl/Crypt-DES-2.03 > perl Makefile.PL PREFIX=/home/MYUSERID/public_html/perl

Warning: I could not locate your pod2man program. Please make sure, your pod2man program is in your PATH before you execute 'make'

Writing Makefile for Crypt::DES Any ideas?

Comment on Re: Irony in pod2man

Replies are listed 'Best First'.
Hand-installing pod2man by pjf (Curate) on Oct 03, 2001 at 13:54 UTC
Well, I was going to write, "They're just warnings. Go on and do a make anyway..." until I did some tests of my own, and discovered that ExtUtils::MakeMaker really really does want pod2man installed. Darn. The PREFIX affects where the modules will be installed. Obviously this needs to be a directory that actually exists. I trust you'll replace your example paths in your node above with real paths on your system. Since pod2man should be a standard part of your perl distribution, it may indicate that other essential pieces are also missing. Reinstalling perl might be a good idea.In fact, I'd go so far as to say this is probably your best option overall. If you really do need to install pod2man from scratch, you can do the following: Get the Podlators tarball, and unzip it somewhere. Make sure that the "podlators-1.10/scripts" directory from the tarball is on your path. If you're using bash and you're in the podlators directory, you can do a `export PATH="$PATH:$PWD/scripts"` to add it. make and install as per normal. (Eg, "perl Makefile.PL", "make", "make install") The installation will use the pod2man script inside the podlators distribution. You don't want to make a habit of this, but it should work. Once the code has installed, make sure that your path is set to include the location of the new pod2man script. When generating the makefile for the podlators distribution, it will complain about not finding pod2man, even though it's in your path. This can be ignored, because the generated makefile will find the pod2man in the scripts directory. Once again, do make sure that you read the Podlators README file on the risks involved of using a version which did not come with your distributon of perl. Cheers, Paul	[reply]

Replies are listed 'Best First'.

Hand-installing pod2man
by pjf (Curate) on Oct 03, 2001 at 13:54 UTC

The PREFIX affects where the modules will be installed. Obviously this needs to be a directory that actually exists. I trust you'll replace your example paths in your node above with real paths on your system.

Since pod2man should be a standard part of your perl distribution, it may indicate that other essential pieces are also missing. Reinstalling perl might be a good idea.In fact, I'd go so far as to say this is probably your best option overall.

If you really do need to install pod2man from scratch, you can do the following:

Get the Podlators tarball, and unzip it somewhere.
Make sure that the "podlators-1.10/scripts" directory from the tarball is on your path. If you're using bash and you're in the podlators directory, you can do a export PATH="$PATH:$PWD/scripts" to add it.
make and install as per normal. (Eg, "perl Makefile.PL", "make", "make install")

The installation will use the pod2man script inside the podlators distribution. You don't want to make a habit of this, but it should work.

Once the code has installed, make sure that your path is set to include the location of the new pod2man script.

When generating the makefile for the podlators distribution, it will complain about not finding pod2man, even though it's in your path. This can be ignored, because the generated makefile will find the pod2man in the scripts directory.

Once again, do make sure that you read the Podlators README file on the risks involved of using a version which did not come with your distributon of perl.

Cheers,
Paul

[reply]