Hello,
I am using all the latest packages from rawhide. When I build perl-Filter, it does not create man pages. This error is not flagged since it builds a package list dynamically based on find.
Has anyone else tried building perl-Filter when using the latest? Did you get man pages?
What is likely to be the problem with not getting man pages? I'm not terribly familiar with the perl susbsystem or packages and I'm just curious.
Thanks, -Steve Grubb
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
On Tue, 28 Sep 2004 13:51:02 -0700 (PDT), Steve G wrote:
Hello,
I am using all the latest packages from rawhide. When I build perl-Filter, it does not create man pages. This error is not flagged since it builds a package list dynamically based on find.
Has anyone else tried building perl-Filter when using the latest? Did you get man pages?
The result of an ordinary rebuild:
$ rpm -qpl perl-Filter-1.30-6.i386.rpm | grep man /usr/share/man/man3/Filter::Util::Call.3pm.gz /usr/share/man/man3/Filter::Util::Exec.3pm.gz /usr/share/man/man3/Filter::cpp.3pm.gz /usr/share/man/man3/Filter::decrypt.3pm.gz /usr/share/man/man3/Filter::exec.3pm.gz /usr/share/man/man3/Filter::sh.3pm.gz /usr/share/man/man3/Filter::tee.3pm.gz /usr/share/man/man3/perlfilter.3pm.gz
$ rpm -q perl perl-5.8.5-4
What is likely to be the problem with not getting man pages? I'm not terribly familiar with the perl susbsystem or packages and I'm just curious.
Do you see anything in the build log which refers to "manifying" man page files? They are created with pod2man from inlined documentation sections.
The result of an ordinary rebuild:
I get the same thing when I build the Filter package on my RH9 machine. So, its not the perl-Filter package that's causing my problem.
Do you see anything in the build log which refers to "manifying" man page files?
No. I did a diff between the toplevel Makefile in the Filter dir. I see the following:
- is from RH9 system + is from rawhide system
-MAKEMAKER = /usr/lib/perl5/5.8.0/ExtUtils/MakeMaker.pm -MM_VERSION = 6.03 +MAKEMAKER = /usr/lib/perl5/5.8.5/ExtUtils/MakeMaker.pm +MM_VERSION = 6.17 +MM_REVISION = 1.133 <snip> MAN1PODS = -MAN3PODS = lib/Filter/cpp.pm \ - lib/Filter/exec.pm \ - lib/Filter/sh.pm \ - perlfilter.pod -INST_MAN1DIR = blib/man1 -MAN1EXT = 1 <snip> -# .PRECIOUS: Makefile # seems to be not necessary anymore - -.PHONY: all config static dynamic test linkext manifest +MAN3PODS =
It looks like the MAN3PODS becomes empty under rawhide system. Where does this point to? MakeMaker? Are there any command line tests that can help identify the bad component?
BTW, none of my perl packages seem to be creating man pages. Filter is the simplest one to illustrate the problem.
Thanks, -Steve Grubb
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
On Tue, 28 Sep 2004 16:02:44 -0700 (PDT), Steve G wrote:
Do you see anything in the build log which refers to "manifying" man page files?
No. I did a diff between the toplevel Makefile in the Filter dir. I see the following:
- is from RH9 system
- is from rawhide system
-MAKEMAKER = /usr/lib/perl5/5.8.0/ExtUtils/MakeMaker.pm -MM_VERSION = 6.03 +MAKEMAKER = /usr/lib/perl5/5.8.5/ExtUtils/MakeMaker.pm +MM_VERSION = 6.17 +MM_REVISION = 1.133
Same Perl and MakeMaker here.
+MAN3PODS =
It looks like the MAN3PODS becomes empty under rawhide system. Where does this point to? MakeMaker? Are there any command line tests that can help identify the bad component?
Something in MakeMaker or MM_* sub-modules for sure, but maybe affected by environment variables, locale, glibc. "perl Makefile.PL verbose verbose" most likely won't reveal anything because the pod2man section of your makefile was unchanged. And "perl -d Makefile.PL" plus stepping through the code with 's' could get quite complex. There are more mighty debugging features included in Perl, such as explained in "perldoc perldebug".
BTW, none of my perl packages seem to be creating man pages. Filter is the simplest one to illustrate the problem.
Hi,
I found the problem doing a lot of diffs. It turns out that if you build perl without the man package installed, it disables the building of documentation later. I will file a bug report for a BuildRequires of man on perl.
But this also points out another problem. Packages that dynamically create file lists can be created even though many files are missing! There should be some examination of the files gathered during the install phase or this practice eliminated to spot problems quicker. From what I can see, my system built at least 15 packages with no man pages. net-snmp was the only package that caught the problem because its perl subpackage uses {_mandir}/man3/*.3pm.*. No other package complained even though stuff was missing.
Thanks for the tips...
-Steve Grubb
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail