From: Scott Fan <fancp2007@gmail.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Julien Olivain <ju.o@free.fr>,
buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] package/sqlite: fix build issue since bump to 3.49.0
Date: Fri, 14 Feb 2025 15:49:00 +0800 [thread overview]
Message-ID: <CAFkzVZa7ns0bBWcjVPLv7BkWLnxmJXKAcTK5-np-m8cUwXa1cQ@mail.gmail.com> (raw)
In-Reply-To: <Z668GPE9/vZROlga@waldemar-brodkorb.de>
Hi Waldemar,
I have sent a new patch (v2), see the link below:
https://patchwork.ozlabs.org/project/buildroot/patch/20250214074235.917242-1-fancp2007@gmail.com/
With this patch, I tested the following defconfig, it's ok.
$ cat defconfig
BR2_aarch64=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_ASTERISK=y
Could you take a moment to test this patch for your work? thanks.
Scott Fan
On Fri, Feb 14, 2025 at 11:44 AM Waldemar Brodkorb <wbx@openadk.org> wrote:
>
> Hi Scott,
> Scott Fan wrote,
>
> > Hi Waldemar,
> >
> > Thank you for your feedback.
> >
> > I have sent a new patch to fix it, see the link below:
> > https://patchwork.ozlabs.org/project/buildroot/patch/20250214021416.392363-1-fancp2007@gmail.com/
> >
> > Could you take a moment to test this patch for your work? thanks.
>
> Thanks for the fast patch. But it now fails when compiling shell.c:
> /home/wbx/buildroot/output/host/bin/aarch64-buildroot-linux-gnu-gcc -o sqlite3 \
> shell.c sqlite3.c \
> -I. -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_OMIT_JSON -DSQLITE_THREADSAFE=1 -DHAVE_READLINE=1 -DSQLITE_HAVE_ZLIB=1 -DSQLITE_OMIT_READLINE_COMPLETION \
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g0 -D_FORTIFY_SOURCE=1 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/home/wbx/buildroot/output/host/aarch64-buildroot-linux-gnu/sysroot/usr/include \
> -Wl,-rpath,/usr/lib -lm -lz -ledit -lncurses
> shell.c:151:11: fatal error: readline/readline.h: No such file or directory
> 151 | # include <readline/readline.h>
> | ^~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
>
> The configure command puts out:
> NOTE: the local libedit but uses <readline/readline.h> so we
> will compile with -DHAVE_READLINE=1 but will link with
> libedit.
>
> thanks for working on it.
>
> 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 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:50 [Buildroot] [PATCH] package/sqlite: fix build issue since bump to 3.49.0 Scott Fan
2025-02-12 14:24 ` Baruch Siach via buildroot
2025-02-12 15:47 ` Fiona Klute via buildroot
2025-02-13 3:59 ` Scott Fan
2025-02-13 6:39 ` Roy Kollen Svendsen
2025-02-13 8:19 ` Scott Fan
2025-02-13 14:16 ` Scott Fan
2025-02-13 4:50 ` [Buildroot] [PATCH v2] " Scott Fan
2025-02-13 17:42 ` Fiona Klute via buildroot
2025-02-13 21:37 ` Julien Olivain
2025-02-13 22:46 ` Waldemar Brodkorb
2025-02-14 2:23 ` Scott Fan
2025-02-14 3:44 ` Waldemar Brodkorb
2025-02-14 7:49 ` Scott Fan [this message]
2025-02-18 20:40 ` [Buildroot] [PATCH] " Julien Olivain
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=CAFkzVZa7ns0bBWcjVPLv7BkWLnxmJXKAcTK5-np-m8cUwXa1cQ@mail.gmail.com \
--to=fancp2007@gmail.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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.