Bug 12248 – minor Makefile.in changes to get rpm-4.0-0.33 to compile

Bug 12248 - minor Makefile.in changes to get rpm-4.0-0.33 to compile

Summary:	minor Makefile.in changes to get rpm-4.0-0.33 to compile

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	rpm (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-06-14 05:40 EDT by Jonathan Kamens
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-06-14 05:41:15 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Makefile patches (1.18 KB, patch) 2000-06-14 05:41 EDT, Jonathan Kamens	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jonathan Kamens 2000-06-14 05:40:15 EDT

I kept getting "/usr/bin/ld: cannot find -lrpm" when trying to build rpm
from rpm-4.0-0.33.src.rpm.  I don't really understand why, but I had to
make the attached changes to make rpm build properly.

Comment 1 Jonathan Kamens 2000-06-14 05:41:14 EDT

Created attachment 458 [details]
Makefile patches

Comment 2 Jeff Johnson 2000-06-14 09:11:36 EDT

I believe this is fixed in CVS. I've been feuding with libtool to get
library dependencies correct, and believe that I have a working config now.

Comment 3 SB 2000-06-15 16:04:21 EDT

How do I install the newest rpm package and the rawhide package when they are 
all in 4.0 format and I only have rpm-3.1?  In order to build rpm from the cvs 
tree I need to upgrade my libtool, and that too is in 4.0 format...any help 
here?

-Stan Bubrouski

Note You need to log in before you can comment on or make changes to this bug.