Relative paths lead to full link line with all libs : ./liblist -m . < libname.map | tr " " "\n" | wc ## 110 libs
Relative paths lead to full link line with all libs : ./liblist -m . < libname.map | tr " " "\n" | wc ## 110 libs Absolute -m path that is over 85-90 characters in length (max lib length is 40 chars) leads to silent truncation of libs listed on the link line. ./liblist -m $PWD < libname.map | tr " " "\n" | wc ## 36 libs From the config/liblist.c code it is clearly due to the use of char libname[128] Clearly the workaround is to use relative paths, but nevertheless ... a trivial fix could avoid others the chore of tracking this down in future. Also using a really long path, will cause it to segment... p=/data/env/local/dyb/releases/1.0.0-rc0
p=dyb/releases/1.0.0-rc01/Nu-Wa- geant4/4.9.1.p01/ uncharacterized
Relative paths lead to full link line with all libs : ./liblist -m . < libname.map | tr " " "\n" | wc ## 110 libs Absolute -m path that is over 85-90 characters in length (max lib length is 40 chars) leads to silent truncation of libs listed on the link line. ./liblist -m $PWD < libname.map | tr " " "\n" | wc ## 36 libs From the config/liblist.c code it is clearly due to the use of char libname[128] Clearly the workaround is to use relative paths, but nevertheless ... a trivial fix could avoid others the chore of tracking this down in future. Also using a really long path, will cause it to segment... p=/data/env/local/dyb/releases/1.0.0-rc01/NuWa-1.0.0-rc01/../external/geant4/4.9.1.p01/uncharacterized_linux_debug/lib $p/liblist -m $p < $p/libname.map Segmentation fault
