Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3B4F48CE.5060303@ece.gatech.edu>
Date:	Fri, 13 Jul 2001 15:15:26 -0400
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607 Netscape6/6.1b1
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	Jason Tishler <Jason DOT Tishler AT dothill DOT com>
CC:	shabbir AT talib DOT com, cygwin AT cygwin DOT com
Subject:	Re: rpm 4.0.2 Build Problem (was Re: Installing Berkeley DB 3.2.9)
References:	<20010713130149 DOT B402 AT dothill DOT com>

Jason Tishler wrote:

> Chuck,
> 
> On Thu, Jul 12, 2001 at 08:28:12PM -0400, Charles S. Wilson wrote:
> 
>>Jason Tishler wrote:
>>
>>>Now, if I could just get rpm 4.0.2 to build with it.  Sigh...
>>>
>>Hmm.  Well that's a bummer.
>>
> 
> It is probably some bone-headed thing that I'm doing or not doing.
> Nevertheless, Berkeley DB 3.2.9 make install does not seem to produce
> the installation structure that I have found on one of our Linux boxes.
> Do people routinely postprocess what is produced by make install?



People?  Cygwin maintainers usually don't -- "make install ; 
make-tarball" (e.g. in the case of my packages, you can see exactly what 
steps I take by looking at the Cygwin/*.README's.)

Distro maintainers (like Red Hat, Deb) -- all the time.  Take a look at 
the spec files from your "Linux boxes" db rpms.  In order to allow db3 
and db2 and db1 to coexist, I bet the RPM-builders harmonized all three 
packages, either by patching the make install process or explictly 
rearranging things using extra commands in the spec file after 'make 
install'.  Grab the db3 rpm's (or debs, whatever) and unpack using
    rpm2cpio <fn> | cpio -i --make-directories
and inspect the patches and spec file.


> Note that the current version does the same thing that your 2.7.7 did.
> 
> Unfortunately, the rpm source has hardcoded constructs such as:
> 
>     #include <db3/db.h>


Since rpm is more-or-less maintained by Red Hat, I wouldn't be surprised 
if the official rpm source code depended on the installed structure of 
the db3/db2/db1 libraries under Red Hat's "harmonization".


> I was able to workaround this problem with mkdirs and symlinks, but I did
> this after configure.  Possibly by not having the environment "correct"
> before I ran configure caused rpm to configure itself improperly.


Absolutely.  If you rearrange your directory structure between 
"configuring" and "making" stuff will definitely break.

--Chuck

P.S. Note that Michael Ring (who did some of the early porting work on db) has 

some patches for rpm-3.0.6, but I don't know if he continued working with 

rpm-4.x.y.  Michael, are you there?



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -