[yocto] Building toolchain(meta-toolchain) issue for mips

[Mark Hatle]

On 8/14/14, 7:39 AM, atulkumar singh wrote:
> Hi Folks,
>
> I am trying to build toolchain, but while building I am getting following warning:
>
>                  WARNING: QA Issue: gcc-cross-canadian-mips64-n32: found library
> in wrong location:
> /usr/local/windriver/sysroots/x86_64-pokysdk-linux/usr/libexec/mips64-windriver-linux-gnun32/gcc/mips64-windriver-linux-gnun32/4.9.1/liblto_plugin.so.0.0.0
>
> gcc-cross-canadian-mips64-n32: found library in wrong location:
> /usr/local/windriver/sysroots/x86_64-pokysdk-linux/usr/libexec/mips64-windriver-linux-gnun32/gcc/mips64-windriver-linux-gnun32/4.9.1/liblto_plugin.so
>
> gcc-cross-canadian-mips64-n32: found library in wrong location:
> /usr/local/windriver/sysroots/x86_64-pokysdk-linux/usr/libexec/mips64-windriver-linux-gnun32/gcc/mips64-windriver-linux-gnun32/4.9.1/liblto_plugin.so.0
> [libdir]

The above QA warnings indicate that a library was found at a non-standard (/lib, 
/usr/lib) location.  This is an issue if a user links to the library and it's 
not available in the standard ld.so load path.

>                  Matched in
> manifest-x86_64_x86_64-nativesdk-gdb-cross-canadian-mips64.populate_sysroot
>
> manifest-x86_64_x86_64-nativesdk-gdb-cross-canadian-mips32r2.populate_sysroot
>
>
> /data/home/asingh/Yocto/poky/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux/usr/local/windriver/sysroots/x86_64-pokysdk-linux/usr/share/gdb/syscalls/mips-n32-linux.xml
>
>     Matched in
> manifest-x86_64_x86_64-nativesdk-gdb-cross-canadian-mips64.populate_sysroot
>
> manifest-x86_64_x86_64-nativesdk-gdb-cross-canadian-mips32r2.populate_sysroot
>
>
> /data/home/asingh/Yocto/poky/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux/usr/local/windriver/sysroots/x86_64-pokysdk-linux/usr/share/gdb/syscalls/arm-linux.xml

The above indicates two packages, x86_64-nativesdk-gdb-cross-canadian-mips64 and 
x86_64-nativesdk-gdb-cross-canadian-mips32r2 both provided the same file at the 
same installation path.  While not always, this is often times an indication of 
a bug in the system.

As long as both packages could be used separately, and the contents of the two 
files are identical this can be ignored.

--Mark

> Thanks and Regards,
>
> ATUL KUMAR SINGH
>
> This message contains information that may be privileged or confidential and is
> the property of the KPIT Technologies Ltd. It is intended only for the person to
> whom it is addressed. If you are not the intended recipient, you are not
> authorized to read, print, retain copy, disseminate, distribute, or use this
> message or any part thereof. If you receive this message in error, please notify
> the sender immediately and delete all copies of this message. KPIT Technologies
> Ltd. does not accept any liability for virus infected mails.
>
>
>