Re: alarm assert failure

No. Have no socks 4 on that host. IIRC, `--with-socks' assumes (static) library interface of that version. I certainly can link statically with already installed socks 5 library, and result will be the same. `getaddrinfo' will get socksified and will eventually call `alarm' from xemacs in the same place. In this crash `alarm' is called by libc as a part of file locking (see backtrace for details). Socks or no socks, `getaddrinfo' in a random libc may need to consult some shared files, which may involve file locking and calling `alarm'. Protection from this is necessary.