Summary: | DBD-mysql-3.0004 fails to emerge on AMD64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthew Schultz <mattsch> |
Component: | New packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matthew Schultz
2006-08-09 15:52:37 UTC
re-emerge module-build and try again module-build is not emerged on my system. Does DBD-Mysql depend on it because when I go to emerge DBD-Mysql, it does not bring up a module-build dependency? I got this error after I emerged module-build 0.28 and tried to emerge DBD-mysql again:
>>> Emerging (1 of 1) dev-perl/DBD-mysql-3.0004 to /
>>> checking ebuild checksums ;-)
>>> checking auxfile checksums ;-)
>>> checking miscfile checksums ;-)
>>> checking DBD-mysql-3.0004.tar.gz ;-)
>>> Unpacking source...
>>> Unpacking DBD-mysql-3.0004.tar.gz to /var/tmp/portage/DBD-mysql-3.0004/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/DBD-mysql-3.0004/work/DBD-mysql-3.0004 ...
* Using ExtUtils::MakeMaker
Can't locate DBI/DBD.pm in @INC (@INC contains: /etc/perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.8 /usr/lib64/perl5/vendor_perl/5.8.7 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/5.8.8 /usr/local/lib/site_perl .) at Makefile.PL line 23.
!!! ERROR: dev-perl/DBD-mysql-3.0004 failed.
Call stack:
ebuild.sh, line 1539: Called dyn_compile
ebuild.sh, line 939: Called src_compile
ebuild.sh, line 1248: Called perl-module_src_compile
perl-module.eclass, line 125: Called perl-module_src_prep
perl-module.eclass, line 114: Called die
!!! Unable to build! (are you using USE="build"?)
!!! If you need support, post the topmost build error, and the call stack if relevant.
Reopening as the suggestion did not solve the problem. Can I have the output of `perldoc -l DBI` ? Looks like DBI's not in your @INC, which is weird. I tried perldoc -l DBI and it output that there wasn't any documentation for DBI. Then I decided to reemerge DBI-1.50 and and then emerged DBD-mysql again and this time it emerged. Not sure why you were asked to emerge module-build, clearly doesn't use it: * Using ExtUtils::MakeMaker (it's why i added that fluff to the eclass ;) Was part of your upgrade and upgrade of perl perhaps? If so, a short run of perl-cleaner should catch any modules hanging around form your pre-5.8.8 install (DBI is certainly a dep, and this has all the hallmarks of being the result of a perl upgrade). You're right. I reemerged perl a little while ago because it was complaining about not being compiled as multi-threaded as I have everything set as multi-threaded. That must have resulted in breaking DBI. Closing. Note: please run perl-cleaner after recompiling perl ;) Matthew, if you did run perl-cleaner and DBI was still b0rked, reopen or file a new bug. Thanks Reemerging DBI worked. I didn't have to run perl-cleaner to emerge DBD-mysql, but I ran it anyway just in case. Thanks for the help! |