From: Rudi Heitbaum <rudi@heitbaum.com>
To: Russell Senior <russell@personaltelco.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: ell location bug/inconsistency with README
Date: Wed, 12 Jul 2023 10:10:20 +0000 [thread overview]
Message-ID: <ZK58DFhBZ9kVA1ts@53c778cd7e6b> (raw)
In-Reply-To: <CAHP3WfMz1p4MHwwDGTeU6iyuPz3OhnoB2EZ62s4voZbjhBEocw@mail.gmail.com>
On Tue, Jul 11, 2023 at 09:51:47PM -0700, Russell Senior wrote:
> I mentioned this on the irc channel recently, thought I'd escalate to
> the mailing list. Also, I am a total newbie with bluez, so please
> pardon what appears like and actually is pathetic ignorance.
>
> I am building bluez 5.68 on OpenWrt and found that a recent commit
> 1106b28be8 seems to have made the configure script look for ell
> whether or not --enable-mesh or --enable-btpclient are used (I'm not
> using them), in contrast to the language in the README:
>
> "When neither --enable-mesh nor --enable-btpclient is specified, then this
> part is irrelevant and Embedded Linux library is not required."
>
> I worked around it by patching out the part of configure that errors
> on not finding ell, but this seems like a bug either in the code or
> the README.
Hi Russell,
Were you cross compiling? If so. This should fix the compile:
https://patchwork.kernel.org/project/bluetooth/patch/20230701041252.139338-1-rudi@heitbaum.com/
https://lore.kernel.org/linux-bluetooth/20230701041252.139338-1-rudi@heitbaum.com/
Regards
Rudi
> Thanks,
>
> --
> Russell Senior
> russell@personaltelco.net
prev parent reply other threads:[~2023-07-12 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHP3WfM2efs35fvQ+uOjy2awWgKosAfA7FbeAob8k6GhBwZvng@mail.gmail.com>
2023-07-12 4:51 ` ell location bug/inconsistency with README Russell Senior
2023-07-12 10:10 ` Rudi Heitbaum [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=ZK58DFhBZ9kVA1ts@53c778cd7e6b \
--to=rudi@heitbaum.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=russell@personaltelco.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 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.