Emerging (1 of 1) dev-perl/DBD-mysql-4.00.7 * DBD-mysql-4.007.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking DBD-mysql-4.007.tar.gz to /var/tmp/portage/dev-perl/DBD-mysql-4.00.7/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/dev-perl/DBD-mysql-4.00.7/work/DBD-mysql-4.007 ... * Using ExtUtils::MakeMaker Can't locate DBI/DBD.pm in @INC (@INC contains: /etc/perl /usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/site_perl/5.8.8/i686-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/5.8.8/i686-linux-thread-multi /usr/lib/perl5/5.8.8 /usr/local/lib/site_perl .) at Makefile.PL line 23. * * ERROR: dev-perl/DBD-mysql-4.00.7 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2597: Called perl-module_src_compile * environment, line 2298: Called perl-module_src_prep * environment, line 2351: Called die * The specific snippet of code: * echo "$pm_echovar" | perl Makefile.PL ${myconf} INSTALLMAN3DIR='none' PREFIX=/usr INSTALLDIRS=vendor DESTDIR=${D} || die "Unable to build! (are you using USE="build"?)"; * The die message: * Unable to build! (are you using USE="build"?) Reproducible: Didn't try
Please post your `emerge --info' too.
np3, please, try to reinstall dev-perl/DBI before installing dev-perl/DBD-mysql: emerge -1 dev-perl/DBI See if it fixes the problem.
(In reply to comment #2) > np3, please, try to reinstall dev-perl/DBI before installing > dev-perl/DBD-mysql: > emerge -1 dev-perl/DBI > > See if it fixes the problem. > Fixed the problem for me...
(In reply to comment #3) > (In reply to comment #2) > > np3, please, try to reinstall dev-perl/DBI before installing > > dev-perl/DBD-mysql: > > emerge -1 dev-perl/DBI > > > > See if it fixes the problem. > > > > Fixed the problem for me... > For me as well. Thanks for the workaround.