|
From: | Guillaume |
Subject: | [Octave-bug-tracker] [bug #55608] [MXE Octave] lib vs lib64 |
Date: | Wed, 30 Jan 2019 08:16:19 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
URL: <https://savannah.gnu.org/bugs/?55608> Summary: [MXE Octave] lib vs lib64 Project: GNU Octave Submitted by: gyom Submitted on: Wed 30 Jan 2019 01:16:17 PM UTC Category: Configuration and Build System Severity: 3 - Normal Priority: 5 - Normal Item Group: Build Failure Status: None Assigned to: None Originator Name: Guillaume Originator Email: Open/Closed: Open Discussion Lock: Any Release: other Operating System: GNU/Linux _______________________________________________________ Details: I am trying to build mxe-octave on openSUSE 15.0 and I come across a number of issues due to the fact that the built libraries are stored in usr/lib64 while they seem to be expected in usr/lib. Adding a symbolic link between them before the beginning of the built of any library allows me to proceed further (`mkdir usr; cd usr; ln -s lib64 lib`). Other errors occurs later on due a similar issue with usr/x86_64-w64-mingw32/lib vs usr/x86_64-w64-mingw32/lib64 but it's harder to deal with as both directories are used and symbolic links become replaced by hard links when a built package installs its libraries. This would mean that different packages use a different strategy to define where libraries are stored (/usr/lib vs /usr/lib64) for which openSUSE returns different answers. I could find a related discussion here: https://stackoverflow.com/questions/9247769/ _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55608> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |