meta-linaro woes continue
n.b. this is a continuation of "Kernel Panics on armv4t with gcc.4.5.1" but the actual discussion has changed enough and there was too much noise in the previous thread.
Trying to use the meta-linaro layer (to solve my problems with GCC/4.5.1 on armv5te ), I was able to include and use the layer with the attached changes. I added this layer intact, moving meta-linaro into my poky tree at the same level as meta, meta-extras, etc.
I also had to copy meta/recipes-devtools/gcc/gcc-4.5.1 into meta-linaro/recipes-devtools/gcc (I didn't know how to expand the FILESPATH variable to suck from the main meta tree)
The next problem is this:
| configure: WARNING: unrecognized options: --enable-languages, --enable-threads, --enable-target-optspace, --enable-lto, --enable-libssp, --disable-bootstrap, --disable-libgomp, --disable-libmudflap, --with-float, --with-local-prefix, --with-sysroot, --with-build-sysroot, --disable-libunwind-exceptions, --enable-__cxa_atexit | Checking autotools environment for common misconfiguration | NOTE: Checking autotools environment for common misconfiguration | This autoconf log indicates errors, it looked at host includes. | Rerun configure task after fixing this. The path was '/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3' | ERROR: This autoconf log indicates errors, it looked at host includes. | Rerun configure task after fixing this. The path was '/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3' | Function 'do_qa_configure' failed | ERROR: Function 'do_qa_configure' failed
NOTE: package gcc-runtime-4.5.1.linaro-r0: task do_qa_configure: Failed
Ideas? I'm really anxious to see if this fixes my kernel problems.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
meta-linaro/conf/layer.conf +2 -1
@@ -5,7 +5,8 @@ RSP_ROOT ?= "sda1" BBPATH := "${BBPATH}:${LAYERDIR}" # We have an images and various recipe-* directories, add to BBFILES -BBFILES := "${BBFILES} ${LAYERDIR}/images/*.bb ${LAYERDIR}/images/*.bbappend ${LAYERDIR}/recipes-*/*.bb ${LAYERDIR}/recipes-*/*.bbappend" +BBFILES := "${BBFILES} ${LAYERDIR}/images/*.bb ${LAYERDIR}/images/*.bbappend \ + ${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend" BBFILE_COLLECTIONS += "linaro" BBFILE_PATTERN_linaro := "^${LAYERDIR}/"
meta-linaro/recipes-devtools/gcc/gcc-4.5.1.linaro.inc +9 -1
@@ -49,6 +49,14 @@ SRC_URI = "http://launchpad.net/gcc-linaro/4.5/4.5-2010.11-0/+download/gcc-linar file://gcc-poison-parameters.patch \ " + +do_move_src() { + echo moving ${WORKDIR}/gcc-linaro-4.5-2010.11-1 ${WORKDIR}/gcc-${PV} + mv ${WORKDIR}/gcc-linaro-4.5-2010.11-1 ${WORKDIR}/gcc-${PV} +} + do_unpack_append() { - mv gcc-linaro-4.5-2010.11-1 gcc-${PV} + bb.build.exec_func('do_move_src', d) } + +
Quoted 3 lines · Gary Thomas
n.b. this is a continuation of "Kernel Panics on armv4t with gcc.4.5.1" but the actual discussion has changed enough and there was too much noise in the previous thread.
Hi Gary,
We're both pounding away on the meta-linaro layer at the same time unfortunately. I've reorganized things a bit and cleaned up how the layer is configured. I believe this layer ran into some trouble when gcc and binutils changed, but also suffered from a bad BBFILES variable as well (as you noted below). I'll push my changes to poky-contrib/dvhart/meta-linaro just as soon as they build.
--
Darren
Quoted 42 lines
Trying to use the meta-linaro layer (to solve my problems with GCC/4.5.1 on armv5te ), I was able to include and use the layer with the attached changes. I added this layer intact, moving meta-linaro into my poky tree at the same level as meta, meta-extras, etc.
I also had to copy meta/recipes-devtools/gcc/gcc-4.5.1 into meta-linaro/recipes-devtools/gcc (I didn't know how to expand the FILESPATH variable to suck from the main meta tree)
The next problem is this:
| configure: WARNING: unrecognized options: --enable-languages, --enable-threads, --enable-target-optspace, --enable-lto, --enable-libssp, --disable-bootstrap, --disable-libgomp, --disable-libmudflap, --with-float, --with-local-prefix, --with-sysroot, --with-build-sysroot, --disable-libunwind-exceptions, --enable-__cxa_atexit
| Checking autotools environment for common misconfiguration | NOTE: Checking autotools environment for common misconfiguration | This autoconf log indicates errors, it looked at host includes. | Rerun configure task after fixing this. The path was'
/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3'| ERROR: This autoconf log indicates errors, it looked at host includes.
| Rerun configure task after fixing this. The path was '/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3'| Function '
do_qa_configure' failed
| ERROR: Function 'do_qa_configure' failed
NOTE: package gcc-runtime-4.5.1.linaro-r0: taskdo_qa_configure: FailedIdeas? I'm really anxious to see if this fixes my kernel problems.
Thanks
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 14 lines · Darren Hart
Quoted 3 lines · Gary Thomas
n.b. this is a continuation of "Kernel Panics on armv4t with gcc.4.5.1" but the actual discussion has changed enough and there was too much noise in the previous thread.
Hi Gary,
We're both pounding away on the meta-linaro layer at the same time unfortunately. I've reorganized things a bit and cleaned up how the layer is configured. I believe this layer ran into some trouble when gcc and binutils changed, but also suffered from a bad BBFILES variable as well (as you noted below). I'll push my changes to poky-contrib/dvhart/meta-linaro just as soon as they build.
Quoted 39 lines
--
DarrenQuoted 36 lines
Trying to use the meta-linaro layer (to solve my problems with GCC/4.5.1 on armv5te ), I was able to include and use the layer with the attached changes. I added this layer intact, moving meta-linaro into my poky tree at the same level as meta, meta-extras, etc.
I also had to copy meta/recipes-devtools/gcc/gcc-4.5.1 into meta-linaro/recipes-devtools/gcc (I didn't know how to expand the FILESPATH variable to suck from the main meta tree)
The next problem is this:
| configure: WARNING: unrecognized options: --enable-languages, --enable-threads, --enable-target-optspace, --enable-lto, --enable-libssp, --disable-bootstrap, --disable-libgomp, --disable-libmudflap, --with-float, --with-local-prefix, --with-sysroot, --with-build-sysroot, --disable-libunwind-exceptions, --enable-__cxa_atexit
| Checking autotools environment for common misconfiguration | NOTE: Checking autotools environment for common misconfiguration | This autoconf log indicates errors, it looked at host includes. | Rerun configure task after fixing this. The path was'
/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3'| ERROR: This autoconf log indicates errors, it looked at host includes.
| Rerun configure task after fixing this. The path was '/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3'| Function '
do_qa_configure' failed
| ERROR: Function 'do_qa_configure' failed
NOTE: package gcc-runtime-4.5.1.linaro-r0: taskdo_qa_configure: FailedIdeas? I'm really anxious to see if this fixes my kernel problems.
I'm hitting something similar with libtool. I've pushed my dev branch out so you can see how things have changed. I've also asked Nitin to take a look at the libtool issues (and if they are related to the linaro gcc).
My branch is available here:
poky-extras/dvhart/meta-linaro-dev
I picked up your do_src_move change as it resolves the issue - but I can't say that I really understand the problem being solved - can you elaborate on why you took this approach? I'll credit you properly in the commit in the final set of branches.
Also note, this branch WILL be rebased and otherwise abused as I get it in shape for a pull request.
Thanks,
Darren
Quoted 11 lines
Quoted 9 lines
Thanks
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 58 lines · Darren Hart
Quoted 14 lines · Darren Hart
Quoted 3 lines · Gary Thomas
n.b. this is a continuation of "Kernel Panics on armv4t with gcc.4.5.1" but the actual discussion has changed enough and there was too much noise in the previous thread.
Hi Gary,
We're both pounding away on the meta-linaro layer at the same time unfortunately. I've reorganized things a bit and cleaned up how the layer is configured. I believe this layer ran into some trouble when gcc and binutils changed, but also suffered from a bad BBFILES variable as well (as you noted below). I'll push my changes to poky-contrib/dvhart/meta-linaro just as soon as they build.
Quoted 39 lines
--
DarrenQuoted 36 lines
Trying to use the meta-linaro layer (to solve my problems with GCC/4.5.1 on armv5te ), I was able to include and use the layer with the attached changes. I added this layer intact, moving meta-linaro into my poky tree at the same level as meta, meta-extras, etc.
I also had to copy meta/recipes-devtools/gcc/gcc-4.5.1 into meta-linaro/recipes-devtools/gcc (I didn't know how to expand the FILESPATH variable to suck from the main meta tree)
The next problem is this:
| configure: WARNING: unrecognized options: --enable-languages, --enable-threads, --enable-target-optspace, --enable-lto, --enable-libssp, --disable-bootstrap, --disable-libgomp, --disable-libmudflap, --with-float, --with-local-prefix, --with-sysroot, --with-build-sysroot, --disable-libunwind-exceptions, --enable-__cxa_atexit
| Checking autotools environment for common misconfiguration | NOTE: Checking autotools environment for common misconfiguration | This autoconf log indicates errors, it looked at host includes. | Rerun configure task after fixing this. The path was'
/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3'| ERROR: This autoconf log indicates errors, it looked at host includes.
| Rerun configure task after fixing this. The path was '/home/local/efacec_omap_linaro/tmp/work/armv5te-poky-linux-gnueabi/gcc-runtime-4.5.1.linaro-r0/gcc-4.5.1.linaro/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libstdc++-v3'| Function '
do_qa_configure' failed
| ERROR: Function 'do_qa_configure' failed
NOTE: package gcc-runtime-4.5.1.linaro-r0: taskdo_qa_configure: FailedIdeas? I'm really anxious to see if this fixes my kernel problems.
I'm hitting something similar with libtool. I've pushed my dev branch out so you can see how things have changed. I've also asked Nitin to take a look at the libtool issues (and if they are related to the linaro gcc).
Quoted 6 lines
My branch is available here:
poky-extras/dvhart/meta-linaro-dev
I picked up your
do_src_movechange as it resolves the issue - but I can't say that I really understand the problem being solved - can you elaborate on why you took this approach? I'll credit you properly in the commit in the final set of branches.
I made this change because do_unpack_append() was being treated as a Python function, so the syntax was wrong. By using that function to run a shell function, the problem is solved. I patterned this after similar functions, e.g. in the eglibc recipe. It took me a while to find and understand this, but then it became obvious.
Quoted 2 lines
Also note, this branch WILL be rebased and otherwise abused as I get it in shape for a pull request.
Thanks for your time
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 7 lines · Gary Thomas
Quoted 4 lines · Darren Hart
I picked up your
do_src_movechange as it resolves the issue - but I can't say that I really understand the problem being solved - can you elaborate on why you took this approach?
I'll credit you properly in the commit in the final set of branches.
Quoted 5 lines
I made this change because
do_unpack_append()was being treated as a Python function, so the syntax was wrong. By using that function to run a shell function, the problem is solved. I patterned this after similar functions, e.g. in the eglibc recipe. It took me a while to find and understand this, but then it became obvious.
Ewww, that's pretty obfuscated. Did you determine why one function is treated as python and the other as bash?
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 8 lines · Darren Hart
Quoted 7 lines · Gary Thomas
Quoted 4 lines · Darren Hart
I picked up your
do_src_movechange as it resolves the issue - but I can't say that I really understand the problem being solved - can you elaborate on why you took this approach?
I'll credit you properly in the commit in the final set of branches.
Quoted 8 lines
Quoted 5 lines
I made this change because
do_unpack_append()was being treated as a Python function, so the syntax was wrong. By using that function to run a shell function, the problem is solved. I patterned this after similar functions, e.g. in the eglibc recipe. It took me a while to find and understand this, but then it became obvious.Ewww, that's pretty obfuscated. Did you determine why one function is treated as python and the other as bash?
No clue, I was just following precedent. Richard probably knows the details.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------