Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <000501c2d044$9191a4f0$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc: <cygwin AT cygwin DOT com>
References: <005b01c2cfd8$5036a800$0a1c440a AT BRAMSCHE> <000b01c2cfdb$49a9d6d0$78d96f83 AT pomello> <3E45DBEC DOT 9070005 AT ece DOT gatech DOT edu>
Subject: Re: [avail for test] libtool-devel-20030121-1
Date: Sun, 9 Feb 2003 14:07:23 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Charles Wilson wrote:
> Max Bowsher wrote:
>> This seems like a good time to mention that I ran into this problem
>> building gtk+ (or glib), I forget. It wanted -luuid, but -luuid is a
>> static archive, which libtool doesn't currently like. I had to hack
>> libtool as Ralf mentions above to get it to work.
>
> ARGH.  That defeats the whole purpose of the *POLICY* change in
>   libtool. I do NOT want to be in the business of supporting a forked
> version of
> libtool that disagrees with mainline on a *fundamental* policy issue.
>
> ** you can't build shared libraries that depend on static libraries,
> when using a "modern" libtool (e.g. HEAD CVS, pre-1.5) **

Nor would I expect you to. However, I might try to change the mainline's
mind on this at some point, once I've studied the issue more thoughroughly.

> If you have a problem with the policy, the place to fix it is NOT to
> hack up libtool.  Instead, get shared versions of your dependencies.

Even when making a library shared is 10 parts overhead for 1 part
usefulness? It's not libtool's place to force platforms to change. However,
neither is it the libtool mainline maintainer's place to go out and write
code to deal with every little foible of every platform.

I will research the policy descision in the libtool ML archives, and see if
I can come up with a good solution.



Max.


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