Is there some way we can tweak things so that Amy's problem (attached)
is less likely to happen?
What I'm thinking is that, though stock Darwin systems apparently
don't have ncurses, they probably have something equivalent. Could we
figure out what that something is, make whatever changes Hugs needs
(hopefully none) so that it can use that something and then (re)order
the tests in configure.in so that it tests for the preferred form
first.
Or, since the problem presumably comes from having built the binary
distro on quite a well configured development machine, does anyone out
there have access to a less well configured Darwin box that we could
use for building binary distributions?
[Oh, how I long for the days when source distributions were the
standard way of doing things. You ran configure, it detected what
your machine was actually like, and you built a binary which actually
matched your machine. Easy! The binary distribution approach only
seems to work well when machines are relatively uniform.]
--
Alastair
Amy Barnes <amymarie(a)slingshot.co.nz> writes:
> Finally worked out my problem was not that I didn't know to load
> hugs, I have a file missing -
>
> [localhost:~] amy% hugs dyld: hugs can't open library:
> /usr/lib/libncurses.5.dylib (No such file or directory, errno = 2)
