[PATCH]: mknetrel builds Guile #3: libtool

[Charles Wilson]

Christopher Faylor wrote:

>>libtool needs to *know* what linker is being used -- but (at least on 
>>cygwin) it doesn't link using ld.  It uses gcc.
>>
>>But, libtool.m4 does cause configure.in/configure to test ld's 
>>characteristics during configure -- and you want those tests to be 
>>performed on the correct ld.
>>
> 
> How does libtool determine the correct linker?  I have never had any
> problems building things.  I would think that if libtool needed to be
> told to use i686-pc-cygwin-ld I would have noticed that by now.


Sorry, I should have been more specific.  libtool, in general, as used 
on the entire panoply of systems that support it, needs to know the 
correct ld.  That knowledge does not seem to be used in the cygwin bits, 
however.

So, *on the cygwin platform* or when *targetting the cygwin platform*, 
it seems that running the tests (via libtool.m4 -> aclocal.m4 -> 
configure) against the wrong ld will cause no harm (except perhaps a few 
confusing output messages during ./configure: e.g. if cross building on 
an AIX host, cygwin target -- where the AIX ld doesn't support shared libs).

Silly to worry about, I guess.  I tend to look at the big "general" 
picture too much, and not exclude extraneous information that doesn't 
apply to the specific problem: cygwin-target, linux (or other 
"mainstream" unix) host.

--Chuck