public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] sim: fix readline linkage Date: Sat, 5 Nov 2022 14:23:36 +0000 (GMT) [thread overview] Message-ID: <20221105142336.DF0A2385843A@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5a9886170b3bc9027ec72ab425fb0e3d4a1aa330 commit 5a9886170b3bc9027ec72ab425fb0e3d4a1aa330 Author: Mike Frysinger <vapier@gentoo.org> Date: Sat Nov 5 21:21:31 2022 +0700 sim: fix readline linkage Now that we link programs in the top dir instead of the arch subdir, update the readline library path to be relative to the top dir. Diff: --- sim/configure | 2 +- sim/m4/sim_ac_platform.m4 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sim/configure b/sim/configure index d8b734e59eb..0a0eb6dbf0c 100755 --- a/sim/configure +++ b/sim/configure @@ -13446,7 +13446,7 @@ fi if test -r ../readline/Makefile; then - READLINE_LIB=../../readline/readline/libreadline.a + READLINE_LIB=../readline/readline/libreadline.a READLINE_CFLAGS='-I$(READLINE_SRC)/..' else { $as_echo "$as_me:${as_lineno-$LINENO}: checking for readline in -lreadline" >&5 diff --git a/sim/m4/sim_ac_platform.m4 b/sim/m4/sim_ac_platform.m4 index 467987e11e7..abfb2bd9e6e 100644 --- a/sim/m4/sim_ac_platform.m4 +++ b/sim/m4/sim_ac_platform.m4 @@ -190,7 +190,7 @@ AC_SUBST(TERMCAP_LIB) dnl We prefer the in-tree readline. Top-level dependencies make sure dnl src/readline (if it's there) is configured before src/sim. if test -r ../readline/Makefile; then - READLINE_LIB=../../readline/readline/libreadline.a + READLINE_LIB=../readline/readline/libreadline.a READLINE_CFLAGS='-I$(READLINE_SRC)/..' else AC_CHECK_LIB(readline, readline, READLINE_LIB=-lreadline,
reply other threads:[~2022-11-05 14:23 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=20221105142336.DF0A2385843A@sourceware.org \ --to=vapier@sourceware.org \ --cc=gdb-cvs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).