From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 0/1] V2 gcc-cross: argument list too long when do_install
Date: Mon, 18 Jun 2012 09:51:39 -0700 [thread overview]
Message-ID: <4FDF5C9B.1000700@linux.intel.com> (raw)
In-Reply-To: <cover.1339643088.git.liezhi.yang@windriver.com>
On 06/14/2012 05:18 AM, Robert Yang wrote:
> Changes of V2:
> * Use the patch rather than sed command as Khem suggested.
>
> // Robert
>
> The following changes since commit 7f017cab0b3e4d5a4fc356eccd8eb8429b0531d0:
>
> connman: bump PR and add some comments (2012-06-13 13:11:23 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib robert/too_long
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/too_long
>
> Robert Yang (1):
> gcc-cross: argument list too long when do_install
>
> meta/recipes-devtools/gcc/gcc-4.6.inc | 1 +
> .../gcc/gcc-4.6/gcc-argument-list-too-long.patch | 33 ++++++++++++++++++++
> meta/recipes-devtools/gcc/gcc-4.7.inc | 1 +
> .../gcc/gcc-4.7/gcc-argument-list-too-long.patch | 33 ++++++++++++++++++++
> 4 files changed, 68 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-devtools/gcc/gcc-4.6/gcc-argument-list-too-long.patch
> create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/gcc-argument-list-too-long.patch
>
>
> _______________________________________________
> 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!
prev parent reply other threads:[~2012-06-18 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 12:18 [PATCH 0/1] V2 gcc-cross: argument list too long when do_install Robert Yang
2012-06-14 12:18 ` [PATCH 1/1] " Robert Yang
2012-06-18 16:51 ` 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=4FDF5C9B.1000700@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Zhenfeng.Zhao@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox