Summary: | gnome-extras/gnome-power-manager-2.32.0 emerge fails {sgml?} | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Guy <defuebr> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
Guy
2010-12-26 05:29:27 UTC
Created attachment 258088 [details]
build log
Looks like somebody from gnome-power-manager made a point of making things hard in case of problems with docbook2man. Once emerge fails, go to WORKDIR/man, change 'docbook2man $? &> /dev/null' to 'docbook2man $?' in that Makefile.am, in WORKDIR run automake, then make. This way, we should get some valid output. (In reply to comment #2) > Looks like somebody from gnome-power-manager made a point of > making things hard in case of problems with docbook2man. > Once emerge fails, go to WORKDIR/man, > change 'docbook2man $? &> /dev/null' to 'docbook2man $?' in that Makefile.am, > in WORKDIR run automake, then make. > This way, we should get some valid output. > I'm not a programmer so your instructions were a bit sparse for me to understand. These results are from my best guess as to what you were asking for. Hope they help. pyrodyno ~ # cd /var/tmp/portage/gnome-extra/gnome-power-manager-2.32.0/work/gnome-power-manager-2.32.0/man pyrodyno man # ls -l total 60 -rw-r--r-- 1 root root 21669 Dec 26 12:11 Makefile -rw-r--r-- 1 root root 570 Dec 26 12:10 Makefile.am -rw-r--r-- 1 root root 15996 Dec 26 12:11 Makefile.in -rw-r--r-- 1 root root 4375 Jan 27 2010 gnome-power-manager.sgml -rw-r--r-- 1 root root 3850 Jan 27 2010 gnome-power-preferences.sgml -rw-r--r-- 1 root root 4053 Jan 27 2010 gnome-power-statistics.sgml pyrodyno man # nano -w Makefile.am pyrodyno man # automake automake-1.11: `configure.ac' or `configure.in' is required pyrodyno man # automake Makefile.in automake-1.11: no Automake input file found for `Makefile.in' automake-1.11: no input file found among supplied arguments pyrodyno man # make cd .. && /bin/sh /var/tmp/portage/gnome-extra/gnome-power-manager-2.32.0/work/gnome-power-manager-2.32.0/missing --run automake-1.11 --foreign man/Makefile cd .. && /bin/sh ./config.status man/Makefile config.status: creating man/Makefile docbook2man gnome-power-manager.sgml Using catalogs: /etc/sgml/sgml-docbook-4.1.cat Using stylesheet: /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print Working on: /var/tmp/portage/gnome-extra/gnome-power-manager-2.32.0/work/gnome-power-manager-2.32.0/man/gnome-power-manager.sgml Can't locate SGMLS/Output.pm in @INC (@INC contains: /etc/perl /usr/lib64/perl5/site_perl/5.12.2/x86_64-linux /usr/lib64/perl5/site_perl/5.12.2 /usr/lib64/perl5/vendor_perl/5.12.2/x86_64-linux /usr/lib64/perl5/vendor_perl/5.12.2 /usr/lib64/perl5/5.12.2/x86_64-linux /usr/lib64/perl5/5.12.2 /usr/lib64/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.12.1 /usr/lib64/perl5/vendor_perl /usr/local/lib/site_perl .) at /usr/bin/sgmlspl line 59. BEGIN failed--compilation aborted at /usr/bin/sgmlspl line 59. make: *** [gnome-power-manager.1] Error 8 For what it's worth ... # equery b Output.pm * Searching for Output.pm ... dev-cpp/glibmm-2.24.2-r1 (/usr/lib64/glibmm-2.4/proc/pm/Output.pm) I'm guessing there's an associated docbook package that I need to install? I did a 'locate SGMLS' and found the 'dev-perl/SGMLSpm' package. I checked to see if it was installed: # emerge -s SGMLSpm Searching... [ Results for search key : SGMLSpm ] [ Applications found : 1 ] * dev-perl/SGMLSpm Latest version available: 1.03-r6 Latest version installed: 1.03-r6 Size of files: 91 kB Homepage: http://search.cpan.org/author/DMEGG/SGMLSpm-1.03ii/ Description: Perl library for parsing the output of nsgmls License: GPL-2 I re-installed it using 'emerge SGMLSpm' 'gnome-power-manager' went to completion. Thanks for the tip regarding the editing to remove ' &> /dev/null' from Makefile.am. I've seen this type of error before with @INC and each time it invariably requires re-installing some other already installed package. I'm leaving the bug open to let you decide what to do with it and because sending error messages to /dev/null is .. not useful. Since I already have experience with @INC errors, I probably would have been able to figure this out on my own. {sigh} Any chance you've failed at a point to run perl-cleaner ? (In reply to comment #6) > Any chance you've failed at a point to run perl-cleaner ? > That's actually a good question but not for the any of the common reasons you may think. Unfortunately, the answer is "I don't know". I maintain a private network with between 6~10 pcs at any given time. When I do a round of global updates, I normally run coordinated rounds of perl-cleaner, checks for gcc/glibc upgrades, lafilefixer, revdep-rebuild and python-updater as seems appropriate. This is complicated further by the fact I have a sub group of 4 PCs where one PC is a binary packages server for the other 3. I know I ran perl-cleaner during the last major round of updates. I just don't know if the machine I just updated got processed with perl-cleaner during the prior go round. It should have been. But I can't say with certainty one way or the other. Regardless, I'll hit all the machines with perl-cleaner for sure during this round. Thank you. could you run perl-cleaner --all and tell us if gnome-power-manager build succeeds afterwards ? (In reply to comment #8) > could you run perl-cleaner --all and tell us if gnome-power-manager build > succeeds afterwards ? > I'm sorry. I wasn't clear in expressing myself in my prior comment #5. After re-emerging SGMLpm, gnome-power-manager successfully compiled. Running perl-cleaner now probably won't tell us anything. FWIW: I usually run "perl-cleaner --phall" when I run it. This time, the results were: # perl-cleaner --phall * Beginning a clean up of .ph files * Excluding files for 5.12.2 and 5.12.2/x86_64-linux from cleaning * Locating ph files for removal * Updating ph files. * Ignore all "No such file..." messages! Can't open machine/ansi.h: No such file or directory Can't open sys/_types.h: No such file or directory I interpret this to mean that everything was clean and nothing was found which required action. Ok, this was most likely due to a missing perl-cleaner run, thanks for the update. |