From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/libserial: bump to version 0.6.0rc2
Date: Sun, 23 Aug 2015 22:56:00 +0200 [thread overview]
Message-ID: <20150823225600.37bad21a@free-electrons.com> (raw)
In-Reply-To: <1438295004-5934-1-git-send-email-joerg.krause@embedded.rocks>
Dear J?rg Krause,
On Fri, 31 Jul 2015 00:23:24 +0200, J?rg Krause wrote:
> Also:
> * Update patch #1
> * Remove patch #2, fixed upstream
> * add new dependency to boost
> * use hashes from sourceforge
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> Changes in v2:
> * Fix selecting package boost (Thomas Petazzoni)
> ---
> .../libserial/0001-disable-python-bindings.patch | 21 +++++++++++----------
> .../libserial/0002-add-missing-header-include.patch | 15 ---------------
> package/libserial/Config.in | 8 ++++++--
> package/libserial/libserial.hash | 5 +++--
> package/libserial/libserial.mk | 3 ++-
> 5 files changed, 22 insertions(+), 30 deletions(-)
> delete mode 100644 package/libserial/0002-add-missing-header-include.patch
Applied to next after doing the following changes:
[Thomas:
- add locally calculated sha256 hash
- show the Config.in comment about toolchain dependencies only when
BR2_PACKAGE_BOOST_ARCH_SUPPORTS is set.]
Also, the SourceForge page of libserial indicates that the project has
now moved to Github: https://github.com/crayzeewulf/libserial/. If you
have the time to 1/ send a Buildroot patch to use Github as the
upstream rather than SourceForge and 2/ upstream a patch to make the
Python binding optional, it would be great.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-23 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 22:23 [Buildroot] [PATCH v2 1/1] package/libserial: bump to version 0.6.0rc2 Jörg Krause
2015-08-23 20:56 ` Thomas Petazzoni [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=20150823225600.37bad21a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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