Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/dbus-cpp: fix cross-compilation
Date: Tue, 21 Mar 2017 23:07:18 +0100	[thread overview]
Message-ID: <20170321230718.3664467e@free-electrons.com> (raw)
In-Reply-To: <1490132039-29054-1-git-send-email-yann.morin.1998@free.fr>

Hello,

On Tue, 21 Mar 2017 22:33:59 +0100, Yann E. MORIN wrote:
> dbus-cpp has an ugly hack to not cross-build the tools when it detects
> cross-compilation.
> 
> However, we already have a host variant that builds those tools (and we
> anyway don't seem to need them to begin with).
> 
> Drop our patch that propagates the CXXFLAGS/LDFLAGS_FOR_BUILD. Replace
> with a patch to cross-compile the tools.
> 
> Fixes:
>     http://autobuild.buildroot.org/results/110/1100539caae6ef62c61a3b96bc54f7c0a215cc62/
>     and many, many more.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> 
> ---
> Changes v1 -> v2:
>   - add missing commit log to patch  (Thomas)
> ---
>  package/dbus-cpp/0002-cross-compile-tools.patch    | 34 ++++++++++++++++++++++
>  .../dbus-cpp/0002-cxxflags-ldflags-for-build.patch | 32 --------------------
>  2 files changed, 34 insertions(+), 32 deletions(-)
>  create mode 100644 package/dbus-cpp/0002-cross-compile-tools.patch
>  delete mode 100644 package/dbus-cpp/0002-cxxflags-ldflags-for-build.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2017-03-21 22:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 21:33 [Buildroot] [PATCHv2] package/dbus-cpp: fix cross-compilation Yann E. MORIN
2017-03-21 22:07 ` Thomas Petazzoni [this message]
2017-03-30 22:33 ` Peter Korsgaard

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=20170321230718.3664467e@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