Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: Alexander Fedotov <alfedotov@gmail.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Re: GDB 12.1 mingw build fails on Fedora 35
Date: Thu, 28 Jul 2022 12:43:57 -0600	[thread overview]
Message-ID: <87r125hyc2.fsf@tromey.com> (raw)
In-Reply-To: <CAN8C2CrvaLgAtMe5Fu16oEfzK88W3jKQF47xxE25wq8dSfvWRw@mail.gmail.com> (Alexander Fedotov's message of "Wed, 27 Jul 2022 14:17:19 +0300")

Alex> I'm trying to build GDB 12.1 from the release tarball on Fedora 35
Alex> using MinGW i686-w64-mingw32 compiler. And getting following
Alex> gnulib error:

I have definitely seen this error before, but I don't remember what I
did to fix it.

I have the gdb 12 branch checked out and I was able to this build on
Fedora 34:

murgatroyd. ./config.status --version
config.status
configured by ../binutils-gdb/configure, generated by GNU Autoconf 2.69,
  with options "'--host=i686-w64-mingw32' '--target=i686-w64-mingw32' '--disable-binutils' '--disable-gas' '--disable-gold' '--disable-gprof' '--disable-ld' '--disable-guile' '--disable-source-highlight' '--without-debuginfod' 'LDFLAGS=-lssp' '--disable-sim' '--disable-gprofng' 'host_alias=i686-w64-mingw32' 'target_alias=i686-w64-mingw32'"


I haven't upgraded to Fedora 35 yet.

FWIW git master doesn't build in this configuration for me due to some
BFD changes.

Tom

      reply	other threads:[~2022-07-28 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 11:17 Alexander Fedotov via Gdb-patches
2022-07-28 18:43 ` Tom Tromey via Gdb-patches [this message]

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=87r125hyc2.fsf@tromey.com \
    --to=gdb-patches@sourceware.org \
    --cc=alfedotov@gmail.com \
    --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