Bug 39524
Summary: | Compilation of rpm 4.0.2 gets undefined reference to `db3Free' to 'db3New' | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mark Post <mark.post> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
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: | 2001-05-08 01:55:11 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
Mark Post
2001-05-08 01:55:07 UTC
You can't successfully compile rpm-4.0 without db3 installed, and installed as in the Red Hat spec file, with include file in /usr/include/db3 etc. The choice of db3 (and db1 in rpm-4.0.2) is not optional. Meanwhile, db1 has already been eliminated and db-3.2.9 has been added to the rpm source tree in rpm-4.0.3-0.18 (still under development). Then the ./configure script should be updated to actually _fail_ if it can't find db3, instead of continuing as it does now. Actually, it should also be updated to not even look for db1. |