public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Jose E. Marchesi <jemarch@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/configure: regenerate Date: Tue, 15 Nov 2022 19:33:54 +0000 (GMT) [thread overview] Message-ID: <20221115193354.B0CB3392AC21@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=02dbc2b9e76ad0cd452563c3ee7a8b1571eed89b commit 02dbc2b9e76ad0cd452563c3ee7a8b1571eed89b Author: Jose E. Marchesi <jose.marchesi@oracle.com> Date: Tue Nov 15 20:26:30 2022 +0100 gdb/configure: regenerate The commit bbaabc767a4293492817a0840819aef2768cce90 introduced an incorrect thunk for the `configure' script. This patch regenerates configure by calling autoreconf. Diff: --- gdb/configure | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gdb/configure b/gdb/configure index 712d22e75b3..23e6b7160ec 100755 --- a/gdb/configure +++ b/gdb/configure @@ -28548,7 +28548,8 @@ WIN32LIBS="$WIN32LIBS $WIN32APILIBS" # always want our bfd. CFLAGS="-I${srcdir}/../include -I../bfd -I${srcdir}/../bfd $CFLAGS" LDFLAGS="-L../bfd -L../libiberty" - LIBS="-lbfd -liberty $LIBS" + intl=`echo $LIBINTL | sed 's,${top_builddir}/,,g'` + LIBS="-lbfd -liberty $intl $LIBS" CC="./libtool --quiet --mode=link $CC" { $as_echo "$as_me:${as_lineno-$LINENO}: checking for ELF support in BFD" >&5 $as_echo_n "checking for ELF support in BFD... " >&6; } @@ -28664,7 +28665,8 @@ fi # always want our bfd. CFLAGS="-I${srcdir}/../include -I../bfd -I${srcdir}/../bfd $CFLAGS" LDFLAGS="-L../bfd -L../libiberty" - LIBS="-lbfd -liberty $LIBS" + intl=`echo $LIBINTL | sed 's,${top_builddir}/,,g'` + LIBS="-lbfd -liberty $intl $LIBS" CC="./libtool --quiet --mode=link $CC" { $as_echo "$as_me:${as_lineno-$LINENO}: checking for Mach-O support in BFD" >&5 $as_echo_n "checking for Mach-O support in BFD... " >&6; }
reply other threads:[~2022-11-15 19:33 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=20221115193354.B0CB3392AC21@sourceware.org \ --to=jemarch@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).