| Summary: | Perl 5.8.1 and XML-SAX fails to install ParserDetails.ini | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Shaun Guth <l8nite> |
| Component: | [OLD] Development | Assignee: | Gentoo Perl team <perl> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | acooks, liquidx |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | xml-sax-0.12 merge log | ||
|
Description
Shaun Guth
2003-10-08 16:14:27 UTC
Which perl ebuild was this? Is it still a problem? After install XML::SAX from portage I see this warning in apache log could not find ParserDetails.ini in /usr/lib/perl5/site_perl/5.8.3/XML/SAX is normal ? maybe need add to ebuild default ParserDetails.ini ? root@work portage # emerge -pv perl XML-SAX These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-lang/perl-5.8.3 +berkdb -doc +gdbm +threads 11,721 kB [ebuild R ] dev-perl/XML-SAX-0.12 0 kB XML-SAX comes with a ParserDetails.ini file already. [[[root@enki]]] qpkg -f /usr/lib/perl5/site_perl/5.8.0/XML/SAX/ParserDetails.ini dev-perl/XML-SAX * Granted, the ebuild for XML-SAX looks like it could use some tweaking for Gentoo purposes, but the file is created. Downgrading from blocker as this does not prevent the installation of the OS. Please reopen if after reading the comments you still aren't working. No comment in over a month and half (aside from devs), closing. I seem to be getting the same problem, where XML-SAX (0.12) doesn't actually include ParserDetails.ini. This is both on ~x86 and ~ppc using perl-5.8.3. Portage 2.0.50-r2 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.6.1-mm2) ================================================================= System uname: 2.6.1-mm2 i686 Celeron (Mendocino) Gentoo Base System version 1.4.3.13 distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [disabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium2 -Os -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"CONFIG_PROTECT_MASK="/etc/X11/starthere /etc/fenris /etc/gconf /etc/postfix/sample /etc/sound/events /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium2 -Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg cvs digest distcc noauto sandbox" GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage.local/liquidx /usr/portage.local/user" SYNC="rsync://potato.vegetable.org.uk/gentoo-portage" USE="X aalib alsa apm avi berkdb bluetooth bonobo cjk crypt cups curl encode esd foomaticdb gdbm geoip gif gnome gnomedb gphoto2 gpm gtk gtk2 gtkhtml guile imlib jabber jpeg ldap libg++ libwww mad mmx motif mozilla moznocompose moznoirc moznomail mozsvg mpeg msn mysql ncurses nls nptl oggvorbis opengl oscar oss pam pda pdflib png pnp postgres python quicktime readline real sdl slang spell ssl tcltk tcpd tetex truetype trusted x86 xml2 xmms xv yahoo zlib" Created attachment 28121 [details]
xml-sax-0.12 merge log
I confirm this bug with sys-devel/libperl-5.8.2 and dev-perl/XML-SAX-0.12. Here is my nasty work-around: emerge -C XML-SAX perl -MCPAN -e 'install XML::SAX' emerge XML-SAX Ugly and stupid, but it does result in a working XML::SAX. I looked at the XML-SAX-0.12.ebuild, but nothing seems amiss. I wonder if the src_install() function that is inherited from perl-module.eclass is the real culprit? OK, emerge sync and give it a whirl. Re-evaluating the Makefile.PL for this one, it appears to have changed directions in the pre-formatted questions it asks during building, but the ebuild never reflected this change. The modified ebuild is in place and should be available as you read this. Let us know if this can be closed out now Re-closing after no comment from a month ago. |