From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] gnuradio: fix compilation with cmake-3.5
Date: Tue, 22 Mar 2016 18:25:24 +0100 [thread overview]
Message-ID: <4pb8scxncf.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20160322181159.600222f8@x230.trabucayre.com
Am Tue, 22 Mar 2016 18:11:59 +0100 schrieb gwenhael.goavec:
> according to FindBoost.cmake boost_threads depends on atomic & chrono. I
> think (I'm test before sent a patch) it's better to add the missing
> dependencies. No ?
Hi,
I have no idea about the internal dependencies of boost. According to the
commit message CMake now recognizes "indirect dependencies", with them
gnuradio compiles without problems, like it did with cmake 3.4.3. So we
have too choices:
- add dependencies to gnuradio without being sure they are really needed
- live with "indirect dependencies" in boost without knowing whether they
cause harm or not.
Regards, Bernd
next prev parent reply other threads:[~2016-03-22 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 11:31 [Buildroot] [PATCH v2 1/1] gnuradio: fix compilation with cmake-3.5 Gwenhael Goavec-Merou
2016-03-22 16:50 ` Bernd Kuhls
2016-03-22 17:11 ` gwenhael.goavec
2016-03-22 17:25 ` Bernd Kuhls [this message]
2016-03-23 7:57 ` gwenhael.goavec
2016-03-22 19:19 ` Thomas Petazzoni
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=4pb8scxncf.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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