Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Cc: tom_rini@mentor.com
Subject: [2011.03-maintenance] libdca build fix
Date: Thu,  8 Sep 2011 10:43:50 +0000	[thread overview]
Message-ID: <cover.1315478126.git.obi@opendreambox.org> (raw)

Hi Tom,

please apply this build fix, which was cherry-picked from master
4f4ed88bc7caa3d2b0b44ae2f51907aa9e68fc1b.

The following changes since commit bc8ddbf7944f82383936d88379619aa46c3954a2:

  binutils-2.18: fix checksums (2011-09-05 17:43:27 +0200)

are available in the git repository at:
  git://git.opendreambox.org/git/obi/openembedded.git 2011.03-maintenance
  http://cgit.opendreambox.org/obi/openembedded.git/log/?h=2011.03-maintenance

Andreas Oberritter (1):
  libdca: fix sed failing on unpack

 recipes/libdca/libdca_0.0.5-3.bb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

-- 
1.7.2.5




             reply	other threads:[~2011-09-08 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 10:43 Andreas Oberritter [this message]
2011-09-09 20:52 ` [2011.03-maintenance] libdca build fix Tom Rini

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=cover.1315478126.git.obi@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=tom_rini@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox