Summary: | Compilation of db during install gives "undefined reference to `dbopen'" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tim Bates <gentoo> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.4_rc4 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tim Bates
2003-06-22 02:52:09 UTC
One reference to something possibly related to this problem that I can find on the 'net is: http://www.sleepycat.com/docs/ref/build_unix/notes.html Scroll down to the bottom, part 7. It indicates that the db-1.85 libraries have to be properly installed for this to complete. db-1.85-r1 is installed on my system, I've tried emerging it again but it doesn't seem to make any difference. During the emerge of 1.85, it gives this: patching file recno/rec_put.c patch: **** malformed patch at line 725: ! if (flags == R_SETCURSOR) This may not be relevant; perhaps it should be filed as a separate bug. I think there is something seriously wrong with my system. Earlier today it gave me a segfault while doing the "Updating Portage cache" part of `emerge sync' and just now it died during the configure of db, complaining that it couldn't find qsort, and I ran `emerge system' again straight away and that worked. Things goind randomly wrong is not a good state for a server to be in. I might try doing a memory test when I get home today, but if anyone could make some helpful suggestions in the meantime it would be appreciated. I'm not sure any more whether it's worth leaving this bug open, although it's the only thing going wrong with my system that seems to be consistently reproducible so I will. Okay, I did a memtest86 and it turns out one of my two memory sticks is faulty; a series of almost-consecutive words have their lowest bit stuck at 1. This probably causes misaligned memory reads for any addresses stored in those locations. I've removed that stick and extensively tested the other, and since then haven't had a problem. A clean installation has now gotten past compiling db, so it seems this was entirely related to the memory problems, despite the apparent reproducibility of the bug. Please close this bug report. bad memory cause this |