Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 13 Jul 2001 13:01:49 -0400 From: Jason Tishler To: "Charles S. Wilson" Cc: shabbir@talib.com, cygwin@cygwin.com Subject: rpm 4.0.2 Build Problem (was Re: Installing Berkeley DB 3.2.9) Message-ID: <20010713130149.B402@dothill.com> Mail-Followup-To: "Charles S. Wilson" , shabbir@talib.com, cygwin@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B4E409C.2040304@ece.gatech.edu> User-Agent: Mutt/1.3.18i Organization: Dot Hill Systems Corp. 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? 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 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. 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.Tishler@dothill.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/