There are various things in how the usocket library is packaged that prevent it from being used in standalone programs with ECL. I summarize them<br><br>- A package usocket-system is defined and used in package.lisp. This package is not needed, as ASDF provides it and when the executable is created it does not exist.<br>

<br>- Standalone executables do not have ASDF in it. There is no need. Yet usocket uses it to define a logical hostname which is never used.<br><br>- The references to usocket-system propagate to usocket-test.<br><br>I attach a patch against the version that quicklisp distributes. With this patch usocket builds as an independent library without problems and can be shipped in standalone executables as well.<br>

<br>Juano<br clear="all"><br>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br><a href="http://juanjose.garciaripoll.googlepages.com" target="_blank">http://juanjose.garciaripoll.googlepages.com</a><br>