From: Darren Hart <dvhart@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: meta-linaro woes continue
Date: Thu, 03 Feb 2011 23:08:55 -0800 [thread overview]
Message-ID: <4D4BA607.3060006@linux.intel.com> (raw)
In-Reply-To: <4D4B37F9.7080708@mlbassoc.com>
On 02/03/2011 03:19 PM, Gary Thomas wrote:
> 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
>
> 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
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-02-04 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 23:19 meta-linaro woes continue Gary Thomas
2011-02-04 7:08 ` Darren Hart [this message]
2011-02-04 22:21 ` Darren Hart
2011-02-04 22:29 ` Gary Thomas
2011-02-04 23:54 ` Darren Hart
2011-02-05 0:30 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D4BA607.3060006@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.