Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAHP3WfM2efs35fvQ+uOjy2awWgKosAfA7FbeAob8k6GhBwZvng@mail.gmail.com>
In-Reply-To: <CAHP3WfM2efs35fvQ+uOjy2awWgKosAfA7FbeAob8k6GhBwZvng@mail.gmail.com>
From:   Russell Senior <russell@personaltelco.net>
Date:   Tue, 11 Jul 2023 21:51:47 -0700
Message-ID: <CAHP3WfMz1p4MHwwDGTeU6iyuPz3OhnoB2EZ62s4voZbjhBEocw@mail.gmail.com>
Subject: ell location bug/inconsistency with README
To:     linux-bluetooth@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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.

Thanks,

-- 
Russell Senior
russell@personaltelco.net