On 2017-05-10 01:31:02 +0200, Vincent Lefevre wrote: > > closing this issue, there is no "propoer" solution. > > I'm just thinking... Couldn't the use of a run path for > /usr/lib/gcc-snapshot/lib be a proper solution? i.e. give > a better wrapper as an example? For instance, on amd64, > the wrapper could be: > > ----------- snip ---------- > #!/bin/sh > LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH > PATH=/usr/lib/gcc-snapshot/bin:$PATH > exec gcc -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib \ > -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib32 \ > -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/libx32 "$@" > ----------- snip ----------
Forget that. This breaks the use of LD_RUN_PATH. :( Or the contents of LD_RUN_PATH should be added as rpath arguments by the wrapper. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)