DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=L08s22NaKkhZ6CWi+EHNjnFQxpHxNQn5/Eqrgent47g
	JSM+X7D7NkcKkG6XIJY+gS9MFf1M0nHDWa6BxDYFyvVsWPI+oxuMv23ZzSMMgrif
	q+G4wEY6NUHNWNX5YOvjjbwCJX/p0f3yojIXNnAksEPsCfJj7OcURfAPug8WQR6E
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51B98EB9.3020407@users.sourceforge.net>
Date: Thu, 13 Jun 2013 04:19:53 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: postgresql: libpq.a not an import library
References: <51B0E34A.5010801@users.sourceforge.net> <51B0E93B.9030806@gmail.com> <51B16F2D.7010500@users.sourceforge.net> <51B32B26.7050006@gmail.com> <51B97E1B.3060801@gmail.com>
In-Reply-To: <51B97E1B.3060801@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2013-06-13 03:08, Danjel McGougan wrote:
> It seems the latest libpq5 (9.2.4-2) installs /bin/cygpq-5.dll, but at
> least xemacs fails to find this lib (it looks for cygpq.dll) and fails
> to load. Downgrading libpq5 to 8.2.11-1 solves the xemacs issue for me.

Marco,

While I'm glad to finally have properly versioned PostgreSQL DLLs, we do 
need to worry about not breaking everything in the distro (and Ports) 
which is linked against the old, unversioned cygpq.dll.

I suggest renaming the old libpq5-8.x packages on sourceware to libpq, 
and changing all libpq5 deps in the distro to libpq, namely for:

algol68g
clisp
libQtSql4
libsasl2-sql
odbc-psql
xemacs

Can you take care of this, or shall I?

> Before I downgraded I tried to symlink cygpq.dll to cygpq-5.dll, but this
> caused xemacs to silently fail to start.

The Windows runtime linker doesn't understand symlinks, so that wouldn't 
have worked.


Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple