Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 16 Jul 2001 16:55:59 -0400 From: Jason Tishler To: "Charles S. Wilson" 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) Message-ID: <20010716165559.I614@dothill.com> Mail-Followup-To: "Charles S. Wilson" , shabbir AT talib DOT com, cygwin AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B4F48CE.5060303@ece.gatech.edu> User-Agent: Mutt/1.3.18i Organization: Dot Hill Systems Corp. Chuck, On Fri, Jul 13, 2001 at 03:15:26PM -0400, Charles S. Wilson wrote: > Jason Tishler wrote: > > 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 > > 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. I followed your advice and read the spec file from the Red Hat db 3.2.9 RPM. I used the information gleaned to post process make install to match the harmonization mentioned above. Then I reran configure on rpm. Finally, after some head banging I managed to "build" rpm. It appears that the rpm (4.0.2) package is very Linux centric. I will entertain posting a patch once I figure out the right way to correct all of the issue. I guess that it is time to learn automake. Sigh... BTW, the test suite also seems very Linux centric -- hardcoded paths, expected output such as "ld-linux.so.2", etc. Did you every try to run the test suite for your rpm 3.0.3 package? If so, what were the results? Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: 732.264.8770 x235 Dot Hill Systems Corp. Fax: 732.264.8798 82 Bethany Road, Suite 7 Email: Jason DOT Tishler AT dothill DOT com Hazlet, NJ 07730 USA WWW: http://www.dothill.com -- 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/