Sanity check output from 6.12 GCC is identical to output from 6.10 Toolchain

Alex Winfield lordadonis at gmail.com
Sun Feb 25 09:16:41 PST 2007


>On 2/25/07, Alex Winfield <lordadonis at gmail.com> wrote:
>  
>
>>    
>>
>>>On 2/25/07, Alex Winfield <lordadonis at gmail.com> wrote:
>>>
>>>
>>>      
>>>
>>>>SEARCH_DIR("/tools/i686-pc-linux-gnu/lib")
>>>>
>>>>
>>>>        
>>>>
>>>it looks like the new linker from 6.11 binutils is not being used.
>>>try that grep command on the linker binary inside the chroot
>>>environment and see what you get.
>>>
>>>$ grep -a 'SEARCH.*/usr/lib' /usr/bin/ld |sed 's|; |\n|g' | sort | uniq
>>>SEARCH_DIR("/lib")
>>>SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
>>>SEARCH_DIR("/usr/lib");
>>>SEARCH_DIR("/usr/local/lib")
>>>
>>>      
>>>
>>Using that grep command, I get the exact same output that you listed:
>>
>>$ grep -a 'SEARCH.*/usr/lib' /usr/bin/ld |sed 's|; |\n|g' | sort | uniq
>>SEARCH_DIR("/lib")
>>SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
>>SEARCH_DIR("/usr/lib");
>>SEARCH_DIR("/usr/local/lib")
>>
>>    
>>
>
>so now i wonder if PATH was set correctly.
>The shell will use the first match it finds so the order of those
>directories does matter. Double check the set up
>when entering the chroot environment.
>  
>
Checking variable PATH:

echo $PATH
/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin

that's the output.



More information about the lfs-support mailing list