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: Wed, 11 Jul 2001 17:48:22 -0400 From: Jason Tishler To: "Charles S. Wilson" Cc: Steve Jorgensen , "cygwin AT cygwin. Com (E-mail)" Subject: Re: initdb failure - postgres hangs with 100% CPU Message-ID: <20010711174822.E453@dothill.com> Mail-Followup-To: "Charles S. Wilson" , Steve Jorgensen , "cygwin AT cygwin. Com (E-mail)" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B4CB903.9010807@ece.gatech.edu> User-Agent: Mutt/1.3.18i Organization: Dot Hill Systems Corp. Chuck, On Wed, Jul 11, 2001 at 04:37:23PM -0400, Charles S. Wilson wrote: > Jason, I recommend that postgres build the import library with a > ".dll.a" extention, rather than ".a". This requires no changes when > linking client code; ld will interpret "-lpq" to mean "libpq.dll.a" > FIRST, and then later look for "libpq.a" iff .dll.a is not found. > > What you're doing now is fine; it works now and will continue to work -- > but convention sez ".a" = static lib, ".dll.a" = import lib. (yah, I > know that the mswindows import libs in the cygwin and mingw packages use > ".a" ....) Unfortunately, your proposed change would affect PostgreSQL's global Makefile.shlib makefile which in turn would "affect" the building of shared libraries on all of the umpteen supported platforms. Sorry, but I don't really want to go there since I assume it will be an uphill battle. Besides, don't you want pq.dll renamed cygpq.dll, etc. too? 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/