Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christian Biesinger <cbiesinger@google.com>,
	Tom Tromey <tromey@adacore.com>,
	simon.marchi@polymtl.ca, Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Building today's snapshot of GDB with MinGW
Date: Tue, 30 Jun 2020 17:09:00 +0300	[thread overview]
Message-ID: <83wo3ozlvn.fsf@gnu.org> (raw)
In-Reply-To: <CAPTJ0XEokO0Ht787+19d2yWF3cxqtzv+q0RqKo+JoENuhxaMGg@mail.gmail.com> (message from Christian Biesinger on Mon, 29 Jun 2020 15:36:50 -0500)

> From: Christian Biesinger <cbiesinger@google.com>
> Date: Mon, 29 Jun 2020 15:36:50 -0500
> Cc: gdb-patches <gdb-patches@sourceware.org>
> 
> > 1. The configure script doesn't allow --with-static-standard-libraries
> > when GDB is built with source-highlight.  Is this limitation going to
> > stay (and if so, why), or could it be lifted?  (I needed to hack the
> > configure script to get past the error message.)
> 
> Looks like this was discussed before at
> https://sourceware.org/pipermail/gdb-patches/2020-April/167388.html,
> no real outcome AFAICT

Tom, could you please share your views on this?  You seemed to be
saying there that we must link libstdc++ dynamically to support
exceptions thrown by source-highlight, but could you perhaps add more
details about the reasons?  Also, do the problems you had in mind
affect GDB that is linked statically with source-highlight, and if
not, could we modify the configure script to allow that with
"-static-libstdc++"?

> > 2. Building in libctf produces the same errors I reported back in
> > February for GDB 9.1.  I thought the libctf developer fixed them
> > up-stream (or was I dreaming?), so why isn't the fix in our
> > repository?  I fixed those exactly as I fixed them for GDB 9.1.
> 
> So reading https://sourceware.org/bugzilla/show_bug.cgi?id=25155, Nick
> mentioned an RFC patch, but I can't tell if that landed.

Joel, should I install the same libctf patches we had in
gdb-9.1-branch in the current master?  Or would you like to talk to
the upstream maintainer first?

> > 3. "make TAGS" in the gdb/ directory fails because HFILES_NO_SRCDIR
> > includes files that no longer exist: gdb_select.h and
> > tui/tui-windata.h.  Once these are removed from the list, TAGS is
> > built.
> 
> This also happens on Linux. I guess few people use "make TAGS"...

Any reason not to delete those 2 file names from the list?

> > 4. Running "maint selftests" produces several warnings and failures:
> >
> >   warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB.  Attempting to continue with the default i386:x86-64 settings.
> 
> Possibly related to
> https://sourceware.org/pipermail/gdb-patches/2020-March/166678.html ?

Simon, any chance you could look into this, or instruct me how to
investigate?


  reply	other threads:[~2020-06-30 14:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 18:27 Eli Zaretskii
2020-06-29 20:36 ` Christian Biesinger
2020-06-30 14:09   ` Eli Zaretskii [this message]
2020-06-30 22:24     ` Simon Marchi
2020-07-01 15:09       ` Eli Zaretskii
2020-07-02 13:50         ` Eli Zaretskii
2020-07-02 14:25           ` Simon Marchi
2020-07-02 14:30             ` Simon Marchi
2020-07-02 17:47               ` Eli Zaretskii
2020-07-02 14:40             ` Pedro Alves
2020-07-02 17:46               ` Eli Zaretskii
2020-07-02 18:21                 ` Pedro Alves
2020-07-02 18:33                   ` Eli Zaretskii
2020-07-02 18:34                     ` Pedro Alves
2020-07-01 15:20       ` Eli Zaretskii
2020-07-01 19:25         ` Christian Biesinger
2020-07-02  2:29           ` Eli Zaretskii
2020-07-02 10:18             ` Hannes Domani
2020-07-02 13:20               ` Eli Zaretskii
2020-07-06 10:39                 ` Hannes Domani
2020-07-06 16:35                   ` Eli Zaretskii
2020-07-01 19:25     ` Joel Brobecker
2020-07-02 13:46       ` Eli Zaretskii
2020-06-30 16:18 ` Eli Zaretskii
2020-06-30 18:21   ` Christian Biesinger
2020-06-30 18:28     ` Eli Zaretskii
2020-07-01 19:29   ` Joel Brobecker
2020-07-02  2:31     ` Eli Zaretskii
2020-07-01 19:30   ` Joel Brobecker
2020-07-02 13:39     ` Eli Zaretskii
2020-07-03 15:25       ` Joel Brobecker
2020-07-27  9:49         ` Tom de Vries
2020-07-27 10:05           ` Tom de Vries
2020-07-27 10:26             ` Tom de Vries
2020-07-27 11:48               ` [committed][gdb/build] Fix typo sys/sockets.h -> sys/socket.h Tom de Vries
2020-07-27 12:51                 ` Joel Brobecker
2020-07-27 14:18               ` Building today's snapshot of GDB with MinGW Eli Zaretskii
2020-07-02 14:12 ` Eli Zaretskii
2020-07-03 15:08   ` 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=83wo3ozlvn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tromey@adacore.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