[EMAIL PROTECTED] (Marc Haber) writes:
> On 04 Jul 1999 16:51:07 +0200, you wrote:
> >Either your zlib installation or lsh's configure script seem to be
> >broken. Where is the zlib.h file located on your system?
>
> |mh@torres[5/505]:/mnt/main6/home/mh$ ls -al /usr/include/zlib.h
> |-rw-r--r-- 1 root root 40898 Oct 17 1998 /usr/include/zlib.h
> |mh@torres[6/506]:/mnt/main6/home/mh$
Then I don't understand why the configure script didn't find it. Do
you get any clues from the config.log file? What happens if you
manually edit the zlib_h lines in config.h or configure.cache?
> So I could compile it without scsh installed?
Yes. If you get a distribution (such as the current snapshot) where
all the automatically generated files are included. As soon as you
want to hack the C source files, however, you will need scsh to
regenerate these files to keep them uptodate. It's the src/*.x files,
and a few other header files.
> The problem is the following: You'd want your package to be a Debian
> package sooner or later. Depending on a non-free package like scsh,
> lsh couldn't get into the main distribution. I see this as a problem
> with Debian that could easily be fixed.
>
> But if lsh can be compiled and used without scsh, the problem is taken
> away IMO. But that's upon to the Debian people to decide.
I'd like to adapt the scheme stuff so that people can use scsh or
guile or whatever scheme implementation they have handy. But it's not
very high on my list of important things to do. (Personally, I like
scsh, and I'd also like to get some more experience with its module
system. That's why I don't want to replace it completely with the
guile-only version).
/Niels
