From: Glenn Burkhardt <gbburkhardt@gmail.com>
To: gdb@sourceware.org
Subject: Re: MinGW build target
Date: Mon, 29 Aug 2016 10:48:00 -0000 [thread overview]
Message-ID: <0d2ab350-d00c-fc30-28ed-872f5f7ca223@gmail.com> (raw)
In-Reply-To: <83twe4buvf.fsf@gnu.org>
Thanks - that works better. I suppose that the '32' on 'mingw32' is an
artifact that predates the MinGW-w64 fork of the MinGW code base.
On 8/28/2016 2:39 PM, Eli Zaretskii wrote:
>> Date: Sun, 28 Aug 2016 21:26:56 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> CC: gdb@sourceware.org
>>
>>> What's the correct build target for MinGW-w64? I tried using
>>>
>>> --build=x86_64-w64-mingw64
>>>
>>> with gdb-7.11.1 and x86_64-6.1.0-release-posix-seh-rt_v5-rev0, and it's
>>> trying to compile ser-unix.c. That doesn't seem right, and, of course,
>>> MinGW doesn't include <sys/socket.h>.
>> Why do you need an explicit argument? Doesn't config.guess guess
>> correctly? If not, maybe your uname needs and update/upgrade?
> In any case, it sounds like x86_64-w64-mingw32 is what you want.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2016-08-29 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 17:54 Glenn Burkhardt
2016-08-28 18:27 ` Eli Zaretskii
2016-08-28 18:40 ` Eli Zaretskii
2016-08-29 10:48 ` Glenn Burkhardt [this message]
2016-08-29 7:47 ` Joel Brobecker
2016-08-29 10:51 ` Glenn Burkhardt
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=0d2ab350-d00c-fc30-28ed-872f5f7ca223@gmail.com \
--to=gbburkhardt@gmail.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