From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] libiio: new package
Date: Wed, 7 Jan 2015 10:00:03 +0100 [thread overview]
Message-ID: <20150107100003.33c641db@free-electrons.com> (raw)
In-Reply-To: <54ACF478.4080509@analog.com>
Dear Paul Cercueil,
On Wed, 7 Jan 2015 09:55:20 +0100, Paul Cercueil wrote:
> Thanks for merging this patch - and thanks for the extra work.
>
> I see you added a dependency on thread support in the toolchain, is it
> because it breaks some builds if not set?
> The library in itself will work just fine on a system without threads,
> only the IIO Daemon requires threads, that's why I'm asking.
I honestly don't remember. You can try building with the base config
http://autobuild.buildroot.org/toolchains/configs/br-arm-full-nothread.config
and see what breaks (of course after removing the dependency on
threads).
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-07 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 9:34 [Buildroot] [PATCH v5] libiio: new package Paul Cercueil
2014-12-21 21:39 ` Thomas Petazzoni
2015-01-07 8:55 ` Paul Cercueil
2015-01-07 9:00 ` Thomas Petazzoni [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=20150107100003.33c641db@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