All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] bitbake meta-toolchain with gcc 4.5.1 failed
Date: Tue, 23 Aug 2011 20:42:51 -0700	[thread overview]
Message-ID: <4E54733B.2000809@linux.intel.com> (raw)
In-Reply-To: <cover.1313921149.git.liezhi.yang@windriver.com>

On 08/21/2011 03:08 AM, Robert Yang wrote:
> * Steps to reproduce the error:
> 1) Add the following lines to conf/local.conf:
>
> SDKGCCVERSION="4.5.1"
> GCCVERSION="4.5.1"
>
> 2) bitbake meta-toolchain
>
> The we will notice the error that sed can't find the directory:
>
> ${TMPDIR}/work-shared/gcc-${PV}/gcc-${PV}-${PR}
>
> we had changed the name of S from gcc-${PV} to gcc-${PV}-${PR}, but didn't
> update meta/recipes-devtools/gcc/gcc-common.inc, so fix S in gcc-common.inc
> would make it work.
>
> The following changes since commit edd8e1e8b974eb3f0f9f66c2207aadf43612350b:
>
>    documentation/adt-manual/adt-command.xml: general edits. (2011-08-20 17:52:00 -0700)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib robert/gcc_451
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/gcc_451
>
> Robert Yang (1):
>    bitbake meta-toolchain with gcc 4.5.1 failed
>
>   meta/recipes-devtools/gcc/gcc-common.inc |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2011-08-24  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-21 10:08 [PATCH 0/1] bitbake meta-toolchain with gcc 4.5.1 failed Robert Yang
2011-08-21 10:08 ` [PATCH 1/1] " Robert Yang
2011-08-24  3:42 ` Saul Wold [this message]

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=4E54733B.2000809@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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.