Summary: | Build system mishandles ORIGIN-based runpath | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Jeffrey Walton <noloader> |
Component: | Build Process | Assignee: | Chris Liddell (chrisl) <chris.liddell> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | sphinx.pinastri |
Priority: | P4 | ||
Version: | 9.53.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- |
Description
Jeffrey Walton
2020-09-16 06:52:47 UTC
Google finds only one site that has "audit-rpath-bins.sh". Please give an example of a platform where Ghostscript does not build. (In reply to Peter Cherepanov from comment #1) > Google finds only one site that has "audit-rpath-bins.sh". That's probably my Build Scripts at https://github.com/noloader/Build-Scripts. > Please give an > example of a platform where Ghostscript does not build. Ubuntu 18.05, x86_64. Another is Solaris 11.3, i86pc. Yet another is CentOS 5, x86_64. None of them handle RUNPATHs properly. I have a admit, I can't see a way to make this work reliably. And I can't see any way, anywhere that autotools would handle it. Basically, every time the "value" of LDFLAGS is assigned, the variable expansion will happen, and we do that in various places for a number of reasons. After digging into this again, I really feel this is a limitation of autoconf and co more than a specific problem with the Ghostscript build. I'm therefore changing this to "Later", so it won't be forgotten. |