From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/protobuf: needs gcc >= 4.5
Date: Sun, 7 May 2017 15:20:52 +0200 [thread overview]
Message-ID: <20170507152052.011081f0@free-electrons.com> (raw)
In-Reply-To: <20170507131652.22322-1-romain.naour@gmail.com>
Hello,
On Sun, 7 May 2017 15:16:52 +0200, Romain Naour wrote:
> diff --git a/package/protobuf-c/Config.in b/package/protobuf-c/Config.in
> index a32e6cd..6f916c5 100644
> --- a/package/protobuf-c/Config.in
> +++ b/package/protobuf-c/Config.in
> @@ -4,12 +4,14 @@ config BR2_PACKAGE_PROTOBUF_C
> depends on BR2_TOOLCHAIN_HAS_THREADS
> # host-protobuf only builds on certain architectures
> depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
> + depends on BR2_HOST_GCC_AT_LEAST_4_5 # host-protobuf
You're adding a new dependency to protobuf-c, but protobuf-c is also
selected by a few packages:
package/collectd/Config.in: select BR2_PACKAGE_PROTOBUF_C
package/riemann-c-client/Config.in: select BR2_PACKAGE_PROTOBUF_C
You also need to propagate the dependency to these packages.
Generally speaking, when propagating new dependencies, you should not
only take care of first level reverse dependencies, but also
recursively take care of all reverse dependencies.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-07 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 13:16 [Buildroot] [PATCH] package/protobuf: needs gcc >= 4.5 Romain Naour
2017-05-07 13:20 ` Thomas Petazzoni [this message]
2017-05-07 13:33 ` Romain Naour
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=20170507152052.011081f0@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