Re: [Mingw-w64-public] gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library

Hi, On Sun, Nov 20, 2022 at 3:59 PM Eli Zaretskii wrote: > > > Date: Sun, 20 Nov 2022 16:44:08 +0100 > > From: Pali Rohár > > Cc: g...@gcc.gnu.org, mingw-w64-public@lists.sourceforge.net > > > > > Installing a redistributable is a nuisance, and dependence on non-system > > > libraries might make

Re: [Mingw-w64-public] Invalid DLL when linking VS2019 (vc142) lib

Hi, On Sat, Jan 22, 2022 at 12:40 PM Martin Storsjö wrote: > > Hi, > > On Sat, 22 Jan 2022, Matthew Brett wrote: > > > The Scipy build links against a static library `npymath.lib`, until > > recently built with VS2017 v141 toolset. > > Mixing static libraries

[Mingw-w64-public] Invalid DLL when linking VS2019 (vc142) lib

Hi, We have run into a puzzling error when building the Scipy project with mingw-w64. The Scipy build links against a static library `npymath.lib`, until recently built with VS2017 v141 toolset. This build worked fine, until recently when the build for `npymath.lib` switched to using the VS2019

Re: [Mingw-w64-public] UCRT compiler does not recognize printf format flags it can parse at run-time

Hi, On Wed, Jan 19, 2022 at 7:41 PM Martin Storsjö wrote: > > Hi Matthew, > > On Wed, 19 Jan 2022, Matthew Brett wrote: > > > We've run into a problem over at > > https://github.com/rgommers/scipy/issues/118 > > > > The essence of the problem is t

[Mingw-w64-public] UCRT compiler does not recognize printf format flags it can parse at run-time

Hi, We are currently using the UCRT build of MinGW-w64 to build the Scipy library for Python - thanks for all your work that has made this possible. We've run into a problem over at https://github.com/rgommers/scipy/issues/118 The essence of the problem is that the *compiler* warns when we use t

Re: [Mingw-w64-public] [Poll] Move to git

> Am 09.05.2014 15:52, schrieb JonY: >> For mingw-w64 developers, state your SF ID; for the registered voters, >> simply reply with the same email address you registered with. [X] Yes, move to git [ ] No, continue with SVN --

Re: [Mingw-w64-public] Register your vote (was Re: mingw-w64 may move to git in the future)

against mingw for our distribution * I intend to submit patches for any problems I find while testing numerics on Windows I'm an experienced user of svn and git: http://sourceforge.net/u/matthewbrett/profile/ https://github.com/matthew-brett Best, Matthew

Re: [Mingw-w64-public] Advice on accuracy of exp function

Hi, On Tue, Apr 29, 2014 at 2:08 PM, Kai Tietz wrote: > 2014-04-29 21:16 GMT+02:00 Matthew Brett : >> Hi, >> >> I'm sorry to ask this question without more information, but I'm >> hoping you can give me an idea what more information I need. >> >>

[Mingw-w64-public] Advice on accuracy of exp function

Hi, I'm sorry to ask this question without more information, but I'm hoping you can give me an idea what more information I need. Some of us got very interested in using Mingw-w64 as the standard compiler for Python numerical tools such as numpy and scipy: https://github.com/numpy/numpy/wiki htt

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

Hi, On Mon, Apr 28, 2014 at 11:49 PM, Rodny wrote: > JonY writes: > >> >> Hi, >> >> mingw-w64 may migrate from svn to git in the future, seeing that sf can >> now do multiple repos per project. >> >> Structure wise, everything under trunk will still stay together in the >> new repo, but any exte

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

Hi, On Mon, Apr 28, 2014 at 1:05 PM, LRN wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 28.04.2014 23:29, Matthew Brett wrote: >> On Mon, Apr 28, 2014 at 12:10 PM, Adrien Nader wrote: >>> On Mon, Apr 28, 2014, LRN wrote: >>>> -B

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

Hi, On Mon, Apr 28, 2014 at 12:38 PM, Adrien Nader wrote: > On Mon, Apr 28, 2014, Matthew Brett wrote: >> Hi, >> >> On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader wrote: >> > On Mon, Apr 28, 2014, Matthew Brett wrote: >> >> Hi, >> >>

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

On Mon, Apr 28, 2014 at 12:10 PM, Adrien Nader wrote: > On Mon, Apr 28, 2014, LRN wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 28.04.2014 22:42, Adrien Nader wrote: >> > On Mon, Apr 28, 2014, Matthew Brett wrote: >> >> Hi, >

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

Hi, On Mon, Apr 28, 2014 at 11:42 AM, Adrien Nader wrote: > On Mon, Apr 28, 2014, Matthew Brett wrote: >> Hi, >> >> On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM wrote: >> > On 4/28/2014 5:17 AM, JonY wrote: >> >> mingw-w64 may migrate from sv

Re: [Mingw-w64-public] mingw-w64 may move to git in the future

Hi, On Mon, Apr 28, 2014 at 8:04 AM, John E. / TDM wrote: > On 4/28/2014 5:17 AM, JonY wrote: >> mingw-w64 may migrate from svn to git in the future, seeing that sf can >> now do multiple repos per project. > *snip* >> Discuss. > > I'm a bit surprised at the choice of Git -- in my experience, Win

Re: [Mingw-w64-public] [Project News | New Builds]

Hi, On Fri, Apr 25, 2014 at 7:17 PM, Dongsheng Song wrote: > On Sat, Apr 26, 2014 at 8:35 AM, JonY wrote: >> On 4/25/2014 23:37, Dongsheng Song wrote: You may need to use winpthread if you want to use --enable-libgomp. >>> >>> Yes. In my situation, we dont't need winpthread. Since we o

Re: [Mingw-w64-public] Bug fix for expm1 - how to proceed?

Hi, On Wed, Apr 16, 2014 at 10:47 PM, Matthew Brett wrote: > Hi, > > On Wed, Apr 16, 2014 at 11:50 AM, Kai Tietz wrote: >> Hello Matthew, >> >> 2014-04-16 20:36 GMT+02:00 Matthew Brett : >>> Hi, >>> >>> Sorry for my ignorance about mingw-

Re: [Mingw-w64-public] Bug fix for expm1 - how to proceed?

Hi, On Wed, Apr 16, 2014 at 11:50 AM, Kai Tietz wrote: > Hello Matthew, > > 2014-04-16 20:36 GMT+02:00 Matthew Brett : >> Hi, >> >> Sorry for my ignorance about mingw-w64 - I am hoping for advice on >> submitting a patch. >> >> When testing against

[Mingw-w64-public] Bug fix for expm1 - how to proceed?

Hi, Sorry for my ignorance about mingw-w64 - I am hoping for advice on submitting a patch. When testing against the Python numpy library, we found a failing test for the mingw-w64 expm1 routine. Specifically, we found that: double i = -0.0; return expm1(i); returns 0 instead of -0, as I believ