While compiling tcpwrap-1.0 I ran into a small problem:

The configure script checks whether libwrap is available by the usual
method of compiling a small piece of code and linking it against the
desired library.

Even though libwrap is available (/usr/sfw/lib/libwrap.so) this step
fails because there are two extern symbols in libwrap which the
application is required to provide:

[252]   |         0|         0|NOTY |GLOB |0    |UNDEF  |allow_severity
[301]   |         0|         0|NOTY |GLOB |0    |UNDEF  |deny_severity

And the actual tcpwrap code does indeed provide these:

% grep severity tcpwrap.c
int allow_severity = 0;
int deny_severity = 0;

.. but the small dummy code created by the configure script does not,
so it fails. 

One way to solve this is just by removing the libwrap detection from
the configure stage (as we already know it is available on OpenSolaris).



-- 
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems

Reply via email to