From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Buildroot Development <buildroot@buildroot.org>
Subject: Re: [Buildroot] libreadline undefined symbol error when generating rootfs tarball
Date: Wed, 17 Sep 2025 12:20:22 +0700 [thread overview]
Message-ID: <aMpFFo96JmNi24Zq@archie.me> (raw)
In-Reply-To: <20250916084217.4db9aa85@pc-1>
[-- Attachment #1.1: Type: text/plain, Size: 2130 bytes --]
On Tue, Sep 16, 2025 at 08:42:17AM +0200, Peter Seiderer wrote:
> The following patch fixed the problem for me:
>
> diff --git a/package/readline/readline.mk b/package/readline/readline.mk
> index f69cbe45e2..078607a0c5 100644
> --- a/package/readline/readline.mk
> +++ b/package/readline/readline.mk
> @@ -15,6 +15,10 @@ READLINE_CONF_OPTS = \
> --disable-install-examples \
> --with-curses \
> --with-shared-termcap-library
> +HOST_READLINE_CONF_OPTS = \
> + --disable-install-examples \
> + --with-curses \
> + --with-shared-termcap-library
> READLINE_LICENSE = GPL-3.0+
> READLINE_LICENSE_FILES = COPYING
> READLINE_CPE_ID_VENDOR = gnu
Applying your patch, I get another build error (this time on gdb):
```
CXX init.o
CXXLD gdb
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `tgoto@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `UP@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `tgetent@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `tgetnum@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `PC@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `tgetstr@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `tgetflag@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `BC@NCURSES6_TINFO_5.0.19991023'
/usr/bin/ld: /home/bagas/repo/buildroot/output/host/lib/libreadline.so: undefined reference to `tputs@NCURSES6_TINFO_5.0.19991023'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:2232: gdb] Error 1
```
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-09-17 5:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 2:11 [Buildroot] libreadline undefined symbol error when generating rootfs tarball Bagas Sanjaya
2025-09-16 6:42 ` Peter Seiderer via buildroot
2025-09-17 5:20 ` Bagas Sanjaya [this message]
2025-09-17 15:20 ` Peter Seiderer via buildroot
2025-09-18 0:28 ` Bagas Sanjaya
2025-09-18 6:52 ` Peter Seiderer via buildroot
2025-09-18 22:18 ` Bagas Sanjaya
2025-09-19 14:20 ` Peter Seiderer via buildroot
2025-09-20 7:05 ` Bagas Sanjaya
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=aMpFFo96JmNi24Zq@archie.me \
--to=bagasdotme@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
/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