From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Zied Guermazi <zied.guermazi@trande.de>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/8] configure gdb build system for supporting btrace on arm processors
Date: Thu, 4 Mar 2021 16:35:02 +0000 [thread overview]
Message-ID: <DM5PR11MB169095D4A9765A22D0F5AF0BDE979@DM5PR11MB1690.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210226024602.55057-2-zied.guermazi@trande.de>
Hello Zied,
> gdb/ChangeLog
>
> * Makefile.in LIBOPENCSD_C_API: set the flag.
> * config.in LIBOPENCSD_C_API: undefine it if
> libopenocsd library is available.
This file is auto-generated.
> diff --git a/gdbsupport/common.m4 b/gdbsupport/common.m4
> index 3ed95dabc85..8d2f959e8f3 100644
> --- a/gdbsupport/common.m4
> +++ b/gdbsupport/common.m4
> @@ -186,6 +186,45 @@ AC_DEFUN([GDB_AC_COMMON], [
[...]
> + if test "$perf_event" != yes; then
> + if test "$" = yes; then
Should this be $with_arm_cs?
> + AC_MSG_ERROR([linux/perf_event.h missing or too old])
> + else
> + AC_MSG_WARN([linux/perf_event.h missing or too old; CoreSight Tracing will
> be unavailable.])
> + fi
> + fi
> +
> + AC_LIB_HAVE_LINKFLAGS([opencsd_c_api], [], [#include
> "opencsd/c_api/opencsd_c_api.h"], [ocsd_get_version();])
> + if test "$HAVE_LIBOPENCSD_C_API" != yes; then
> + if test "$" = yes; then
Also here.
> + AC_MSG_ERROR([libopencsd_c_api is missing or unusable])
> + else
> + AC_MSG_WARN([libopencsd_c_api is missing or unusable; CoreSight Tracing
> will be unavailable.])
> + fi
> + else
> + LIBS="$LIBS $LIBOPENCSD_C_API"
> + fi
> + fi
> +
> +
> BFD_SYS_PROCFS_H
> if test "$ac_cv_header_sys_procfs_h" = yes; then
> BFD_HAVE_SYS_PROCFS_TYPE(gregset_t)
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2021-03-04 16:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 2:45 [PATCH 0/8] extend branch tracing to use ARM CoreSight traces Zied Guermazi
2021-02-26 2:45 ` [PATCH 1/8] configure gdb build system for supporting btrace on arm processors Zied Guermazi
2021-03-04 16:35 ` Metzger, Markus T [this message]
2021-03-10 22:09 ` Zied Guermazi
2021-02-26 2:45 ` [PATCH 2/8] add btrace coresight related commands Zied Guermazi
2021-03-04 16:35 ` Metzger, Markus T
[not found] ` <8a71a9a3-ad14-b716-6d86-ece063061b02@trande.de>
2021-03-10 22:37 ` Zied Guermazi
2021-03-16 10:16 ` Metzger, Markus T
2021-03-19 15:21 ` Zied Guermazi
2021-02-26 2:45 ` [PATCH 3/8] start/stop btrace with coresight etm and parse etm buffer. nat independant Zied Guermazi
2021-03-04 16:35 ` Metzger, Markus T
2021-03-11 0:12 ` Zied Guermazi
2021-03-16 10:16 ` Metzger, Markus T
2021-03-19 15:29 ` Zied Guermazi
2021-03-29 14:01 ` Metzger, Markus T
2021-03-30 15:11 ` Zied Guermazi
2021-02-26 2:45 ` [PATCH 4/8] start/stop btrace with coresight etm and collect etm buffer on linux os Zied Guermazi
2021-02-26 2:45 ` [PATCH 5/8] fix issue: gdb hangs in the command following a commad returning with TARGET_WAITKIND_NO_HISTORY Zied Guermazi
2021-02-26 7:12 ` Aktemur, Tankut Baris
2021-03-10 20:39 ` Zied Guermazi
2021-02-26 2:46 ` [PATCH 6/8] add support for coresight btrace via remote protocol Zied Guermazi
2021-02-26 2:46 ` [PATCH 7/8] adapt btrace testcases for arm target Zied Guermazi
2021-02-26 2:46 ` [PATCH 8/8] document btrace support for arm targets using coresight etm traces Zied Guermazi
2021-02-26 7:36 ` Eli Zaretskii
2021-03-10 20:36 ` Zied Guermazi
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=DM5PR11MB169095D4A9765A22D0F5AF0BDE979@DM5PR11MB1690.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=zied.guermazi@trande.de \
/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).