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

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

[Octave-bug-tracker] [bug #56876] Prefix ending with "/" leads to missin


From: Martin K
Subject: [Octave-bug-tracker] [bug #56876] Prefix ending with "/" leads to missing *.oct and *.m search paths.
Date: Mon, 9 Sep 2019 11:14:55 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

URL:
  <https://savannah.gnu.org/bugs/?56876>

                 Summary: Prefix ending with "/" leads to missing *.oct and
*.m search paths. 
                 Project: GNU Octave
            Submitted by: grisu86
            Submitted on: Mon 09 Sep 2019 03:14:53 PM UTC
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I recognized the following strange behavior when installing octave-5.1.0 from
scratch. 

My build scripts added a "/" to the end of the desired prefix and thus
configure was called like 

./configure --prefix=/opt/octave-5.1/ 

afterwards some commands are missing like the qr decomposition or plotting
although everything was found by the configure script. A look into the output
of "path" inside octave afterwards showed that the following paths are
missing: 
- PREFIX/lib/octave/5.1.0/site/oct/x86_64-pc-linux-gnu
- PREFIX/lib/octave/site/oct/api-v53/x86_64-pc-linux-gnu
- PREFIX/lib/octave/site/oct/x86_64-pc-linux-gnu
and some others. I found out that configure replaces some paths in 
libinterp/corefcn/default-defs.h.in with a leading "/" and some of the not.
This leads to the problem that the  prepend_home_dir function in
libinterp/corefcn/defaults.cc detects an absolute path and does not prepend
the correct prefix.  It seems to affect the following variables: 
- OCTAVE_LOCALVEROCTFILEDIR
- OCTAVE_LOCALAPIOCTFILEDIR
- OCTAVE_LOCALOCTFILEDIR
- OCTAVE_OCTFILEDIR

If I call the configure script without the trailing "/", like 

./configure --prefix=/opt/octave-5.1

the leading "/" in OCTAVE_OCTFILEDIR etc. is gone and prepend_home_dir returns
the correct path. 






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56876>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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