octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51994] strange path corruption when path is c


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #51994] strange path corruption when path is changed in a script or unit test
Date: Wed, 20 Sep 2017 16:18:51 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #3, bug #51994 (project octave):

Ok, this has something to do with the way the load path is stored differently
between stable and default and the side-effects of the builtin '__pathorig__'
function.

Here is the simplest test case I can come up with to demonstrate this weird
behavior


>> pathdef;
>> __have_gnuplot__
>> pathdef
error: if: undefined value used in conditional expression
error: called from
    .../libinterp/dldfcn/PKG_ADD at line 4 column 1
    pathdef at line 75 column 7


The underlying difference is due to 'pathdef', and the underlying internal
function '__pathorig__', altering the load path.

In previous versions of Octave, when running out of the build tree, 'pathdef'
returned an empty string and did not alter the load path. In the default
version, it returns what the default path _would be_ if Octave were already
installed. And if 'make install' has already been run, those directories are
actually added to the load path. This results in the wrong copy of
'__have_gnuplot__' being called when the PKG_ADD files are processed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51994>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]