All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: raj.khem@gmail.com
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 2/2] binutils: Allow plugins
Date: Sun, 22 Jan 2012 13:41:50 -0500	[thread overview]
Message-ID: <4F1C586E.7030809@gmail.com> (raw)
In-Reply-To: <20120121225823.GA12691@sakrah.homelinux.org>

On 21/01/2012 5:58 PM, Khem Raj wrote:
> enabling plugins regardless is a good thing and since we use binutils
> 2.22+ now a days in oe-core plugins are well supported. Please submit the patch
> where you add this option (--enable-plugins) to binutils common configure
> that will be add to EXTRA_OECONF in binutils.inc
>
> -Khem

Sweet! Sorry I've been MIA for a bit. I've sent in the new patch,
which patches all 3 includes. From a look, this seemed necessary,
but if it isn't, let me know.

Patch is sent in reply to the original patch set, titled:

     [PATCH 2/2 v2] binutils: Always enable plugins

Enjoy.

- Derek


  reply	other threads:[~2012-01-22 18:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  1:23 [PATCH 1/2] binutils-cross-canadian: Allow ld-is-gold Derek Buitenhuis
2012-01-04  1:23 ` [PATCH 2/2] binutils: Allow plugins Derek Buitenhuis
2012-01-06 21:48   ` Derek Buitenhuis
2012-01-06 22:31   ` Saul Wold
2012-01-21 22:58   ` Khem Raj
2012-01-22 18:41     ` Derek Buitenhuis [this message]
2012-01-05 20:15 ` [PATCH 1/2] binutils-cross-canadian: Allow ld-is-gold Saul Wold
2012-01-05 20:33   ` Derek Buitenhuis
2012-01-22 18:41 ` [PATCH 2/2 v2] binutils: Always enable plugins Derek Buitenhuis
2012-01-22 18:57   ` Khem Raj
2012-01-22 19:01     ` Derek Buitenhuis
2012-01-22 19:05       ` Khem Raj
2012-02-02  2:08     ` Derek Buitenhuis
2012-02-02  5:04       ` Khem Raj
2012-04-29 17:56         ` Derek Buitenhuis
2012-04-30 14:36           ` Saul Wold
2012-04-30 15:52           ` Koen Kooi

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=4F1C586E.7030809@gmail.com \
    --to=derek.buitenhuis@gmail.com \
    --cc=poky@yoctoproject.org \
    --cc=raj.khem@gmail.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.