From: Alexander Fedotov <alfedotov@gmail.com>
To: felix.willgerodt@intel.com, gdb@sourceware.org
Subject: Re: Mingw64 build failure
Date: Fri, 12 Aug 2022 13:08:11 +0300 [thread overview]
Message-ID: <CAN8C2CrFwzg=mwss22vvcLb0S-jJsG9uKJVqYJcMyFema2eq1A@mail.gmail.com> (raw)
I had the same issue with GDB12 build using mingw32 on f32 and f35.
But after some trials this configuration works for me:
"'--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'"
Alex
next reply other threads:[~2022-08-12 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 10:08 Alexander Fedotov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-07 10:01 Willgerodt, Felix
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='CAN8C2CrFwzg=mwss22vvcLb0S-jJsG9uKJVqYJcMyFema2eq1A@mail.gmail.com' \
--to=alfedotov@gmail.com \
--cc=felix.willgerodt@intel.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).