libtool creating DLLs called ".exe"

libtool creating DLLs called ".exe"

[Lapo Luchini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerrit wrote (in http://www.cygwin.com/ml/cygwin/2004-10/msg00558.html):

|> Sometimes it switches to .exe instead of .dll.  Will investigate
|> this further. My current theory is that -o <soname> just missed
|> the .dll extension and .exe is then taken as default.
|
| I saw similar errors before, IIRC there were some old MACROS in .m4
|  files used from inside the package source tree, but never tracked
| it really down.  After cleaning up with old buggy .m4 files and
| reconfiguring it works in most of the cases.

What about if it happens and the source don't have no custom m4 files? 0=)
I got the problem specifically in SQLite 3.0.8 sources, it seems that
$soname isn't set at all.

I'll try to debug it this evening, on the train, on my way home...
hope to find the problem and/or a fix.

Lapo

BTW: is it possible to rename the "used DLLs" in a compiled executable?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iEYEARECAAYFAkHJUssACgkQaJiCLMjyUvv19QCfU5COHDfe54UZCQ3JTaZFIcHf
/MYAoMUBn5bnwhcBTwBjJroclP03O8ii
=sGTS
-----END PGP SIGNATURE-----


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

Re: libtool creating DLLs called ".exe"

[Lapo Luchini]

Lapo Luchini wrote:

> I'll try to debug it this evening, on the train, on my way home...
> hope to find the problem and/or a fix.

In the libtool generated for sqilte I found the bug to be that $soname
is defined with $shared_extension, which in turn is defined with
$shrext, but the file contained "only" a definition for $shrext_cmds
(defined but never used), and no $shrext at all.

Modifying the line to say $shrext instead of $shrext_cmds completely
solved the problem. I was pretty much happy and ready to send a ptch
upstream when I noticed that in a different project the code that used
$shr_ext wasn't included at all and that "patch" did nothing to help.

Moreover reading the "original" libtool I noticed that BOTH $shrext and
$shrext_cmds are used here and there... but I know very little about
libtool internals.

Thus, I don't know the "real solution" yet ^_^"""
Any suggestion?

(one could be to write to a libtool mailing list insetad of a cygwin
one, that's for sure.. but I tought someone could be interested too, as
the problem arose more than one time on this list already...)

-- 
Lapo Luchini
lapo@lapo.it (PGP & X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)


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