Summary: | perl-core/DB_File-1.815 undefined symbol error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Whit Blauvelt <whit> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Whit Blauvelt
2007-10-24 01:56:07 UTC
Re-emerge sys-libs/db, then recompile perl-core/DB_File and try again. That got rid of the symbol error. Instead mimedefang-milter's slaves would fail with a sig 11. Reinstalling mimedefang-2.57 stopped those segfaults, but now it fails with: Oct 24 10:32:45 xxxx mimedefang[10078]: MIMEDefang-2.57: st_optionneg[-1227437168]: 0xff does not fulfill action requirements 0x804cf90 Oct 24 10:32:45 xxxx sm-mta[10294]: l9OEWjPR010294: milter_sys_read(mimedefang): cmd read returned 0, expecting 5 Oct 24 10:32:45 xxxx sm-mta[10294]: l9OEWjPR010294: Milter (mimedefang): to error state There's seems to be a couple of layers of trouble here - the sys-libs/db needing the recompile, and now something with mimedefang. I'll try recompiling mimedefang-2.63 next, to see if something's been fixed since 2.57 that pertains here. If that's the case, should I rename this to a mimedefang bug, or file a new one? No joy. Hand-built 2.63's slaves segfault (while the ebuild version of 2.57 have the other problem I just noted). So how can the source of the problem be narrowed down farther? Unrelated, please file a *new* bug. |