Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ronan Loftus <rlf42@posteo.net>
To: buildroot@buildroot.org
Cc: Ronan Loftus <rlf42@posteo.net>
Subject: [Buildroot] [PATCH 1/1] package/readline: propagate CONF_OPTS to host build
Date: Sun, 19 Jul 2026 03:16:04 +0000	[thread overview]
Message-ID: <20260719031547.3512747-1-rlf42@posteo.net> (raw)

--with-shared-termcap-library is only applied to the target readline
because CONF_OPTS is not inherited by the host variant. The resulting
host libreadline.so.8 has no DT_NEEDED on ncurses/tinfo, leaving
termcap symbols (UP, BC, tgetent, ...) unresolved.

With recent binutils (--no-copy-dt-needed-entries), any process
loading this libreadline via LD_LIBRARY_PATH fails at startup. This
breaks fakeroot-based rootfs generation when host-gdb (which pulls
host-readline) is selected:

  /bin/sh: symbol lookup error: .../host/lib/libreadline.so.8:
  undefined symbol: UP

Reproduced on Arch Linux (gcc 16.1.1, binutils 2.46.1).

Signed-off-by: Ronan Loftus <rlf42@posteo.net>
---
 package/readline/readline.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/readline/readline.mk b/package/readline/readline.mk
index f69cbe45..8c49fab8 100644
--- a/package/readline/readline.mk
+++ b/package/readline/readline.mk
@@ -15,6 +15,7 @@ READLINE_CONF_OPTS = \
 	--disable-install-examples \
 	--with-curses \
 	--with-shared-termcap-library
+HOST_READLINE_CONF_OPTS = $(READLINE_CONF_OPTS)
 READLINE_LICENSE = GPL-3.0+
 READLINE_LICENSE_FILES = COPYING
 READLINE_CPE_ID_VENDOR = gnu
-- 
2.55.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

                 reply	other threads:[~2026-07-19  3:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260719031547.3512747-1-rlf42@posteo.net \
    --to=rlf42@posteo.net \
    --cc=buildroot@buildroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox