21.09.2016, 20:41, "Thiago Macieira" <thiago.macie...@intel.com>:
> On quarta-feira, 21 de setembro de 2016 19:24:34 PDT Oswald Buddenhagen wrote:
>>  > and you can then search the
>>  > paths from /etc/ld.so.conf & /etc/ld.so.conf.d/*.
>>
>>  that will suffer from x-build issues again.
>
> Hmm... if we're cross-compiling, we should have access to the path to the
> sysroot, so we can find ld.so.conf there.
>
> $ ls /opt/poky/sysroots/*/etc/ld.so.conf
> /opt/poky/sysroots/aarch64-poky-linux/etc/ld.so.conf
> /opt/poky/sysroots/armv7a-neon-poky-linux-gnueabi/etc/ld.so.conf
> /opt/poky/sysroots/mips32r2-poky-linux/etc/ld.so.conf
> /opt/poky/sysroots/mips64-poky-linux/etc/ld.so.conf
> /opt/poky/sysroots/ppc7400-poky-linux/etc/ld.so.conf
> /opt/poky/sysroots/ppce500v2-poky-linux-gnuspe/etc/ld.so.conf
> /opt/poky/sysroots/x86_64-pokysdk-linux/etc/ld.so.conf

Do these file have any content?

I have a few fully working toolchains from 2 vendors at my hands, one has empty 
ld.so.conf, others don't have any

>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> _______________________________________________
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

-- 
Regards,
Konstantin
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to