[Development] Any supported platforms not tested in CI?

Thiago Macieira thiago.macieira at intel.com
Fri Oct 20 17:14:12 CEST 2017

On Friday, 20 October 2017 07:09:26 PDT Konstantin Tokarev wrote:
> I've found this on Intel side:
> https://software.intel.com/en-us/node/628867
> I hope Thiago can tell us more about this option.
> I know PathScale had bi-endian compiler in the past, but I don't know if
> it's possible to obtain it now.

That's a compiler to run on bi-endian systems, which I don't think anyone ever 
does. I've never seen this tool, I don't know if we could get access to it, 
and in any case I recommend against trying to do that.

For every architecture where the processor can run in either endianness, the 
system chooses one and sticks to it, so all software is specifically compiled 
for that choice. It's also encoded in the Qt sysinfo name:

$ $QTLIBDIR/libQt5Core.t.so | head -1
This is the QtCore library version Qt 5.10.0 (x86_64-little_endian-lp64 shared 
(dynamic) debug build; by GCC 7.2.1 20171005 [gcc-7-branch revision 253439])

	armel		- l for little endian
	mipsel		- l for little endian
	mips64el		- l for little endian
	ppc64el		- l for little endian

I'd recommend trying the mips build, though it doesn't have the "e" which I 
believe stands for either "embedded" or "EABI" (where the E stands for 
"embedded"). Yocto also defaults to big endian:

$ file -L /opt/poky/2.3/sysroots/mips32r2-poky-linux/lib/libc.so.6
/opt/poky/2.3/sysroots/mips32r2-poky-linux/lib/libc.so.6: ELF 32-bit MSB 
shared object, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked, 
interpreter /lib/ld.so.1, for GNU/Linux 3.2.0, stripped

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list