Re: eu3.2 on puppy 3.01 on qemu #2
Matt Lewis wrote:
>
> Matt Lewis wrote:
> >
> > ChrisBurch2 wrote:
> > >
> > > 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.
>
> Actually, looking at the code now, the error message assumes a value for
> eudir (as do other spots in the code) but the include processing does not,
> so this is possibly a bug. The documentation is slightly ambiguous to me:
>
> From euphoria/HTML/refman_2.htm#61
>
> Finally, if it still hasn't found the file, it will search euphoria\include.
>
> This directory contains the standard Euphoria include files. The environment
>
> variable EUDIR tells ex.exe/exw.exe/exu where to find your euphoria
> directory.
>
> It doesn't say what happens if EUDIR isn't set. We need to change some
> combination of the behavior (should be assume a default for EUDIR?) or
> the documentation and the error message.
>
> Matt
The installer does set EUDIR and EUINC. An issue I reported months ago is that
it does so repeatedly when successive versions are (re)installed. The INNO script
may not have the ability to detect whether the new path is redundant or not.
As a result, EUDIR not being set is to be expected only from old versions which
do not know about .conf files anyway. Unless the behaviour under Linux is
different, of course.
CChris
|
Not Categorized, Please Help
|
|
