| Summary: | vim.eclass's unmatched useflags of perl and libperl message is outdated | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marco Napetti <marco.napetti> |
| Component: | Current packages | Assignee: | Vim Maintainers <vim> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | LMSSUETZEGJC, perl |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Error log | ||
|
Description
Marco Napetti
2011-08-12 21:56:29 UTC
[ebuild R ] sys-devel/libperl-5.10.1 0 kB [ebuild R ~] dev-lang/perl-5.12.4-r1 USE="berkdb doc gdbm ithreads -build -debug" 0 kB [ebuild R ~] app-editors/vim-7.3.219 USE="X acl bash-completion cscope gpm nls perl python ruby vim-pager -debug -minimal" 0 kB From this "report" it's hard to tell what your problem is, but somehow I suspect it's INVALID. Created attachment 283099 [details]
Error log
Exactly the same error as the original poster's. I think the error message can be very misleading.
(In reply to comment #2) > Exactly the same error as the original poster's. I think the error message can > be very misleading. How do you know ? Any psi powers you posses ? Seriously though, if that's the message, there's already a bug about it. IIRC, perl-5.12.4-r1, followed by rebuild of ExtUtils-ParseXS should help a bit there. vim.eclass: eerror "If the above messages seem to be talking about perl" eerror "and undefined references, please try re-emerging both" eerror "perl and libperl with the same USE flags. For more" eerror "information, see:" eerror " https://bugs.gentoo.org/show_bug.cgi?id=18129" This is only problem of <dev-lang/perl-5.10. Since 5.10 libperl and perl are installed by dev-lang/perl. You can drop this message. Marco, if your problem is the "Undefined subroutine &ExtUtils::ParseXS::errors called at..." then go to bug #378107. The eclass isn't used for recent versions anymore and the message isn't in newer ebuilds. *** Bug 423137 has been marked as a duplicate of this bug. *** |
