From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Cc: nickc@redhat.com, Indu Bhagat <indu.bhagat@oracle.com>
Subject: [PATCH,V2 11/15] libctf: add libsframe to LDFLAGS and LIBS
Date: Mon, 17 Oct 2022 15:16:08 -0700 [thread overview]
Message-ID: <20221017221612.495324-12-indu.bhagat@oracle.com> (raw)
In-Reply-To: <20221017221612.495324-1-indu.bhagat@oracle.com>
[No changes in V2]
bfd now depends on libsframe.
ChangeLog:
* libctf/configure.ac:
* libctf/configure: Regenerated
---
libctf/configure | 4 ++--
libctf/configure.ac | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/libctf/configure b/libctf/configure
index 176b3d6b918..abe4cfe1eff 100755
--- a/libctf/configure
+++ b/libctf/configure
@@ -13218,9 +13218,9 @@ OLD_LIBS=$LIBS
# always want our bfd.
CFLAGS="-I${srcdir}/../include -I../bfd -I${srcdir}/../bfd $CFLAGS"
ZLIBDIR=`echo $zlibdir | sed 's,\$(top_builddir)/,,g'`
-LDFLAGS="-L../bfd -L../libiberty $ZLIBDIR $LDFLAGS"
+LDFLAGS="-L../bfd -L../libiberty -L../libsframe/.libs/ $ZLIBDIR $LDFLAGS"
intl=`echo $LIBINTL | sed 's,${top_builddir}/,,g'`
-LIBS="-lbfd -liberty -lz $ZSTD_LIBS $intl $LIBS"
+LIBS="-lbfd -liberty -lz -lsframe $ZSTD_LIBS $intl $LIBS"
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ELF support in BFD" >&5
$as_echo_n "checking for ELF support in BFD... " >&6; }
if ${ac_cv_libctf_bfd_elf+:} false; then :
diff --git a/libctf/configure.ac b/libctf/configure.ac
index 2e2ccf4b624..72b2ed7ea31 100644
--- a/libctf/configure.ac
+++ b/libctf/configure.ac
@@ -88,9 +88,9 @@ OLD_LIBS=$LIBS
# always want our bfd.
CFLAGS="-I${srcdir}/../include -I../bfd -I${srcdir}/../bfd $CFLAGS"
ZLIBDIR=`echo $zlibdir | sed 's,\$(top_builddir)/,,g'`
-LDFLAGS="-L../bfd -L../libiberty $ZLIBDIR $LDFLAGS"
+LDFLAGS="-L../bfd -L../libiberty -L../libsframe/.libs/ $ZLIBDIR $LDFLAGS"
intl=`echo $LIBINTL | sed 's,${top_builddir}/,,g'`
-LIBS="-lbfd -liberty -lz $ZSTD_LIBS $intl $LIBS"
+LIBS="-lbfd -liberty -lz -lsframe $ZSTD_LIBS $intl $LIBS"
AC_CACHE_CHECK([for ELF support in BFD], ac_cv_libctf_bfd_elf,
[AC_TRY_LINK([#include <stdlib.h>
#include <string.h>
--
2.37.2
next prev parent reply other threads:[~2022-10-17 22:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 22:15 [PATCH,V2 00/15] Definition and support for SFrame unwind format Indu Bhagat
2022-10-17 22:15 ` [PATCH,V2 01/15] sframe.h: Add SFrame format definition Indu Bhagat
2022-10-17 22:15 ` [PATCH,V2 02/15] gas: add new command line option --gsframe Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 03/15] gas: generate .sframe from CFI directives Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 04/15] gas: testsuite: add new tests for SFrame unwind info Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 05/15] libsframe: add the SFrame library Indu Bhagat
2022-10-27 18:07 ` Mike Frysinger
2022-10-30 7:37 ` Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 06/15] bfd: linker: merge .sframe sections Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 07/15] readelf/objdump: support for SFrame section Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 08/15] unwinder: generate backtrace using SFrame format Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 09/15] unwinder: Add SFrame unwinder tests Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 10/15] gdb: sim: buildsystem changes to accommodate libsframe Indu Bhagat
2022-10-27 17:36 ` [PATCH, V2 " Mike Frysinger
2022-10-30 7:16 ` Indu Bhagat
2022-10-17 22:16 ` Indu Bhagat [this message]
2022-10-17 22:16 ` [PATCH,V2 12/15] src-release.sh: Add libsframe Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 13/15] binutils/NEWS: add text for SFrame support Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 14/15] gas/NEWS: add text about new command line option and " Indu Bhagat
2022-10-17 22:16 ` [PATCH,V2 15/15] doc: add SFrame spec file Indu Bhagat
2022-10-21 10:52 ` [PATCH,V2 00/15] Definition and support for SFrame unwind format Nick Clifton
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=20221017221612.495324-12-indu.bhagat@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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 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).