All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH] arago.conf: Update preferred version of binutils to 2.23.1
Date: Tue, 4 Mar 2014 22:06:36 -0500	[thread overview]
Message-ID: <20140305030635.GT22125@edge> (raw)
In-Reply-To: <1393802295-7212-1-git-send-email-sam.nelson@ti.com>

What are you strying to fix here? Moreover, arago.conf is not the right place 
for that...


On Sun, Mar 02, 2014 at 06:18:15PM -0500, Sam Nelson wrote:
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> 
> ---
> - 2.23.1 is available in oe-core/meta/recipes-devtools/binutils/binutils_2.23.1.bb
> ---
> ---
>  meta-arago-distro/conf/distro/arago.conf |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf
> index 76254f2..a789e89 100644
> --- a/meta-arago-distro/conf/distro/arago.conf
> +++ b/meta-arago-distro/conf/distro/arago.conf
> @@ -70,3 +70,5 @@ LICENSE_FLAGS_WHITELIST = "commercial_gst-ffmpeg"
>  PACKAGE_ARCH := "${TUNE_PKGARCH}-${PREFERRED_VERSION_linux-libc-headers}"
>  # Need to include the new PACKAGE_ARCH to the PACKAGE_ARCHS variable
>  PACKAGE_ARCHS += "${TUNE_PKGARCH}-${PREFERRED_VERSION_linux-libc-headers}"
> +
> +PREFERRED_VERSION_binutils = "2.23.1"
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2014-03-05  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 23:18 [PATCH] arago.conf: Update preferred version of binutils to 2.23.1 Sam Nelson
2014-03-05  3:06 ` Denys Dmytriyenko [this message]
2014-03-05 17:41   ` Nelson, Sam
2014-03-05 19:55     ` Denys Dmytriyenko
2014-03-05 20:31       ` Nelson, Sam

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=20140305030635.GT22125@edge \
    --to=denys@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=sam.nelson@ti.com \
    /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.