FS#62028 - [opencascade] CMake files fail for non-standard $PATH
Attached to Project:
Community Packages
Opened by Gabriel Souza Franco (gbs) - Saturday, 16 March 2019, 14:09 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 17 March 2019, 16:32 GMT
Opened by Gabriel Souza Franco (gbs) - Saturday, 16 March 2019, 14:09 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 17 March 2019, 16:32 GMT
|
Details
Description:
Due to CMake search rules, if /bin comes before /usr/bin in the path, the prefix computed in the opencascade CMake files becomes '/', resulting in paths like '//include/opencascade' which don't exist. This was reported as build failures when trying to compile freecad from the AUR. Steps to reproduce: - export PATH=/bin:$PATH - Try to build freecad Fix: I've attached a new version of the cmake-fix-variable patch that fixes both the original 64-bit suffix issue and this new path issue. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Sunday, 17 March 2019, 16:32 GMT
Reason for closing: Not a bug
Additional comments about closing: Do not use /bin in your PATH as it will break relative links in many places. Relative links are kind of ugly, but they are also an upstream issue; meanwhile, there is a reason Arch does not officially ship with /bin in the PATH (because it does not work and never has since the /usr merge).
As a general rule of thumb it is advisable to treat the PATH installed by /etc/profile as canonical, and only ever modify it, and only then by adding your own custom paths --not by re-adding any system paths.
Sunday, 17 March 2019, 16:32 GMT
Reason for closing: Not a bug
Additional comments about closing: Do not use /bin in your PATH as it will break relative links in many places. Relative links are kind of ugly, but they are also an upstream issue; meanwhile, there is a reason Arch does not officially ship with /bin in the PATH (because it does not work and never has since the /usr merge).
As a general rule of thumb it is advisable to treat the PATH installed by /etc/profile as canonical, and only ever modify it, and only then by adding your own custom paths --not by re-adding any system paths.