From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gnuradio: depends on shared libs
Date: Mon, 30 Mar 2015 19:59:34 +0300 [thread overview]
Message-ID: <20150330165934.GJ12479@tarshish> (raw)
In-Reply-To: <1427737015-12068-1-git-send-email-gwenj@trabucayre.com>
Hi Gwenhael Goavec-Merou,
On Mon, Mar 30, 2015 at 07:36:55PM +0200, Gwenhael Goavec-Merou wrote:
> From: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
>
> volk must be compiled with toolchain built with shared lib to avoid :
> attempted static link of dynamic object `../lib/libvolk.so.0.0.0'
>
> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
> ---
> package/gnuradio/Config.in | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/package/gnuradio/Config.in b/package/gnuradio/Config.in
> index 274afaa..bdf701c 100644
> --- a/package/gnuradio/Config.in
> +++ b/package/gnuradio/Config.in
> @@ -1,5 +1,6 @@
> -comment "gnuradio needs a toolchain w/ C++, IPV6, NPTL, largefile, wchar"
> +comment "gnuradio needs a toolchain w/ C++, IPV6, NPTL, largefile, wchar and shared libs"
> depends on BR2_USE_MMU
> + depends on BR2_STATIC_LIBS
> depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR || \
> !BR2_TOOLCHAIN_HAS_THREADS_NPTL || !BR2_LARGEFILE || \
> !BR2_INET_IPV6
Should add '|| BR2_STATIC_LIBS' to this list of ORed dependencies to get the
intended behaviour. Otherwise the comment will not be shown when
!BR2_STATIC_LIBS.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2015-03-30 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 17:36 [Buildroot] [PATCH 1/1] gnuradio: depends on shared libs Gwenhael Goavec-Merou
2015-03-30 16:59 ` Baruch Siach [this message]
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=20150330165934.GJ12479@tarshish \
--to=baruch@tkos.co.il \
--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