From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/openobex: disable on Blackfin
Date: Thu, 2 Nov 2017 11:38:39 +0100 [thread overview]
Message-ID: <20171102113839.07a5f135@windsurf> (raw)
In-Reply-To: <CAHXCMMK+CvjV8fYCE=gVg1iMeoZYppJiy0HfK8QJ8pck+U_oxA@mail.gmail.com>
Hello,
On Thu, 2 Nov 2017 09:01:28 +0100, Samuel Martin wrote:
> >> diff --git a/package/openobex/Config.in b/package/openobex/Config.in
> >> index e611b8d803..4a4dc214ef 100644
> >> --- a/package/openobex/Config.in
> >> +++ b/package/openobex/Config.in
> >> @@ -1,5 +1,6 @@
> >> config BR2_PACKAGE_OPENOBEX
> >> bool "openobex"
> >> + depends on !BR2_bfin
> >> help
> >> Free open source implementation of the Object Exchange (OBEX)
> >> protocol.
> >
> > What about the Config.in comment, and the reverse dependencies of
> > BR2_PACKAGE_OPENOBEX ?
>
> Well, I was not really sure about what to mention... and also wanted
> to heard Waldemar opinion.
I don't understand what you mean here. If you're adding a new
dependency to a package, you must:
- Propagate it to the Config.in comment of that package
- Propagate it to the reverse dependencies of that package
So I'm not sure how you can be "not really sure about what to mention".
You must add a "depends on !BR2_bfin" in the Config.in comment, and
then a depends on !BR2_bfin to all reverse dependencies of openobex,
including their Config.in comments. There is nothing to "mention".
But since Waldemar has submitted a patch to fix the actual problem in
uClibc, this is all moot :)
> FYI, this commit 53996bee433f09a91b12aa53b2be0f7d22c0acbe seems to fix
> a similar issue.
We should revert this commit once Waldemar fix is merged, and we have
rebuilt the toolchains.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-02 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 20:11 [Buildroot] [PATCH 1/4] package/openobex: disable on Blackfin Samuel Martin
2017-11-01 20:11 ` [Buildroot] [PATCH 2/4] package/opencv: fix build failure Samuel Martin
2017-11-02 12:32 ` Thomas Petazzoni
2017-11-01 20:11 ` [Buildroot] [PATCH 3/4] package/opencv: add hashes for patch and license files Samuel Martin
2017-11-02 12:33 ` Thomas Petazzoni
2017-11-01 20:11 ` [Buildroot] [PATCH 4/4] package/ussp-push: removed deprecated/no longer needed deps on openobex-bluez Samuel Martin
2017-11-02 13:18 ` Thomas Petazzoni
2017-11-02 21:34 ` Thomas Petazzoni
2017-11-01 22:23 ` [Buildroot] [PATCH 1/4] package/openobex: disable on Blackfin Thomas Petazzoni
2017-11-02 2:14 ` Waldemar Brodkorb
2017-11-02 8:07 ` Thomas Petazzoni
2017-11-02 8:01 ` Samuel Martin
2017-11-02 10:38 ` Thomas Petazzoni [this message]
2017-11-02 10:42 ` Samuel Martin
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=20171102113839.07a5f135@windsurf \
--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