Re: exu not working
> Hmm .... Does it have correct execute permissions? In which context does
> exu work, and in which does it fail (besides in the cgi scrips)?
>
Permissions for exu are 755. exu doesn't work at all. Like I say, just
entering "exu" at the command prompt does absolutely nothing; I just get the
prompt again as if I had merely pressed enter. And, using "echo $?" I get
an exit code of 127.
> Do the scripts themselves have correct execute permission? What user owns
> the scripts/exu, and what user is running it? What is the first line of
the
> scripts?
>
This should all be ok. At the moment I'm just trying to get the interpreter
running on its own. The owner is "chrissy" and that is who I log on as over
telnet.
> As to which libraries are required for exu, I don't rememeber all of them,
> sorry, the big one was ncurses, which is a pain really. (I went as far as
> writing a huge wrapper to allow Linux Euphoria programs to use plain I/O
> by redefining a bunch of builtins and interfacing directly with glibc...
> however, that doesn't solve dependancy errors caused by a lack of ncurses
> on a machine. Rather annoying, really ... :/)
Can Rob or anyone else with the source tell me? Even if I do find out it's
going to be difficult to do much since it's not my system and tech support
are pretty unresponsive. I can't afford to move hosts right now and anyway
I doubt anyone would let me "test-drive" Euphoria on their system before I
pay up.
Is 2.4 going to be more compatible? I'd prefer not to wait but if it's that
or learn Perl...
chris.
|
Not Categorized, Please Help
|
|
