Message-ID: <4A7F44BF.8020105@gmail.com>
Date: Sun, 09 Aug 2009 22:50:55 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: How to install-libLTLIBRARIES dll to bin?
References: <6910a60907272310q54f29289l454117aff82afd5a@mail.gmail.com> <4A6ED94B.8020003@gmail.com> <4A7E725C.8010706@users.sourceforge.net> <4A7ED3C9.70700@cwilson.fastmail.fm> <4A7F03EA.9030101@gmail.com> <4A7F2C02.80409@cwilson.fastmail.fm> <4A7F30FC.7030506@gmail.com> <4A7F3DAE.7010103@users.sourceforge.net>
In-Reply-To: <4A7F3DAE.7010103@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Yaakov (Cygwin/X) wrote:
> The assumption that $bindir is $libdir/../bin has been there for some
> time; anyone using a nonconformant --bindir= is on their own anyway
> regardless of this patch.

  The assumption is in libtool, not in autoconf, nor in configure, nor in the
Gnu Coding Standards, and it is an invalid assumption(*).  It is *libtool* that
fails to conform, by assuming that $bindir will always and only ever have the
/default/ value that is assigned by configure when the user does not specify
their own choice of setting.

  Why on earth would the --bindir= option even exist if there was no valid way
of ever using it?

    cheers,
      DaveK
-- 
(*) - or rather, it is not an assumption at all; it is, as I previously
explained, a fallible heuristic.


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