Re: [Mingw-w64-public] Fwd: Wine Gecko 2.40-beta1

[Erik van Pienbroek]

Jacek Caban schreef op ma 06-07-2015 om 17:24 [+0200]:
> Hi all,
> 
> I'm forwarding this announcement to mingw-w64 ML, because I know that 
> a few disto maintainers read it. The final release will be in about 5
> -6 weeks, so it's a good moment to ensure that it builds correctly. 
> All feedback is appreciated.
> 
> Thanks,
> Jacek

Hi Jacek,

For Fedora we just tried to get the latest wine-gecko built. In order
to get it built successfully against the recently released mingw-w64
v4.0.4 we had to manually backport the following commits:

7eee339 - msinkaut.idl: Added new file.
fc960d3 - msinkaut.h: Generated header file.
ef5e914 - msinkaut_i.c: Added new file.
4ce7a79 - Install *.c files as headers as well.
85b4034 - textstor.idl: Updated to current Wine version.
a883b47 - Added new versionhelpers.h header.
e4a8812 - d2d1_1helper.h: Added a few missing declarations.
e960f8f - winsdkver.h: Added *_WINBLUE defines.

c440466 - Added liblocationapi.a.

Could somebody please backport these commits to the v4.x branch?

A bit offtopic (not wine-gecko related) but could somebody also please
backport the following commit? It is needed by qt5-qtactiveqt 5.5.0

5f5e2c1 - activscp: Remove duplicate defines.

Regards,

Erik van Pienbroek



--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion

[Duane Ellis]

>> It's built from this project (and branch, be careful to not use
>> master!) on github:
>> https://github.com/Alexpux/mingw-builds/tree/develop but as I say, you
>> want canadian cross, and well, I'll not repeat what I wrote before,
>> I'd just encourage you to read it carefully.
> 
> Actually Python just needs to be cross compiled in this case. It might
> work from mingw-builds, but likely not.


That is _THE_ problem, python generally *blocks* all cross compilation the 
example is here:

https://github.com/python/cpython/blob/master/configure.ac#L377 


Where the “configure” script specifically blocks this.

yea, I could undo this - and let this pass - but they have or had a very 
specific reason to block this

I don’t know what that reason is, could it be

 “it will not work - thus we block it"

Or
“I don’t know if it will - so we block it”

There is no indication behind the reasoning.

-Duane.

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion

[Ray Donnelly]

On Sat, Aug 8, 2015 at 7:35 PM, Ray Donnelly  wrote:
> On Sat, Aug 8, 2015 at 7:18 PM, Duane Ellis  wrote:
>> Thanks for the quick reply.
>>
>> MinGW-w64 doesn't have an instance of Python or an instance of a
>> Python Enabled GDB since MinGW-w64 is a source-only project, more-or
>> less. I assume the builds you are talking about are the semi-official
>> mingw-builds ones, as they come with those things. That porting job
>> was something I initially did for the Google Android NDK (using
>> patches from Roumen Petrov as a base) and that Alexey Pavlov and I
>> worked on for mingw-builds. We continue to maintain the patches in the
>> MSYS2 project.
>>
>>
>> Hmm - the main MingW-64 page pointed me to:
>>
>> This:
>> http://www.mingw-w64.org/doku.php/download
>>
>> Picking the MingW-Builds:
>> http://www.mingw-w64.org/doku.php/download/mingw-builds
>>
>> Which points to:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/
>>
>>
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe/download
>>
>> That file was updated only a few days ago.
>>
>> This has Python, and a PY enabled version of GDB - what I am trying to do is
>> reproduce that …  But with a number of “cross compilation” tools for arm,
>> mips, aver, etc
>
> It's built from this project (and branch, be careful to not use
> master!) on github:
> https://github.com/Alexpux/mingw-builds/tree/develop but as I say, you
> want canadian cross, and well, I'll not repeat what I wrote before,
> I'd just encourage you to read it carefully.

Actually Python just needs to be cross compiled in this case. It might
work from mingw-builds, but likely not.

>
>>
>> How is that build created?
>>
>> -Duane.
>>
>>
>>
>>
>> --
>>
>> ___
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion

[Ray Donnelly]

On Sat, Aug 8, 2015 at 7:18 PM, Duane Ellis  wrote:
> Thanks for the quick reply.
>
> MinGW-w64 doesn't have an instance of Python or an instance of a
> Python Enabled GDB since MinGW-w64 is a source-only project, more-or
> less. I assume the builds you are talking about are the semi-official
> mingw-builds ones, as they come with those things. That porting job
> was something I initially did for the Google Android NDK (using
> patches from Roumen Petrov as a base) and that Alexey Pavlov and I
> worked on for mingw-builds. We continue to maintain the patches in the
> MSYS2 project.
>
>
> Hmm - the main MingW-64 page pointed me to:
>
> This:
> http://www.mingw-w64.org/doku.php/download
>
> Picking the MingW-Builds:
> http://www.mingw-w64.org/doku.php/download/mingw-builds
>
> Which points to:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/
>
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe/download
>
> That file was updated only a few days ago.
>
> This has Python, and a PY enabled version of GDB - what I am trying to do is
> reproduce that …  But with a number of “cross compilation” tools for arm,
> mips, aver, etc

It's built from this project (and branch, be careful to not use
master!) on github:
https://github.com/Alexpux/mingw-builds/tree/develop but as I say, you
want canadian cross, and well, I'll not repeat what I wrote before,
I'd just encourage you to read it carefully.

>
> How is that build created?
>
> -Duane.
>
>
>
>
> --
>
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion

[Qian Hong]

Hey Duane,

On Sun, Aug 9, 2015 at 1:52 AM, Ray Donnelly  wrote:
>>
>> My question is this:
>> Where is the BASH shell for MingW-W64?
>
> There isn't one. The closest you'll come is MSYS2, but that's for
> Windows, not GNU/Linux. Wine-staging can run and build a fair amount
> of MSYS2 now-a-days thanks to the dedicated efforts of Qian Hong and
> other wine-staging developers.

I'm monitoring the MinGW-w64 mailing list and happen to see this conversation.
Thanks Ray for introducing our work on supporting MSYS2 on wine-staging.
Currently it is far from perfect, a status overview could be found here:
https://github.com/fracting/wine-fracting/wiki/MSYS2-on-Wine#build-status

If anyone has any question about MSYS2 on Wine, feel free to find me
on #msys2 / #mingw-w64 / #wine-staging
Contributors are also great welcome :)

Have fun!


-- 
Regards,
Qian Hong

-
http://www.winehq.org

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion

[Duane Ellis]

Thanks for the quick reply.

> MinGW-w64 doesn't have an instance of Python or an instance of a
> Python Enabled GDB since MinGW-w64 is a source-only project, more-or
> less. I assume the builds you are talking about are the semi-official
> mingw-builds ones, as they come with those things. That porting job
> was something I initially did for the Google Android NDK (using
> patches from Roumen Petrov as a base) and that Alexey Pavlov and I
> worked on for mingw-builds. We continue to maintain the patches in the
> MSYS2 project.

Hmm - the main MingW-64 page pointed me to:

This:
http://www.mingw-w64.org/doku.php/download 


Picking the MingW-Builds:
http://www.mingw-w64.org/doku.php/download/mingw-builds 


Which points to:

http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/
 




http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe/download
 


That file was updated only a few days ago.

This has Python, and a PY enabled version of GDB - what I am trying to do is 
reproduce that …  But with a number of “cross compilation” tools for arm, mips, 
aver, etc

How is that build created?

-Duane.



--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] ./configure - and mingw-w64 confusion

[Ray Donnelly]

On Sat, Aug 8, 2015 at 6:22 PM, Duane Ellis  wrote:
> HI,
>
> My ultimate goal is to build a number of “python enabled” instances of GDB 
> that run on Windows.
> (ie: ARM, MIPS, and a few other core types)
>
> I have a candian-cross setup on my linux box, it works great for everything 
> but the “python enablement” step.
> Reason:  Python is specifically not supported in a candian cross, the *only* 
> configuration is Linux and Cygwin Canadian crosses

It's worse than that: CPython can't be built to run on Windows using
any compilers other than MSVC and CPython don't seem to be very
interested in changing that, or accepting patches from people who are.

>
> That blocks me :-( pretty hard
>
> From what I see, Mingw-w64 has an instance of Python *AND* a Python Enabled 
> GDB
>
> And I think I can build what I need - however - I’m confused about what 
> mingw-64 is.

MinGW-w64 doesn't have an instance of Python or an instance of a
Python Enabled GDB since MinGW-w64 is a source-only project, more-or
less. I assume the builds you are talking about are the semi-official
mingw-builds ones, as they come with those things. That porting job
was something I initially did for the Google Android NDK (using
patches from Roumen Petrov as a base) and that Alexey Pavlov and I
worked on for mingw-builds. We continue to maintain the patches in the
MSYS2 project.

>
> My question is this:
> Where is the BASH shell for MingW-W64?

There isn't one. The closest you'll come is MSYS2, but that's for
Windows, not GNU/Linux. Wine-staging can run and build a fair amount
of MSYS2 now-a-days thanks to the dedicated efforts of Qian Hong and
other wine-staging developers.

> How do I do a “./configure” to setup GDB?
>

The Windows Google Android NDK is built cross-canadian on GNU/Linux.
If you download the NDK and look at the build scripts you should be
able to get something going. The version of Python in the NDK is a lot
older than the ones in mingw-builds and in MSYS2 (2.7.5 I think, it's
been ages since I looked at the NDK). We don't build MSYS2's
mingw-w64-python* packages cross-canadian either, but the patches have
a heritage going back to the NDK so there shouldn't be too many
problems in using our latest Python patches in that scenario. The
latest patches can be found at:

https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-python2
https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-python3

> Where can I get a bit more detail about this?
>

You can find me on #msys2 if you need any help with this.

> Thanks.
>
>
>
>
> --
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

[Mingw-w64-public] ./configure - and mingw-w64 confusion

[Duane Ellis]

HI,

My ultimate goal is to build a number of “python enabled” instances of GDB that 
run on Windows.
(ie: ARM, MIPS, and a few other core types)

I have a candian-cross setup on my linux box, it works great for everything but 
the “python enablement” step.
Reason:  Python is specifically not supported in a candian cross, the *only* 
configuration is Linux and Cygwin Canadian crosses

That blocks me :-( pretty hard

From what I see, Mingw-w64 has an instance of Python *AND* a Python Enabled GDB 

And I think I can build what I need - however - I’m confused about what 
mingw-64 is.

My question is this:
Where is the BASH shell for MingW-W64?   
How do I do a “./configure” to setup GDB?

Where can I get a bit more detail about this?

Thanks.




--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc 5.2.1 libgomp testsuite failures with latest runtime and winpthread

[Rainer Emrich]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am 06.08.2015 um 23:27 schrieb Mattias Engdegård:
> 6 aug 2015 kl. 12.46 skrev Rainer Emrich :
>> I assume that's caused by the latest winpthread changes.
> 
> Sort of; it looks like a bug in libgomp that was tolerated by the old mutex
> implementation.
> 
> The acc_device_lock mutex is initialized in initialize_env and used in
> goacc_host_init, both which are declared __attribute__ ((constructor)).
> Such constructors are not called in a very predictable order, and
> apparently we weren't lucky this time.
> 
> The easy way is to make winpthread's mutex implementation more forgiving
> (treating 0-filled memory as if it were PTHREAD_MUTEX_INITIALIZER). Patch:
> 
> diff --git a/mingw-w64-libraries/winpthreads/src/mutex.c
> b/mingw-w64-libraries/wi index fec341a..6e1b392 100644 ---
> a/mingw-w64-libraries/winpthreads/src/mutex.c +++
> b/mingw-w64-libraries/winpthreads/src/mutex.c @@ -56,7 +56,10 @@ typedef
> struct { static bool is_static_initializer(pthread_mutex_t m) { -  return
> (uintptr_t)m >= (uintptr_t)-3; +  /* Treat 0 as a static initializer as
> well (for normal mutexes), + to tolerate sloppy code in libgomp. (We
> should rather fix that code!) */ +  intptr_t v = (intptr_t)m; +  return v
> >= -3 && v <= 0; }
> 
> /* Create and return the implementation part of a mutex from a static
> 
This fixes the issue, libgom.sum attached. Can we have this in head and in 4.x ?

> Fixing libgomp is probably cleaner: either make sure the constructors are
> run in the right order or initialize the acc_device_lock mutex statically.

Are you willing to work on this? I can't, I don't have the skills.

Thanks

Rainer

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVxKl4AAoJEB3HOsWs+KJbrBsIAKDsVw+xfMRanrCobwbdQMMx
GrTsrpuGbOTPBxhNsXI7YmnHS65rKJW9QCgfRBmY6udz2s8KUf2el/2yyADbjtT4
c+AdELVGnQypI2iaf70w2/WEXGQaR76AJ8gAyHp181UAJIIHwCZj4uI0M1gxe2Gy
/AsX84c2D7qduisc+SjGGkDgaK1+/zxopi7YWdU4Bp50/H+SK7HsgiJD84tKRQtV
9V96psZupm/R/m9UJS5AaRbObH8yHRxHF9/MVc0gMRjMaYiNSzTA3yujNWBTV2tP
iCKmTASe3Em6lfx6gFM7qVa0pLnEIr37AQjnBw1l2yKkHjYUEJOh6NwnG/XqOks=
=WYRN
-END PGP SIGNATURE-

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public