[Bug 5338] spamc manpage not generated correctly on OpenBSD platform

[bu...@bugzilla.spamassassin.org]

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5338





------- Additional Comments From jm@jmason.org  2007-03-15 06:44 -------
when you run "make install", does 'blib/man1/spamc.1p' get generated?

If it does, does it look valid when you run "nroff -man 'blib/man1/spamc.1p'"?

This file should be generated during hte "make install" process; if it's not
being generated, I think it's more likely an ExtUtils::MakeMaker bug on OpenBSD
for some reason.

possibly, pod2man behaves differently if you run it from the "spamc" dir instead
of the top level, or maybe the command it's running on OpenBSD generates bad
output.  for what it's worth, here's what it runs on linux:


/usr/bin/perl "-MExtUtils::Command::MM" -e pod2man "--" --section=1p --perm_rw=644\
          sa-compile blib/man1/sa-compile.1p \
          lib/spamassassin-run.pod blib/man1/spamassassin-run.1p \
          sa-learn blib/man1/sa-learn.1p \
          spamassassin blib/man1/spamassassin.1p \
          spamd/spamd blib/man1/spamd.1p \
          spamc/spamc.pod blib/man1/spamc.1p \
          sa-update blib/man1/sa-update.1p

an abbreviated form that produces the same output (except for the timestamp) is:

perl "-MExtUtils::Command::MM" -e pod2man "--" --section=1p --perm_rw=644
spamc/spamc.pod o

I'd be curious to hear if that command's output differs from what is normally
installed as /usr/local/man/man1/spamc.1, too.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.