T20 Linux booting error

Hi @devius! Sorry for the delay.

I’m setting up an environment to try and reproduce your build issue with BSP 2.3.

Also, can you please run another small quick test and try cleaning and building another image? Please run bitbake core-image-minimal -c cleanall then bitbake core-image-minimal. This won’t have Qt support, it’s just for us to test the build process. If it works we can then build the Qt X11 image.

HI, yes for sure I can!

Only one question, when I ran bitbake -c fetchall angstrom-qt-x11-image I had to correct a lot of path of differents repos until all the fetch succeeded, if I run now bitbake core-image-minimal -c cleanall, Will I lose all those route modifications due to cleaning?

ok, I ran what you said, same result

ERROR: Command Error: exit status: 1  Output:
Applying patch eglibc-svn-arm-lowlevellock-include-tls.patch
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|In file included from ../nptl/sysdeps/unix/sysv/linux/libc-lowlevellock.c:21:
|../nptl/sysdeps/unix/sysv/linux/lowlevellock.c: In function '__lll_lock_wait_private':
|../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:34: warning: implicit declaration of function 'THREAD_GETMEM'
|../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:34: error: 'THREAD_SELF' undeclared (first use in this function)
|../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:34: error: (Each undeclared identifier is reported only once
|../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:34: error: for each function it appears in.)
|../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:34: error: 'header' undeclared (first use in this function)
|make[4]: *** [/var/tmp/portage/sys-libs/glibc-2.7-r1/work/build-default-armv4l-unknown-linux-gnu-nptl/nptl/rtld-libc-lowlevellock.os] Error 1
|
|Upstream-Status: Pending
|
|--- libc/ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.h.orig
|+++ libc/ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
Patch eglibc-svn-arm-lowlevellock-include-tls.patch does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/fer/oe-core/build/out-eglibc/work/armv7at2hf-vfp-angstrom-linux-gnueabi/eglibc/linaro-2.19-r2014.04/temp/log.do_patch.4095
ERROR: Task 36 (/home/fer/oe-core/build/../stuff/meta-linaro/meta-linaro-toolchain/recipes-core/eglibc/eglibc_linaro-2.19.bb, do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2120 tasks of which 2109 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
No currently running tasks (2120 of 3870)

Summary: 1 task failed:
  /home/fer/oe-core/build/../stuff/meta-linaro/meta-linaro-toolchain/recipes-core/eglibc/eglibc_linaro-2.19.bb, do_patch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Could you maybe give the following a try? This is the latest I still remember ever having built more recently.

repo init -u http://git.toradex.com/toradex-bsp-platform.git -b LinuxImageV2.3-next

And as Gustavo suggested limit yourself just to the core-image-minimal as a first step.

ok, I did a fetchall first and succeded, now is compiling with core-image-minimal, when finish I’ll post back the results

Glad that worked. Yeah, we once planned to do a V2.3 maintenance release but we never came past what is now on -next.

Ok, seems to work!!

WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 1 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
WARNING: Use of PRINC 15 was detected in the recipe /home/fer/oe-core/build/../stuff/openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends)
Use of PRINC is deprecated.  The PR server should be used to automatically increment the PR.  See: https://wiki.yoctoproject.org/wiki/PR_Service.
NOTE: Tasks Summary: Attempted 1806 tasks of which 325 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory

Summary: There were 39 WARNING messages shown.

Just some warnings.

Next step?

Ok, seems to work!!

Great!

Next step?

Well, be happy and start using it (;-p).

But is the minimal image, without QT…could you guide me to compile with Qt5?

Hey @devius!

Now that core-image-minimal is compiled, can you try compiling qt-x11-image?

ok, but I have to add the meta-qt5 layer right?
Like this:
cd
cd oe-core/stuff

# repository version known to work with V2.1 and V2.2 images
META_QT5=ed05b91f137cb229e9ebababf9f72748aece1bf3
# repository version known to work with v2.4 images (alternatively use HEAD of dizzy branch)
META_QT5=adeca0db212d61a933d7952ad44ea1064cfca747
# repository version known to work with v2.5 images
META_QT5=a610beeee7dd973e544dc67e3598977f5f050b76

git clone --no-checkout https://github.com/meta-qt5/meta-qt5.git 
cd meta-qt5
git checkout -b mywork $META_QT5
cd ..

Which repository version is for V2.3??

And then add the layer to bblayers.conf like this?:

       ${TOPDIR}/../stuff/meta-openembedded/meta-systemd \
       ${TOPDIR}/../stuff/meta-openembedded/meta-networking \
       ${TOPDIR}/../stuff/meta-openembedded/meta-multimedia \
    +  ${TOPDIR}/../stuff/meta-openembedded/meta-ruby \
       ${TOPDIR}/../stuff/meta-lxde \
       ${TOPDIR}/../stuff/meta-browser \
    +  ${TOPDIR}/../stuff/meta-qt5 \

ok, but I have to add the meta-qt5 layer right?

No, not necessarily. Back at that time, openembedded-core came with Qt 4.8 integrated. So either you stick to that one or manually try adding the latest matching Qt 5 layer e.g. from here:

https://github.com/meta-qt5/meta-qt5/tree/daisy

I guess as long as you stay on the daisy branch you may be fine.

Ok I will try adding Qt5 from that branch, but the process is the same I described before right?

Yes, I believe so.

ok, I added the qt5 layer and ran qt-x11-image…and compiled!!!

But when I try to run my application (compiled wit Qt5) the libs are not found:

./myApp: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./myApp)
./myApp: /usr/lib/libQt5Core.so.5: version `Qt_5' not found (required by ./myApp)
./myApp: /usr/lib/libQt5Widgets.so.5: version `Qt_5' not found (required by ./myApp)
./myApp: /usr/lib/libQt5Gui.so.5: version `Qt_5' not found (required by ./myApp)
./myApp: /usr/lib/libQt5SerialPort.so.5: version `Qt_5' not found (required by ./myApp)

Then I searched in /usr/lib and the libs are there!! (also qt4 libs)
(I also couldn’t launch the application from qt, I had to copy it by hand.)

Any ideas?

Thanks

Maybe it has to do with the sdk that I am using in qt to compile the application, since it is the sdk that I used with image 2.8 and that is why the library does not match?

Anyway I tried to generate the sdk for this image (2.3) and this error appears:

 home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c: In function 'void initialize_argument_information(int, arg_data*, args_size*, int, tree, tree, tree, tree, cumulative_args_t, int, rtx_def**, int*, int*, int*, bool*, bool)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c:1230:9: error: 'STACK_CHECK_MAX_VAR_SIZE' was not declared in this scope
    |          STACK_CHECK_MAX_VAR_SIZE) > 0))
    |          ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c: In function 'void expand_builtin_setjmp_setup(rtx, rtx)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c:842:65: error: 'STACK_SAVEAREA_MODE' was not declared in this scope
    |    enum machine_mode sa_mode = STACK_SAVEAREA_MODE (SAVE_NONLOCAL);
    |                                                                  ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c: In function 'int store_one_arg(arg_data*, rtx, int, int, int)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c:4554:68: error: 'FUNCTION_ARG_PADDING' was not declared in this scope
    |        if (none != FUNCTION_ARG_PADDING (arg->mode, TREE_TYPE (pval)))
    |                                                                     ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c: In function 'void expand_builtin_longjmp(rtx, rtx)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c:965:65: error: 'STACK_SAVEAREA_MODE' was not declared in this scope
    |    enum machine_mode sa_mode = STACK_SAVEAREA_MODE (SAVE_NONLOCAL);
    |                                                                  ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c:4561:60: error: 'FUNCTION_ARG_PADDING' was not declared in this scope
    |        if (FUNCTION_ARG_PADDING (arg->mode, TREE_TYPE (pval)) == downward)
    |                                                             ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c: In function 'rtx_def* expand_builtin_nonlocal_goto(tree)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c:1067:57: error: 'STACK_SAVEAREA_MODE' was not declared in this scope
    |    r_sp = gen_rtx_MEM (STACK_SAVEAREA_MODE (SAVE_NONLOCAL),
    |                                                          ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c:4619:60: error: 'FUNCTION_ARG_PADDING' was not declared in this scope
    |        if (FUNCTION_ARG_PADDING (arg->mode, TREE_TYPE (pval)) == downward)
    |                                                             ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c: In function 'void expand_builtin_update_setjmp_buf(rtx)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/builtins.c:1134:65: error: 'STACK_SAVEAREA_MODE' was not declared in this scope
    |    enum machine_mode sa_mode = STACK_SAVEAREA_MODE (SAVE_NONLOCAL);
    |                                                                  ^
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c: In function 'bool must_pass_in_stack_var_size_or_pad(machine_mode, const_tree)':
    | /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/calls.c:4763:43: error: 'FUNCTION_ARG_PADDING' was not declared in this scope
    |        && (FUNCTION_ARG_PADDING (mode, type)
    |                                            ^
    | make[1]: *** [calls.o] Error 1
    | make[1]: *** Waiting for unfinished jobs....
    | make[1]: *** [builtins.o] Error 1
    | /bin/bash /home/fer/oe-core/build/out-eglibc/work-shared/gcc-linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/gcc/../move-if-change tmp-automata.c insn-automata.c
    | echo timestamp > s-automata
    | rm gcc.pod
    | make[1]: Leaving directory `/home/fer/oe-core/build/out-eglibc/work/x86_64-angstromsdk-linux/gcc-crosssdk-initial/linaro-4.8-r2014.04/gcc-linaro-4.8-2014.04/build.x86_64-linux.x86_64-angstromsdk-linux/gcc'
    | make: *** [all-gcc] Error 2
    | ERROR: oe_runmake failed
    | WARNING: exit code 1 from a shell command.
    | ERROR: Function failed: do_compile (log file is located at /home/fer/oe-core/build/out-eglibc/work/x86_64-angstromsdk-linux/gcc-crosssdk-initial/linaro-4.8-r2014.04/temp/log.do_compile.68862)
    ERROR: Task 4215 (/home/fer/oe-core/build/../stuff/meta-linaro/meta-linaro-toolchain/recipes-devtools/gcc/gcc-crosssdk-initial_linaro-4.8.bb, do_compile) failed with exit code '1'
    NOTE: Tasks Summary: Attempted 4663 tasks of which 4356 didn't need to be rerun and 1 failed.
    NOTE: Writing buildhistory
    Waiting for 0 running tasks to finish:
    
    Summary: 1 task failed:
      /home/fer/oe-core/build/../stuff/meta-linaro/meta-linaro-toolchain/recipes-devtools/gcc/gcc-crosssdk-initial_linaro-4.8.bb, do_compile
    Summary: There were 2 WARNING messages shown.
    Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Sorry for so many problems, but I really need to make this work.

Thanks

Hi @devius!

I think qt-x11-image compiles the image with Qt 4. You have to check which image recipe provides Qt 5. If there’s none, you’ll have to include the Qt 5 packages into a recipe or even in local.conf.

But as I said here I added the meta-qt5 layer already…and the libs qt5 seems to be in /usr/lib…

Did you see my last comment in this thread? I tried to compile the sdk (because I was using the sdk compiled for LinuxImage2.8 and maybe the libs are different) but an error occurs.

You have to check which image recipe provides Qt 5

Where can I find that info?

Ok, I rebuilt the sdk and succeded (angstrom-qt-x11-image), but seems is not for QT5, could you tell me how can I build an this image 2.3 with QT5 support?

Thanks