I'm try to install a new system (system A) where one package needs 'dev-perl/XML-LibXML' as dependency to compile. It stops with an error, because it can't find the needed files even if the portage system says 'dev-perl/XML-LibXML' is akready installed. Compared the installed file list with an older system (system B) show many files are missing: System A: * Searching for XML-LibXML in dev-perl ... * Contents of dev-perl/XML-LibXML-2.12.100: /usr /usr/share /usr/share/doc /usr/share/doc/XML-LibXML-2.12.100 /usr/share/doc/XML-LibXML-2.12.100/Changes.bz2 /usr/share/doc/XML-LibXML-2.12.100/README.bz2 /usr/share/doc/XML-LibXML-2.12.100/TODO.bz2 System B: * Searching for XML-LibXML in dev-perl ... * Contents of dev-perl/XML-LibXML-2.12.100: /usr /usr/lib64 /usr/lib64/perl5 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/vendor_perl/5.20.2 /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Attr.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/AttributeHash.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Boolean.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/CDATASection.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Comment.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Common.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Common.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/DOM.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Devel.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Document.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/DocumentFragment.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Dtd.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Element.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/ErrNo.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/ErrNo.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Error.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Error.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/InputCallback.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Literal.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Namespace.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Node.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/NodeList.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Number.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/PI.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Parser.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Pattern.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Reader.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Reader.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/RegExp.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/RelaxNG.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX/Builder.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX/Builder.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX/Generator.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/SAX/Parser.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Schema.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/Text.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/XPathContext.pm /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/XPathContext.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/XML/LibXML/XPathExpression.pod /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/auto /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/auto/XML /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/auto/XML/LibXML /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux/auto/XML/LibXML/LibXML.so /usr/share /usr/share/doc /usr/share/doc/XML-LibXML-2.12.100 /usr/share/doc/XML-LibXML-2.12.100/Changes.bz2 /usr/share/doc/XML-LibXML-2.12.100/README.bz2 /usr/share/doc/XML-LibXML-2.12.100/TODO.bz2 Try to re-install 'dev-perl/XML-LibXML' shows following warnings at end of emerge process: * Update Parser: add XML::LibXML::SAX::Parser failed * Update Parser: add XML::LibXML::SAX failed I guess it's uses 'dev-perl/XML-SAX' fot doing the job. Compared to System B the only difference in 'dev-perl/XML-SAX' is the install location. System A has installed 'dev-perl/XML-SAX' at: /usr/lib64/perl5/vendor_perl/5.20.2/XML/SAX while System B installed the package at /usr/lib64/perl5/vendor_perl/5.20.1/XML/SAX I've already run 'perl-cleaner --all' at System A, but it did not resolve the problem
Attach full build log from dev-perl/XML-LibXML build.
How do I get the buildlog, if portage claims that the package was successful installed and removes all interim files?
(In reply to Mirko Guenther from comment #2) > How do I get the buildlog, if portage claims that the package was successful > installed and removes all interim files? FEATURES=keeptemp emerge -a1 dev-perl/XML-LibXML see man make.conf
Created attachment 422228 [details] Build.log please find the build.log file as attachment
Gee, I though you didn't care... Anyway, > running xml2-config...ok (2.9.2) > Checking for ability to link against xml2...no > Checking for ability to link against libxml2...libxml2, zlib, and/or the Math library (-lm) have not been found. Doesn't really make sense. First, check cflags/libs returned by xml2-config. If that doesn't offer a clear enough hint, you might need to follow that advice about 'perl Makefile.PL', though perhaps there's already a log in the build dir showing the reason of the failure.
(In reply to Rafał Mużyło from comment #5) > Gee, I though you didn't care... > > Anyway, > > > running xml2-config...ok (2.9.2) > > Checking for ability to link against xml2...no > > Checking for ability to link against libxml2...libxml2, zlib, and/or the Math library (-lm) have not been found. > > Doesn't really make sense. > > First, check cflags/libs returned by xml2-config. > If that doesn't offer a clear enough hint, you might need to follow that > advice about 'perl Makefile.PL', though perhaps there's already a log in the > build dir showing the reason of the failure. xml2-config --cflags returns: '-I/usr/include/libxml2' xml2-config --libs returns: '-lxml2 -lz -lm -ldl' looks good for me
Well, so it's not a trivial case, or so it seems... So, as per comment 3, we need bit more than just portage logs, in this case 'keepwork' might suffice. Check the workdir then, there's likely a log file there with results of those tests. If not, follow the advice from the portage log.
Created attachment 423946 [details, diff] dump configure log I was able to find the root cause, why the configure script don't work, but I don't know why it's behaves like this. The build log is attached. As you can see the test programs can't be build because the script wants to link them against the NetworkManager library (libnm.so) The NetworkManager was installed previously on this system as dependency and was removed via 'emerge -ca' as no package claims it as dependency any more. There were also no outstanding 'emerge @redepend-rebuild' required. So in my understanding (in theory) nothing should try to use the NetworkManager any more. Since all my systems have the NetworkManager installed, I can't check, how the configure script behaves, if the NetworkManager was never installed. I guess, it will work. So, the question is, which package depends on the NetworkManager, but don't has it in the DEPEND section of it's ebuild. :/ After install the NetworkManager manually, the configure script was happy.
That sounds like a dupe of bug 552260.
(In reply to Rafał Mużyło from comment #9) > That sounds like a dupe of bug 552260. Indeed. *** This bug has been marked as a duplicate of bug 552260 ***
