From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Buildroot Development <buildroot@buildroot.org>,
Peter Seiderer <ps.report@gmx.net>
Subject: Re: [Buildroot] [PATCH 2/2] package/ncurses: Also build termlib
Date: Fri, 2 Jan 2026 16:43:45 +0100 [thread overview]
Message-ID: <20260102164345.51d40b46@windsurf> (raw)
In-Reply-To: <20250920074707.584930-6-bagasdotme@gmail.com>
Hello,
Thanks for your patch!
On Sat, 20 Sep 2025 14:47:10 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> As a side effect of readline fix in previous commit, building host-gdb
> fails with undefined reference to ncurses error:
>
> 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
Since host-gdb builds fine for most people, there must be something
specific to your environment. Could you provide the details of your
host distribution + the exact Buildroot version + minimal Buildroot
defconfig that exhibits the issue so that people can reproduce ?
To be honest, I don't pretend to fully grasp the interactions between
readline, ncurses, termlib, etc. So if you want patches to be merged,
they need to come with detailed and convincing explanations :-)
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-02 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 7:47 [Buildroot] [PATCH 0/2] Fix undefined reference errors on SDK tarball build Bagas Sanjaya
2025-09-20 7:47 ` [Buildroot] [PATCH 1/2] package/readline: Fix sdk rootfs tarball generation Bagas Sanjaya
2026-01-02 15:41 ` Thomas Petazzoni via buildroot
2025-09-20 7:47 ` [Buildroot] [PATCH 2/2] package/ncurses: Also build termlib Bagas Sanjaya
2026-01-02 15:43 ` Thomas Petazzoni via buildroot [this message]
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=20260102164345.51d40b46@windsurf \
--to=buildroot@buildroot.org \
--cc=bagasdotme@gmail.com \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.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 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.