Andreas Schwab <sch...@linux-m68k.org> writes:
> Rainer Orth <r...@cebitec.uni-bielefeld.de> writes:
>
>> diff --git a/gcc/testsuite/g++.dg/cilk-plus/cilk-plus.exp
>> b/gcc/testsuite/g++.dg/cilk-plus/cilk-plus.exp
>> --- a/gcc/testsuite/g++.dg/cilk-plus/cilk-plus.exp
>> +++ b/gcc/testsuite/g++.dg/cilk-plus/cilk-plus.exp
>> @@ -25,10 +25,11 @@ if { ![check_effective_target_cilkplus]
>> verbose "$tool $libdir" 1
>> set library_var "[get_multilibs]"
>> # Pointing the ld_library_path to the Cilk Runtime library binaries.
>> -set ld_library_path "$[get_multilibs]/libcilkrts/.libs"
>> +append ld_library_path ":${library_var}/libcilkrts/.libs"
>> +set_ld_library_path_env_vars
>>
>> -set ALWAYS_CFLAGS ""
>> -lappend ALWAYS_CFLAGS "-L${library_var}/libcilkrts/.libs"
>> +global TEST_EXTRA_LIBS
>> +set TEST_EXTRA_LIBS "-L${library_var}/libcilkrts/.libs"
>
> There is no point in doing this twice.
What are you talking about? ld_library_path and its corresponding
environment variables are used by the runtime linker (ld.so.1 or
whatever), while the -L flags are for ld.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
