Re: exu not working

new topic     » goto parent     » topic index » view thread      » older message » newer message

Well, turns out, if it was a library error, you'd see a msg like
"ld.so.2: failed to load libncurses.so.6" or something, so that cant be it.

Also, the other possibility i can think of, ncurses failing to initalize
the terminal, cant be it either, as it'd also error an error on stdout/stderr.

Are you doing something to its stdin/stdout/stderr? Thats the only thing I could
think of ... unless ... hmm.

How are you invoking it? Via a remote telnet/ssh shell I suppose? Not that that
would change anything, but still .... hmm.

No matter how cryptic, an error is nearly always shown on the terminal (or, to
be more precise, on stdout/stderr, often used interchangably for error
messages).

Only thing I can think of, either you're running something else called exu,
or your binary is corrupted ... or exu's output is being redirected and lost
somewhere.

What happens if you type the full path to exu on the command line? And,
what does "du -b <full path to exu" show?

jbrown

On Thu, Feb 06, 2003 at 10:21:59PM -0000, tubby.toast at ntlworld.com wrote:
> 
> > 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.
> 
> 
> 
> TOPICA - Start your own email discussion group. FREE!

-- 
 /"\  ASCII ribbon              | 
 \ /  campain against           | Linux User:190064
  X   HTML in e-mail and        | Linux Machine:84163
 /*\  news, and unneeded MIME   |

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu