[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #63511] passing $ORIGIN via LDFLAGS lead to fo
From: |
Thomas Arndt |
Subject: |
[Octave-bug-tracker] [bug #63511] passing $ORIGIN via LDFLAGS lead to fortran compile failure |
Date: |
Mon, 12 Dec 2022 08:51:25 -0500 (EST) |
URL:
<https://savannah.gnu.org/bugs/?63511>
Summary: passing $ORIGIN via LDFLAGS lead to fortran compile
failure
Project: GNU Octave
Submitter: arndtthomas
Submitted: Mon 12 Dec 2022 01:51:24 PM UTC
Category: Configuration and Build System
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Installation Failure
Status: None
Assigned to: None
Originator Name: Thomas
Originator Email:
Open/Closed: Open
Release: 7.3.0
Discussion Lock: Any
Operating System: GNU/Linux
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Mon 12 Dec 2022 01:51:24 PM UTC By: Thomas Arndt <arndtthomas>
Hi guys,
I like to compile Octave and make it portable, so I thought to use
-Wl,-R,$ORIGIN/../lib/... to point to the library location even if the
compiled package was moved. However the configure process fails, since it gets
handed over to gfortran as -R,$ORIGIN/../lib. This leads configure to fail,
since only g++ understands this properly:
configure: error: linking to Fortran libraries from C fails
Is there a way without using patchelf to set the rpath e.g.:
0x000000000000000f (RPATH) Library rpath: [$ORIGIN/../lib]
(i did this for other programs too)
I like to get rid of the LD_LIBRARY_PATH settings!
KR,
Thomas
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63511>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #63511] passing $ORIGIN via LDFLAGS lead to fortran compile failure,
Thomas Arndt <=