From: Christian Biesinger <cbiesinger@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Building today's snapshot of GDB with MinGW
Date: Mon, 29 Jun 2020 15:36:50 -0500 [thread overview]
Message-ID: <CAPTJ0XEokO0Ht787+19d2yWF3cxqtzv+q0RqKo+JoENuhxaMGg@mail.gmail.com> (raw)
In-Reply-To: <83a70l20dn.fsf@gnu.org>
On Mon, Jun 29, 2020 at 1:27 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> At Joel's request I've built today's (29 June) snapshot of GDB using
> mingw.org's MinGW and GCC 9.2.0. There are a few issues I bumped into
> related to Gnulib and MinGW runtime (which I recently upgraded to a
> newer version), and I'm still working on those. So what's below is an
> interim report of issues related to GDB itself:
>
> 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
> 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.
> 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"...
> 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 ?
Christian
next prev parent reply other threads:[~2020-06-29 20:37 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 [this message]
2020-06-30 14:09 ` Eli Zaretskii
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=CAPTJ0XEokO0Ht787+19d2yWF3cxqtzv+q0RqKo+JoENuhxaMGg@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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