27 Aug
2004
27 Aug
'04
3:21 p.m.
Indeed obvious, but just a comment, and btw, this is not just a comment
specific to this situation, usually dllcc comes with the VW distributions
and therefore had the correct pre-requisites been setup , dllcc should
have just loaded. I have noticed that quite often people release stuff but
never bother to test whether stuff loads cleanly. It would be great if we
all could agree to a policy where any package released was verified to
load onto a virgin image i.e. for example the base image that comes with
the VW NC distribution which now is setup to talk to the public repository.
-Charles
On Fri, 27 Aug 2004 09:02:23 +0200, Janko Mivšek <janko.mivsek(a)eranova.si>
wrote:
Hi all,
Quick and obvious solution is to load DLLCC parcel before loading Swazoo
even if you don't use SSL. I'll try to separate OpenSSL code from rest
of Swazoo later, so that DLLCC won't be needed.
Regards
Janko
Lukas Renggli pravi:
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
> This
may be the version of swazoo that is not the right one. Try
> another version: lukas what is the versions you use?
I'm using Swazoo
(0.9.76-bb10,bbadger).
Trying to load Swazoo has the same problem
(depends on DLLCC) and
fails to install.
As far as I know only the OpenSSL-package (library to support
HTTPS)
needs DLLCC, the rest is written in pure Smalltalk and therefor
completely platform independent. You shouldn't need to load the
OpenSSL-package to use Swazoo and/or SmallWiki. SmallWiki doesn't use
OpenSSL/HTTPS!
Hope this helps,
Lukas