[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #56876] configure with --libdir=/octave///lib
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #56876] configure with --libdir=/octave///lib leads to errors in load path construction |
Date: |
Tue, 10 Sep 2019 11:51:40 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36 |
Update of bug #56876 (project octave):
Severity: 3 - Normal => 2 - Minor
Priority: 5 - Normal => 3 - Low
Item Group: None => Build Failure
Status: Need Info => Confirmed
Summary: Prefix ending with "/" leads to missing *.oct and
*.m search paths. => configure with --libdir=/octave///lib leads to errors in
load path construction
_______________________________________________________
Follow-up Comment #4:
Thank you, that helps. I can confirm, if I build Octave with
'--prefix=${PREFIX} --libdir='${PREFIX}//lib', then several directory
variables look like absolute directories rather than relative directories
under OCTAVE_HOME.
This can be easily worked around by calling configure with properly normalized
file names, but I agree that the build system should be resistant to this kind
of unusual input.
Updating summary description.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56876>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/