Bug 90264
Summary: | krb4 support not linked | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jack Neely <jjneely> |
Component: | fetchmail | Assignee: | Miloslav Trmač <mitr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-06-06 23:10:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jack Neely
2003-05-06 03:22:48 UTC
I'm seeing the same thing, using a fetchmailrc which worked perfectly in Red Hat 8.0 and earlier. fetchmail-6.2.0-krb5-config.patch doesn't seem to include the right magic to get the krb4 stuff linked in. Building without it and specifying where the kerberos install is gets a fetchmail build with krb4 support. I'm sorry for the late response. Apparently krb4 support is correctly linked in in current releases, e.g. fetchmail-6.2.5-7. |