Please upload: tcp_wrappers-7.6-3

Corinna Vinschen
Fri Apr 21 14:41:00 GMT 2006

On Apr 21 06:56, Bryan D. Thomas wrote:
> Yaakov wrote:
> > I know that tcp_wrappers doesn't officially come
> with
> > a shared library, but other distributions also do
> > such patches, but they version their shared lib as
> > libwrap0
> Yes, I have been looking at Debian. I will attempt to
> create libwrap0.dll.a, libwrap0.a.  cygwrap-1.dll is
> still correct, or cygwrap-0.dll?

No, you got that wrong.  The import library must not have the version in
its name.  If at one point tcp_wrappers would be changed in a backward
incompatible way, you would like new applications to be linked to the
new DLL, without forcing them to change their Makefiles.  Consider this

  zap: zap.o
    $(CC) -o zap zap.o -lwrap

If you rename libwrap.a and libwrap.dll.a to libwrap0.a and
libwrap0.dll.a, the Makefile would have to be changed accordingly.  But
that's not waht this is good for.  The import libs should always link
against the latest version of the DLL, only the DLL change their name
at each backward incompatible change.  So, right now, you should


> Thank you for the helpful information! Another help
> would be an example of how to see that things are
> working.  Am I correct to expect I could compile, for
> example, Apache from source and OpenSSH from source to
> get them both using the shared wrapper library, then
> see in Sysinternals Process Explorer that one is
> loaded, shared between? lsof would show this also,

Very simple.  The linker searches for *.dll.a first.  So, if it
exists, the application is linked against the DLL.  Only if *.dll.a
doesn't exists, it looks for *.a.

If you want to know which DLLs are linked to an application, just
use cygcheck:

  $ cygcheck /usr/bin/ssh.exe


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-apps mailing list