From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org, johan.hedberg@gmail.com
Subject: Re: bluez-4.97: check dependnecy
Date: Wed, 28 Dec 2011 09:36:11 +0100 [thread overview]
Message-ID: <4EFAD4FB.4030909@visionsystems.de> (raw)
In-Reply-To: <1324659935.1965.259.camel@aeonflux>
Hi Marcel,
>> I was cross compiling bluez-4.97 under Buildroot and with the same configuration as for 4.96 configure failed by not being able to find check framework. Could this dependency be dropped if I don't want to compile tests? I mean it doesn't make much sense using check on x86 build host for arm binaries.
> yes, it can be dropped. We only need that for development. Care to send
> a patch for it.
I've seen and tested your commit regarding this issue. It work perfectly. Thanks.
Yegor
next prev parent reply other threads:[~2011-12-28 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 10:30 bluez-4.97: check dependnecy Yegor Yefremov
2011-12-23 17:05 ` Marcel Holtmann
2011-12-28 8:36 ` Yegor Yefremov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-02 20:50 nello martuscielli
2012-01-02 20:58 ` nello martuscielli
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=4EFAD4FB.4030909@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.