Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <416B0EB0.6000804@cwilson.fastmail.fm>
Date: Mon, 11 Oct 2004 18:52:32 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.4.0b
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Cc: hanwen AT xs4all DOT nl
Subject: Re: libtool bug
References: <16741 DOT 49587 DOT 333388 DOT 685699 AT byrd DOT xs4all DOT nl> <1968842951 DOT 20041008015659 AT familiehaase DOT de> <41662639 DOT 3030306 AT cwilson DOT fastmail DOT fm> <87d5zt4r3g DOT fsf AT peder DOT flower> <657467259 DOT 20041008123554 AT familiehaase DOT de> <41671F91 DOT 8020508 AT cwilson DOT fastmail DOT fm> <87ekk8qina DOT fsf AT peder DOT flower> <41687576 DOT 5000408 AT cwilson DOT fastmail DOT fm> <41687CFB DOT 8030302 AT cwilson DOT fastmail DOT fm> <87mzytboa0 DOT fsf AT peder DOT flower> <16746 DOT 54438 DOT 748058 DOT 786459 AT byrd DOT xs4all DOT nl>
In-Reply-To: <16746.54438.748058.786459@byrd.xs4all.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Han-Wen Nienhuys wrote:
> No, this is not correct. My original email exactly described the
> problem: when linking the libsrfi-1 library with libtool 1.5.10 on
> Cygwin, libguile.dll.a is not linked, causing the link to fail.
> 
> For mysterious reasons (libtool brokenness, I suppose), the compile
> and make install do continue, but at run-time the (use-modules .. )
> call throws error 126, which is entirely understandable, since
> /usr/lib/ does not contain the libsrfi-1 DLL.
> 
> When linking libsrfi-1 by hand (inserting libguile.dll.a into the
> command line),  and copying the resulting DLL to /usr/lib/ , use-modules
> works correctly.

You still haven't answered MY question, from several days ago:

I wrote:
>  This:
> 
>     gcc -shared .libs/srfi-1.o -L/lib -L/usr/lib
>     -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -L/usr/local/lib
>     -lguile -lpthread -lgmp -lcrypt -o
>     .libs/cygguile-srfi-srfi-1-v-2-2.dll -Wl,--image-base=0x10000000
>     -Wl,--out-implib,.libs/libguile-srfi-srfi-1-v-2.dll.a
> 
> ought to succeed, IF
>   /home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs
> contains any of the following:
> 
>           libguile.dll.a
>           guile.dll.a
>           libguile.a
>           cygguile.dll
>           libguile.dll
>           guile.dll
> 
> That's what
> -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs  -lguile
> MEANS, after all. 

And then I wrote:
> BTW, note that the problem (whatever it is) exposed here, will be hidden by the patch I'm about to post to this list and to libtool-patches.
> 
> I really hope somebody (Jan? Han-Wen Nienhuys?) will try their guile build with unmodified libtool-1.5.10, and when the relink fails manually execute
> 
>>     gcc -shared .libs/srfi-1.o -L/lib -L/usr/lib
>>     -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -L/usr/local/lib
>>     -lguile -lpthread -lgmp -lcrypt -o
>>     .libs/cygguile-srfi-srfi-1-v-2-2.dll -Wl,--image-base=0x10000000
>>     -Wl,--out-implib,.libs/libguile-srfi-srfi-1-v-2.dll.a
> 
> from the appropriate directory, but adding "-v -Wl,-verbose" for verbose output from both gcc and ld.  When THAT fails, figure out why it can't find libguile.dll.a in /home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs, because if it is there, it really ought to be able to find it given
> 
> -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -lguile

--
Chuck






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