Re: eu3.2 on puppy 3.01 on qemu #2
ChrisBurch2 wrote:
>
> Next step - puppy has a slightly unusual setup, in that user applications
> can be put into /root/my-applications/bin
>
> I put exu 3.2 there
>
> Then I ran exu sanity from the demo directory - it could find exu, but it
> couldn't
> find get.e (a normal include)
>
> The report was (along the lines of)
> can't find get.e in .
> or in
> or in/root/euphoria/include
>
> Now, get.e is in /root/euphoria/include, I assume this is a default search,
> so is there a problem here?
This message tells me that it didn't find the euinc.conf file. I'm assuming
that you don't have EUDIR set, so it assumes $HOME/euphoria, and looks in
include. This part of the code hasn't changed. Basically, it tries
the conf/command line dirs first, then looks for stuff in your EUINC dirs,
and finally in $EUDIR/include.
I see this behavior on windows, when I get rid of %EUDIR.
> When I put euinc.conf in the sanity directory, it ran fine.
Interesting. It's not supposed to do that (although that's what CK was
asking for). I suspect that Juergen's method of getting the path to
the interpreter didn't work, and it fell back to the current directory
(which is the current--3.1--behavior).
Can you tell me what the output of command_line() is? It should be
something along the lines of:
{"/root/my-applications/bin/exu", "myapp.exu"}
Matt
|
Not Categorized, Please Help
|
|
