All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Which package for bluetooth management?
Date: Thu, 5 May 2016 23:29:20 +0200	[thread overview]
Message-ID: <572BBB30.9090901@gmail.com> (raw)
In-Reply-To: <20160505142533.67f8e473@free-electrons.com>

Il 05/05/2016 14:25, Thomas Petazzoni ha scritto:
> I think it does, see https://patchwork.ozlabs.org/patch/612073/. Thomas 

I apologize, I haven't yet much knowledge about applying patches.
This is what I did:

$git pull
$git apply --stat 
v2-2-2-qt5connectivity-add-bluez5_utils-option-for-QtBluetooth-submodule.patch
$git apply --check 
v2-2-2-qt5connectivity-add-bluez5_utils-option-for-QtBluetooth-submodule.patch

but I got:

error: patch non riuscita: package/qt5/qt5connectivity/Config.in:4
error: package/qt5/qt5connectivity/Config.in: la patch non pu? essere 
applicata
error: patch non riuscita: package/qt5/qt5connectivity/qt5connectivity.mk:20
error: package/qt5/qt5connectivity/qt5connectivity.mk: la patch non pu? 
essere applicata

Thus I opened the file package/qt5/qt5connectivity/Config.in and in fact 
I see a content very different from the "old version" reported in the patch.

My file:

config BR2_PACKAGE_QT5CONNECTIVITY
     bool "qt5connectivity"
     select BR2_PACKAGE_BLUEZ_UTILS
     select BR2_PACKAGE_QT5BASE
     select BR2_PACKAGE_QT5BASE_CONCURRENT
     select BR2_PACKAGE_QT5BASE_DBUS
     depends on !BR2_STATIC_LIBS # bluez_utils
     depends on BR2_USE_WCHAR # bluez_utils
     depends on BR2_TOOLCHAIN_HAS_THREADS # bluez_utils
     depends on BR2_USE_MMU # bluez_utils

what the patch expects:

select BR2_PACKAGE_QT5BASE_CONCURRENT
  	select BR2_PACKAGE_QT5BASE_DBUS
  	depends on !BR2_STATIC_LIBS
- depends on BR2_PACKAGE_NEARD || BR2_PACKAGE_BLUEZ_UTILS
+ depends on BR2_PACKAGE_NEARD || BR2_PACKAGE_BLUEZ_UTILS || 
BR2_PACKAGE_BLUEZ5_UTILS

It seems I have an outdated file, but it's not enough git pull to sync 
with the latest version?
By the way I'm running this one: Buildroot 2016.05-git-01197-gda433d6-dirty

Is there a way to understand on which version the patch was created against?

Thanks for the support
Marco

  parent reply	other threads:[~2016-05-05 21:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 20:55 [Buildroot] Which package for bluetooth management? Marco Trapanese
2016-05-04 22:40 ` Arnout Vandecappelle
2016-05-05  6:41   ` Marco Trapanese
2016-05-05  7:54     ` Marco Trapanese
2016-05-05 12:25       ` Thomas Petazzoni
2016-05-05 12:29         ` Marco Trapanese
2016-05-05 21:29         ` Marco Trapanese [this message]
2016-05-05 21:37           ` Thomas Petazzoni
2016-05-05 21:47             ` Marco Trapanese
2016-05-07  7:32         ` Marco Trapanese
2016-05-07 23:41           ` Arnout Vandecappelle
2016-05-08  5:52             ` Thomas Petazzoni
2016-05-08  9:09             ` Marco Trapanese

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=572BBB30.9090901@gmail.com \
    --to=marcotrapanese@gmail.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 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.