From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: gdb@sourceware.org
Subject: Disable libctf?
Date: Mon, 16 Nov 2020 22:37:43 +0100 [thread overview]
Message-ID: <7030958c-b67e-4d12-8c1d-938f5cabbebf@embedded-brains.de> (raw)
Hello,
a recent change broke the GDB build on my FreeBSD test machine:
gmake[2]: Leaving directory
'/usr/home/user/rtems-source-builder/rtems/build/aarch64-rtems6-gdb-119e99b-x86_64-freebsd12.1-1/build/libctf'
configure: WARNING: libdebuginfod is missing or unusable; some features
may be unavailable.
checking libunwind-ia64.h usability... no
[...]
checking for library containing dlopen... none required
checking whether to use expat... yes
checking for libexpat... yes
checking how to link with libexpat...
/usr/home/user/rtems-source-builder/rtems/build/tmp/sb-1001/6/rtems-aarch64/usr/local/rtems/6/lib/libexpat.a
checking for XML_StopParser... yes
checking for libgmp... no
configure: error: GMP is missing or unusable
I guess I don't need libctf to debug non-Linux embedded systems? I tried
to use --disable-libctf, but this didn't work.
--
embedded brains GmbH
Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
Phone: +49-89-18 94 741 - 16
Fax: +49-89-18 94 741 - 08
PGP: Public key available on request.
embedded brains GmbH
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/
next reply other threads:[~2020-11-16 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 21:37 Sebastian Huber [this message]
2020-11-16 21:44 ` Luis Machado
2020-11-17 7:43 ` Sebastian Huber
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=7030958c-b67e-4d12-8c1d-938f5cabbebf@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gdb@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: 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).