On 21 May 2024, at 22:55, Khem Raj wrote:
> This kinds of errors are something I worry about, where configure may
> silently decide to take another path for wrong or
> insufficient tests. I wonder if we have a way to cache and compare
> configure outcomes.
buildhistory-diff is the easy solution (
On Tue, May 21, 2024 at 8:17 AM Ross Burton via lists.openembedded.org
wrote:
>
> The code fragment used to detect readline in cross builds doesn't compile
> cleanly with GCC 14.1, so readline is never enabled.
>
> Add missing includes so the test works, and readline can be enabled.
>
> Signed-off
Please include a link to the submission.
Alex
On Tue 21. May 2024 at 17.17, Ross Burton via lists.openembedded.org
wrote:
> The code fragment used to detect readline in cross builds doesn't compile
> cleanly with GCC 14.1, so readline is never enabled.
>
> Add missing includes so the test works
The code fragment used to detect readline in cross builds doesn't compile
cleanly with GCC 14.1, so readline is never enabled.
Add missing includes so the test works, and readline can be enabled.
Signed-off-by: Ross Burton
---
...001-m4-readline-add-missing-includes.patch | 38 +
