X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4A7F1317.4050800@gmail.com>
Date: Sun, 09 Aug 2009 19:19:03 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: How to install-libLTLIBRARIES dll to bin?
References: <6910a60907272310q54f29289l454117aff82afd5a AT mail DOT gmail DOT com> <4A6ED94B DOT 8020003 AT gmail DOT com> <4A7E725C DOT 8010706 AT users DOT sourceforge DOT net> <4A7ED3C9 DOT 70700 AT cwilson DOT fastmail DOT fm> <4A7F098B DOT 6030904 AT users DOT sourceforge DOT net>
In-Reply-To: <4A7F098B.6030904@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Yaakov (Cygwin/X) wrote:
> On 09/08/2009 08:48, Charles Wilson wrote:
>> Your patch does basically what Dave's horrible hack did, except his also
>> works if you're installing somewhere other than under THE libdir. His
>> patch "walks" up the directory tree from the .la file location, until it
>> finds a great-uncle ../../../bin directory.
>
> I considered such an approach, but what happens if you a prefix that
> doesn't yet exist on the system?  AFAICS you would have the library in
> $my_new_prefix/lib and the DLL in /bin, which doesn't seem quite right.

  Yep, that's exactly what happened in the libtool testsuite when I tried my
patch there, and is why I decided the whole technique wasn't suitable for upstream.

> * libffi-3.0: usually under $prefix/lib, but I move the library under
> $prefix/lib/libffi/lib so that it's not grabbed accidentally instead of
> gcc's libffi (just like the headers are by default under
> $prefix/lib/libffi/include).

  Ah, you won't have seen the recent thread.  GCC and libffi are now synced
upstream.  The version numbering is a red-herring; there were only ever minor
discrepancies between the two, it's not meant to be an API bump.  Hm, I'm not
sure how (or even if for that matter) it ended up getting resolved, will have to
check, but the upshot of it all is that we should be able to get away with just
shipping one version between us.

    cheers,
      DaveK


--
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