Summary: | sys-libs/db-3.2.9-r11 configure fails - error: cannot find java include files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark Haney <mhaney> |
Component: | New packages | Assignee: | Caleb Tennis (RETIRED) <caleb> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Antonio.Pezo, clemente.aguiar, ian, pauldv, siegerstein, zeekec |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mark Haney
2008-01-23 15:26:00 UTC
Out of curiosity, what package are you installing that needs 3.2? It's kind of an abandoned version of db me thinks. (In reply to comment #1) > Out of curiosity, what package are you installing that needs 3.2? It's kind of > an abandoned version of db me thinks. > Looks to me like an update to python 2.3.6 from -r3 to r4 is the culprit. I can probably remove that db version (since I have 4.5.20_p2 installed) and re-emerge python to use the latest version. It's just odd that this update to db-3.2.9-r11 is listed like this: Calculating world dependencies... done! [ebuild NS ] sys-libs/db-3.2.9-r11 USE="java -doc -test" [ebuild U ] dev-lang/python-2.3.6-r4 [2.3.6-r3] when I emerge -upD world. I'll give the clean/re-emerge a go and see if that fixes it. *** Bug 207996 has been marked as a duplicate of this bug. *** (In reply to comment #1) > Out of curiosity, what package are you installing that needs 3.2? It's kind of > an abandoned version of db me thinks. > equery depends =sys-libs/db-3.2.9-r11 [ Searching for packages depending on =sys-libs/db-3.2.9-r11... ] app-arch/rpm-4.4.6-r4 (=sys-libs/db-3.2*) *** Bug 208163 has been marked as a duplicate of this bug. *** The configure script gets confused because it tries to find the java include files relative to the javac binary, following symlinks if necessary. A temporary workaround is to build the package without java support: echo '=sys-libs/db-3* -java' >> /etc/portage/package.use I was pretty sure I tried to emerge with '-java' but I must have been wrong. Emerging without java works just fine, but what I don't understand is why, if this is such an old version, I need it on my system. No matter what I do to remove it and reemerge all packages that used it, my system still says it needs to install it. This might be because of the way RPM works, and the way berkeley db works. Basically different versions of db have different on-disk formats. In some cases, a silent upgrade is supported, in other cases not. Rpm uses db to store its package database (which as a gentoo user you'd not likely actually use). As such to be compatible with other rpms, rpm would have the version of db locked down. This is also the reason why there are so many slots for berkeley db. I tried it out and can confirm it breaks. I'll disable the useflag in the ebuild for now. It is clearly broken with recent java's and it only builds bindings. Most users of that would use a fairly recent db. |