-   Gentoo (
-   -   ebuild errors (

milomak 06-15-2009 08:43 PM

ebuild errors
I've been using Gentoo for some time now. But I realise when I meet up with an ebuild error, the only thing I know to do is post it on a forum.

What should I look to, to be able to fix the problems myself?

d2_racing 06-15-2009 10:31 PM

Hi, first, you check with google if someone has the error.

Also, you can go to and search for the name of the package that is crashing.

50% of the time, you can solve the problem with google and the bugzilla site and for the rest, you ask for help and that's pretty fine, because I'm sure that a lot of people can have the same problem as your.

mbostwick 06-18-2009 01:52 AM

Also you can check the irc. Anther possible choice is to install one version back.

i92guboj 06-18-2009 06:49 AM

The first thing if you want to solve it yourself is to be able to read and understand the output.

When an ebuild fails there are at least two parts that you must be able to separate. Those are the compiler output and the portage one. It's very important to read the messages and identify where the error comes from. Once done that, then it just takes time and experience to be able to identify the ultimate cause of the problem. But sometimes it can get really tricky.

shuuhen 06-26-2009 12:48 AM

The statements above about learning how to read the output and to search and Google will help you fix many problems. Also, the revdep-rebuild utility helps when a new revision of something requires rebuilding dependencies (part of the gentoolkit package). If you're stuck after that, you'll probably need to ask.

Here's an example. I was putting off updates because I was too busy to do much more than check my email and some of the updates were going from tetex to texlive and a new pcre version. The tetex to texlive upgrade requires rebuilding programs like kile and pcre is just a dependency that happened to have a newer version available.


libtool: link: cannot find the library `/usr/lib64/'
make[4]: *** [kile] Error 1
make[4]: Leaving directory `/var/tmp/portage/app-editors/kile-2.0.3-r1/work/kile-2.0.3/src/kile'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/app-editors/kile-2.0.3-r1/work/kile-2.0.3/src/kile'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/app-editors/kile-2.0.3-r1/work/kile-2.0.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-editors/kile-2.0.3-r1/work/kile-2.0.3'
make: *** [all] Error 2

Most of that make stuff isn't relevant (for this purpose anyway). What we care about is the libtool line. A quick Google search for "cannot find the library" (the bold part, quotes included) would probably get you helpful results. However, the output from emerge (Portage messages, not build messages) after the pcre update says pcre no longer installs .la files and to install dev-util/lafilefixer and run it with the --justfixit argument.

In other cases Portage messages will say something useful like a USE flag should be enabled or disabled. The Portage output will have asterisks to the left of the messages. There can be other cases as well, but this is common stuff. I like to send the output from emerge -uvp to a file before an update so I have a reference of what was updated and what versions were involved.

All times are GMT -5. The time now is 03:54 PM.