MinGW build target

MinGW build target

[Glenn Burkhardt]

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>.



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: MinGW build target

[Eli Zaretskii]

> From: Glenn Burkhardt <gbburkhardt@gmail.com>
> Date: Sun, 28 Aug 2016 13:54:32 -0400
> 
> 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?

Re: MinGW build target

[Eli Zaretskii]

> 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.

Re: MinGW build target

[Glenn Burkhardt]

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

Re: MinGW build target

[Joel Brobecker]

> > 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?

To answer the question of "why" - on Windows, the config.guess output is
not always what you want, as it depends on how you execute that script.
In our case, we build using a cygwin environment, so config.guess
returns a cygwin triplet. So, when you actually want to build a MinGW
debugger, you have to pass the MinGW triplet explicitly.

-- 
Joel

Re: MinGW build target

[Glenn Burkhardt]

On 8/29/2016 3:47 AM, Joel Brobecker wrote:

>>> 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?
> To answer the question of "why" - on Windows, the config.guess output is
> not always what you want, as it depends on how you execute that script.
> In our case, we build using a cygwin environment, so config.guess
> returns a cygwin triplet. So, when you actually want to build a MinGW
> debugger, you have to pass the MinGW triplet explicitly.
>
Correct.  The MinGW-w64 code doesn't include 'uname'.  I'm using Msys2 
as a shell, along with its support programs, which include 'uname'.  On 
Msys2,

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus