I opened an github issue on that topic:
https://github.com/matthew-brett/dll_investigation/issues/1
Carl
Am Sa., 22. Jan. 2022 um 15:56 Uhr schrieb Carl Kleffner <
cmkleff...@gmail.com>:
> Hi,
>
> bad.pyd has a strange section .voltbl at the beginning. good.pyd looks as
> expected.
> (pyd-files
Hi,
bad.pyd has a strange section .voltbl at the beginning. good.pyd looks as
expected.
(pyd-files are DLLs as used by CPython)
Carl
Am Sa., 22. Jan. 2022 um 15:11 Uhr schrieb Matthew Brett <
matthew.br...@gmail.com>:
> Hi,
>
> On Sat, Jan 22, 2022 at 12:40 PM Martin Storsjö wrote:
> >
> >
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 or object files between mingw and
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 or object files between mingw and msvc is not
supported, and not expected to work, in general. You might have
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