http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49375
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> 2011-06-12 14:43:41
UTC ---
(In reply to comment #1)
> LD_LIBRARY_PATH should be only set for executing testcases, not for
> compiling them.
That is not what we are doing:
lib/c-torture.exp: set_ld_library_path_env_vars
lib/gcc-dg.exp: set_ld_library_path_env_vars
lib/g++.exp: set_ld_library_path_env_vars
lib/gfortran.exp: set_ld_library_path_env_vars
lib/go.exp: set_ld_library_path_env_vars
lib/obj-c++.exp: set_ld_library_path_env_vars
lib/objc.exp: set_ld_library_path_env_vars
lib/plugin-support.exp: restore_ld_library_path_env_vars
lib/plugin-support.exp: set_ld_library_path_env_vars
lib/target-libpath.exp:# proc set_ld_library_path_env_vars { }
lib/target-libpath.exp:proc set_ld_library_path_env_vars { } {
lib/target-libpath.exp: verbose -log "set_ld_library_path_env_vars:
ld_library_path=$ld_library_path"
lib/target-libpath.exp:# proc restore_ld_library_path_env_vars { }
lib/target-libpath.exp:proc restore_ld_library_path_env_vars { } {
lib/wrapper.exp: set_ld_library_path_env_vars
set_ld_library_path_env_vars is called when test start and
restore_ld_library_path_env_vars is rarely used. Only
lib/plugin-support.exp handles it correctly.
