[Ecls-list] [usocket-devel] Usocket and ECL's MAKE-BUILD

Chun Tian (binghe) binghe.lisp at gmail.com
Sat Aug 27 05:51:17 UTC 2011

Hi, Juano

Thanks, your patch has been merged into usocket.  I didn't know that packages like XXX-SYSTEM are not needed any more, and you're right that the logical pathname definition was never used by other usocket code.

These changes (with others) will appear in next release 0.5.4, which should be released on mid September.


Chun Tian (binghe)

在 2011-8-26,17:42, Juan Jose Garcia-Ripoll 写道:

> 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
> - 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.
> - 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.
> - The references to usocket-system propagate to usocket-test.
> 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.
> Juano
> -- 
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain) 
> http://juanjose.garciaripoll.googlepages.com
> <patches.diff>_______________________________________________
> usocket-devel mailing list
> usocket-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20110827/27e0328e/attachment.html>

More information about the ecl-devel mailing list