[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Should not mkoctfile set --rpath when linking a standalone program?
|
From: |
Olaf Till |
|
Subject: |
Should not mkoctfile set --rpath when linking a standalone program? |
|
Date: |
Mon, 1 Oct 2012 15:46:35 +0200 |
|
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Currently
mkoctfile --link-stand-alone ...
does not automatically specify -rpath=/<prefix>/lib/octave/<version>
to the linker, so the resulting executable does not find
e.g. liboctinterp.so...
Should not -rpath=$OCTLIBDIR be included in the respective
commandline, directly or in LFLAGS or somewhere?
Olaf
--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net
signature.asc
Description: Digital signature
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- Should not mkoctfile set --rpath when linking a standalone program?,
Olaf Till <=