From: Waldemar Brodkorb <wbx@openadk.org>
To: Scott Fan <fancp2007@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/sqlite: fix configure options for readline/editline support
Date: Fri, 14 Feb 2025 09:08:15 +0100 [thread overview]
Message-ID: <Z6757/dNfhJcco7d@waldemar-brodkorb.de> (raw)
In-Reply-To: <20250214074235.917242-1-fancp2007@gmail.com>
Hi Scott,
Scott Fan wrote,
> The autosetup script will skip checking for readline.h when cross-compiling,
> which will cause line-editing support for the sqlite3 shell to always be "none".
>
> In this case, if the --editline option is provided, an error will be reported:
> ERROR: Explicit --editline failed to find a matching library.
>
> However, we can enable readline or editline support by specifying the CFLAGS
> and LDFLAGS values instead of having it handled automatically by the
> autosetup configure script.
>
> In addition, the libedit package actually depends on the ncurses package,
> just like the readline package. So when using the libedit package,
> also add the ncurses dependency.
Somehow it does not apply cleanly with git am:
Applying: package/sqlite: fix configure options for
readline/editline support
error: patch failed: package/sqlite/sqlite.mk:44
error: package/sqlite/sqlite.mk: patch does not apply
Patch failed at 0001 package/sqlite: fix configure options for
readline/editline support
Any idea?
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-14 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 2:14 [Buildroot] [PATCH] package/sqlite: fix configure options for readline/editline support Scott Fan
2025-02-14 7:42 ` [Buildroot] [PATCH v2] " Scott Fan
2025-02-14 8:08 ` Waldemar Brodkorb [this message]
2025-02-14 9:32 ` Waldemar Brodkorb
2025-02-15 2:51 ` Scott Fan
2025-02-17 2:47 ` Scott Fan
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=Z6757/dNfhJcco7d@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=fancp2007@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox