At 6:28 AM -0500 11/13/02, Michael G Schwern wrote:
>Ok, I just tore the guts out of MakeMaker's manifypods. All the platform
>specific code is gone. Want to download the snapshot from makemaker.org and
>see if "make manifypods" generates man pages on VMS?
For starters you need this:
--- lib/ExtUtils/MM_Any.pm;-0 Wed Nov 13 05:16:34 2002
+++ lib/ExtUtils/MM_Any.pm Thu Nov 14 13:50:49 2002
@@ -184,8 +184,8 @@
return <<END_OF_TARGET;
manifypods : pure_all $dependencies
- \$(NOECHO)\$(POD2MAN_EXE) --section=1 --perm_rw=\$(PERM_RW) $man1pods
- \$(NOECHO)\$(POD2MAN_EXE) --section=3 --perm_rw=\$(PERM_RW) $man3pods
+ \$(NOECHO) \$(POD2MAN_EXE) --section=1 --perm_rw=\$(PERM_RW) $man1pods
+ \$(NOECHO) \$(POD2MAN_EXE) --section=3 --perm_rw=\$(PERM_RW) $man3pods
END_OF_TARGET
}
[end of patch]
If you don't have a space after the '@' then the VMS make utilities pass it to the
shell where it means "take the next token and run it as a command procedure". After
fixing that, pod2man complains that --perm_rw must have an argument and spews
something that I suppose is a document in man page format to the terminal and then
hangs. The PERM_RW macro is not defined but I haven't had time to track down why; is
this something new or has it just never been used before? That's while it's creating
section 1. It never gets to section 3 but I guarantee that a single command that goes
on for 30 lines or so will exceed the command buffer limits.
As a side note, the PPD target has never been fixed per the patch I sent in at RT #
1550.
--
________________________________________
Craig A. Berry
mailto:craigberry@;mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
