public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: Building GDB 15.0.91 on MinGW: CPPFLAGS and libctf
Date: Fri, 07 Jun 2024 22:56:12 +0300	[thread overview]
Message-ID: <86tti4edcz.fsf@gnu.org> (raw)
In-Reply-To: <87r0d8k0gc.fsf@tromey.com> (message from Tom Tromey on Fri, 07 Jun 2024 13:38:27 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: brobecker@adacore.com,  gdb-patches@sourceware.org
> Date: Fri, 07 Jun 2024 13:38:27 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> Hmm... no responses.  I'm somewhat disappointed, since I thought the
> Eli> pretest is important, as we want to release soon...
> 
> People are busy.

So am I.  Emacs 30 is about to enter the release cycle.  Still, I took
several hours of my non-existent free time to try building this
pretest, since Joel asked me to do that each time a pretest is
published.

> Eli> Where do I report libctf bugs?
> 
> Either the binutils product in bugzilla or you can email the patch to
> the binutils list.
> 
> Eli> Is it okay to install the above in the
> Eli> GDB Git repository?
> 
> Not without approval from the appropriate binutils maintainer.

Thanks, will do.

> You can also use --disable-libctf to skip it; I frequently do this.
> It's only useful in special situations anyway.

Yes, about that: I don't have babeltrace, and the configure script
says:

  babletrace support disabled; GDB is unable to read CTF data.

Does this mean libctf is not going to be used in this build?  If so,
why doesn't the configure script disable libctf automatically when
babletrace is not available?

  parent reply	other threads:[~2024-06-07 19:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01 15:59 GDB 15.0.91 available for testing Joel Brobecker
2024-06-06 20:16 ` Building GDB 15.0.91 on MinGW: CPPFLAGS Eli Zaretskii
2024-06-07 12:21   ` Building GDB 15.0.91 on MinGW: CPPFLAGS and libctf Eli Zaretskii
     [not found]     ` <87r0d8k0gc.fsf@tromey.com>
2024-06-07 19:56       ` Eli Zaretskii [this message]
2024-06-07 21:39         ` Tom Tromey
2024-06-08  6:10           ` Eli Zaretskii
2024-06-08  7:54     ` Eli Zaretskii
2024-06-06 20:20 ` Building GDB 15.0.91 on MinGW: gcore.c Eli Zaretskii
     [not found]   ` <87msnwk0du.fsf@tromey.com>
2024-06-08  7:25     ` Eli Zaretskii
2024-06-07 12:27 ` Building GDB 15.0.91 on MinGW: ui_out_emit_type<ui_out_type_tuple>::m_uiout Eli Zaretskii
     [not found]   ` <87ikykk07l.fsf@tromey.com>
2024-06-07 19:57     ` Eli Zaretskii
2024-06-07 12:34 ` Building GDB 15.0.91 on MinGW: libctf.la Eli Zaretskii
2024-06-08  7:56   ` Eli Zaretskii
2024-06-07 13:13 ` Building GDB 15.0.91 on MinGW: Problem with TUI Eli Zaretskii
     [not found]   ` <599928735.5136862.1717766505896@mail.yahoo.com>
2024-06-07 13:48     ` Eli Zaretskii

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=86tti4edcz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).