Qte toolchain also broken in 2013.06 branch

[ilovetogetspamed]

~/qte-example$ source /usr/local/oecore-x86_64/environment-setup-cortexa8hf-vfp-neon-angstrom-linux-gnueabi

~/qte-example$ qmake2
qmake2: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument

[ilovetogetspamed]

$ ldd /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/qmake2
linux-vdso.so.1 => (0x00007fff8c7a8000)
libstdc++.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../usr/lib/libstdc++.so.6 (0x00007f3e84880000)
libm.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../lib/libm.so.6 (0x00007f3e84580000)
libgcc_s.so.1 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../lib/libgcc_s.so.1 (0x00007f3e84368000)
libc.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../lib/libc.so.6 (0x00007f3e83fb8000)
/lib64/ld-linux-x86-64.so.2 (0x00007f3e84b88000)

[koenkooi]

Not a bug with the setupscripts, but with oe-core, but lets' track it here. I'll have a look at the (qt) SDKs later this week.

[ilovetogetspamed]

Thanks Koen, I'll keep you up to date if I find anything else. Chris

On Wed, Aug 28, 2013 at 3:05 AM, Koen Kooi [email protected] wrote:

Not a bug with the setupscripts, but with oe-core, but lets' track it
here. I'll have a look at the (qt) SDKs later this week.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-23395192
.

[ilovetogetspamed]

It looks like it could be an LD_LIBRARY_PATH issue from the documents I
found. See pastebin http://pastebin.com/em5yRhN4 for additional details.
Maybe the "environment-setup-cortexa8hf-vfp-neon-angstrom-linux-gnueabi"
needs updating? Don't know... in way over my head here...

On Wed, Aug 28, 2013 at 3:05 AM, Koen Kooi [email protected] wrote:

Not a bug with the setupscripts, but with oe-core, but lets' track it
here. I'll have a look at the (qt) SDKs later this week.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-23395192
.

[embarcados]

Folks,

Do you have any update on this?
Is there some patch or workaround?

I really need to get this working.

[ilovetogetspamed]

I ended up swtiching to Fedora 19 and it cleared up a lot of issues I was
having on Ubuntu 12.04 LTS. Also make sure you're using --sysroot on your
gcc command line. if you use the CC or CXX variables set when you source
the environment that will do it for you.

$ echo $CC
arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork
-mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 --sysroot=<your sdk's path
goes here>/sysroots/cortexa8hf-vfp-neon-angstrom-linux-gnueabi

On Wed, Oct 2, 2013 at 11:23 AM, embarcados [email protected]:

Folks,

Do you have any update on this?
Is there some patch or workaround?

I really need to get this working.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-25547927
.

[embarcados]

Thanks for the info.
I'm going to try it on Fedora 19.

This is really strange, as soon as Ubuntu (10.04, 11.10,12.04 and 12.10) is officially supported by Yocto Project and Fedora 19 does not:
http://www.yoctoproject.org/docs/1.4.2/ref-manual/ref-manual.html#detailed-supported-distros

Do you know if Yocto or OE guys are looking for a fix?
I could not find anything related on Yocto's bugzilla.

[embarcados]

Ok.
On Fedora 19 the issue __vdso_time has gone.
But I'm not able to use Qt creator. When I configure qmake path it says "Qt version is not properly installed please run make install".
I've followed this instructions:
https://community.freescale.com/thread/309578

Any clue about this?

[ilovetogetspamed]

Haven't figured that one out yet. Let me know if you figure it out.

On Wed, Oct 2, 2013 at 6:23 PM, embarcados [email protected] wrote:

Ok.
On Fedora 19 the issue __vdso_time has gone.
But I'm not able to use Qt creator. When I configure qmake path it says
"Qt version is not properly installed please run make install".
I've followed this instructions:
https://community.freescale.com/thread/309578

Any clue about this?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-25582270
.

[embarcados]

I have found the issue with Qt Creator.
You MUST have to install the qte toolchain on default path (/us/local/oecore-x86_64).