public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>, gdb@sourceware.org
Subject: Re: Disable libctf?
Date: Mon, 16 Nov 2020 18:44:34 -0300	[thread overview]
Message-ID: <fc7fc0ca-0ba0-f023-5db4-39fe6e4387f4@linaro.org> (raw)
In-Reply-To: <7030958c-b67e-4d12-8c1d-938f5cabbebf@embedded-brains.de>

On 11/16/20 6:37 PM, Sebastian Huber wrote:
> 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.
> 

Isn't the problem that GMP is missing? Or the pasted log may be misleading.

  reply	other threads:[~2020-11-16 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 21:37 Sebastian Huber
2020-11-16 21:44 ` Luis Machado [this message]
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=fc7fc0ca-0ba0-f023-5db4-39fe6e4387f4@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=gdb@sourceware.org \
    --cc=sebastian.huber@embedded-brains.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).