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;
Date:   Wed, 12 Jul 2023 10:10:20 +0000
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
Message-ID: <ZK58DFhBZ9kVA1ts@53c778cd7e6b>
References: <CAHP3WfM2efs35fvQ+uOjy2awWgKosAfA7FbeAob8k6GhBwZvng@mail.gmail.com>
 <CAHP3WfMz1p4MHwwDGTeU6iyuPz3OhnoB2EZ62s4voZbjhBEocw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHP3WfMz1p4MHwwDGTeU6iyuPz3OhnoB2EZ62s4voZbjhBEocw@mail.gmail.com>
Precedence: bulk

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