[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49191] working directory spoiled after run of
From: |
Georg Michel |
Subject: |
[Octave-bug-tracker] [bug #49191] working directory spoiled after run of mkoctfile |
Date: |
Mon, 26 Sep 2016 14:35:31 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 |
URL:
<http://savannah.gnu.org/bugs/?49191>
Summary: working directory spoiled after run of mkoctfile
Project: GNU Octave
Submitted by: georgmichel
Submitted on: Mon 26 Sep 2016 02:35:28 PM GMT
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: None
Assigned to: None
Originator Name: Georg Michel
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.2.0-rc2
Operating System: GNU/Linux
_______________________________________________________
Details:
When Octave is pointed to a working directory, it finds the scripts in this
directory as expected. However, after an (error free) run of mkoctfile and a
call to the just compiled function (in another but known directory), Octave
does not find the scripts in the working directory anymore. Even with cd and
pwd showing the correct working directory, the scripts there are not found.
The only solution that works for me is a restart after the compilation. Then
no new compilation is necessary and everything works as expected.
The whole thing appears under OpenSUSE Leap 42.1 with 4.2.0-rc2. With 4.0.0 it
is OK.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49191>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #49191] working directory spoiled after run of mkoctfile,
Georg Michel <=