Commit Graph

37 Commits

Author SHA1 Message Date
Hood Chatham b485100b42
Update numpy to v1.23.0 (#2819) 2022-07-01 07:13:36 -07:00
Hood Chatham 8c8109f1df
Remove make-int-return-values patch (#2770) 2022-06-22 20:35:10 -07:00
Hood Chatham f4f179fee8
Update packages (#2758)
Everything is up to date except:
* yt
* opencv-python
2022-06-22 11:12:05 -07:00
Hood Chatham a7f099e5d6
MAINT Finish tidying up numpy patches (#2717) 2022-06-15 13:11:36 -07:00
Hood Chatham c1c0cd34fa
Update fenv patch to match upstreamed patch (#2692)
This new patch has the benefit that if wasm/emscripten ever does
gain fenv support we will switch to using it automatically.
2022-06-15 07:45:13 -07:00
Hood Chatham a83055b003
Update patch for numpy to determine pointer sizes correctly for cross build (#2695)
Upstream PR: numpy/numpy#21733 (files)

Upstream patch was accepted. Final upstream version is slightly different to support windows,
but the difference doesn't matter for us.
2022-06-13 20:05:49 -07:00
Hood Chatham 2d056ed253
Add support for backend flags to buildpkg (#2690)
And use it to disable numpy optimization by passing the `--disable-optimization` 
flag instead of patching numpy.
2022-06-13 16:40:48 -07:00
Hood Chatham 07322414e8
Replace numpy disable-svml patch with upstreamed version (#2702) 2022-06-13 16:35:05 -07:00
Hood Chatham dc33b25a6f
MAINT Tidy up numpy patches (#2701) 2022-06-12 15:19:09 -07:00
Hood Chatham b9c90fe813
Remove another numpy patch (#2699) 2022-06-12 12:18:45 -07:00
Hood Chatham a47e9085b8
Drop Numpy use local blas lapack patch (#2696) 2022-06-12 13:07:00 +02:00
Hood Chatham d3544a06a8
Drop numpy init alloc cache patch (#2698) 2022-06-12 11:44:34 +09:00
Hood Chatham 105e1bffa3
Drop numpy execinfo patch (#2691) 2022-06-12 11:43:55 +09:00
Hood Chatham 1fc1d6ce8a
Remove numpy disable maybe uninitialized patch (#2694) 2022-06-12 00:32:11 +02:00
Hood Chatham 91c56911f6
Drop numpy fix-longdouble patch (#2693) 2022-06-12 00:31:34 +02:00
Hood Chatham ed5953ceaf
Remove fix-invalid-asm-instruction patch (#2697) 2022-06-12 00:29:36 +02:00
Hood Chatham a54b1b4bd8
Update numpy to v1.22.3 (#2337) 2022-04-01 22:00:47 +02:00
Hood Chatham f7b0f8c5cb
No replay (#2256)
Our package build process currently has a significant flaw: we first run setup.py, recording all compilation commands, then we rewrite these compilation commands to invoke emcc and replay them, and then we pray that the cross compiled executables ended up in the right place to go into the wheel. This is not a good strategy because the build script is allowed to implement arbitrary logic, and if it moves, renames, etc any of the output files then we lose track of them. This has repeatedly caused difficulty for us.

However, we also make no particularly significant use of the two pass approach. We can just do the simpler thing: capture the compiler commands as they occur, modify them as needed, and then run the fixed command.

I also added a patch to fix the numpy feature detection for wasm so that we don't have to include _npyconfig.h and config.h, numpy can generate them in the way it would for a native build. I opened a numpy PR that would fix the detection for us upstream:
numpy/numpy#21154

This clears the way for us to switch to using pypa/build (as @henryiii has suggested) by removing our dependence on specific setuptools behavior.

This is on top of #2238.
2022-03-13 11:39:06 -07:00
Hood Chatham c01ab547f0
Better package cross compilation (#2238)
Co-authored-by: Gyeongjae Choi <def6488@gmail.com>
2022-03-09 20:34:25 -08:00
Hood Chatham dd70b565f5
Remove numpy decorators patch (#2259) 2022-03-07 21:44:35 -08:00
Hood Chatham 9feb50bb48
Remove numpy patches work around for chrome 89 bug (#2171) 2022-03-04 16:09:51 -08:00
Hood Chatham 6bdd96c964
Fix numpy fatal error: incorrect random_float_fill return type (#2137)
Upstream PR numpy/numpy#20911
2022-01-27 00:13:32 -08:00
Hood Chatham a206386564
Fix numpy comparator functions (#2110) 2022-01-16 15:52:34 -08:00
Hood Chatham 19261f394c
Remove function pointer cast emulation (#2019) 2021-12-09 10:31:21 -08:00
LeoPsidom 4662024b56
Upgrade numpy to 1.21.4 (#1934) 2021-11-14 15:03:56 +01:00
Hood Chatham 70e9e19dde
Patches from joemarshall/fpcast (#1708)
Co-authored-by: joemarshall <joe.marshall@nottingham.ac.uk>
Co-authored-by: Roman Yurchak <rth.yurchak@gmail.com>
2021-11-13 12:31:11 +01:00
Hood Chatham 653891b045
ENH Add Ctypes support (#1656) 2021-06-26 10:34:31 +02:00
Hood Chatham 1485732211
Fix memory access out of bounds in numpy + chrome 89 (#1474) 2021-04-17 23:17:19 +02:00
Hood Chatham 8f3f6bda20
Fix numpy in chromium v89 (#1449) 2021-04-12 09:10:27 +02:00
Roman Yurchak d175636851
Update to numpy 1.17.5 (#887) 2021-03-23 22:49:38 +01:00
Roman Yurchak e5672449f9
F2C, CLAPACK, scipy and numpy fixes for the upstream backend (#1193)
Co-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk>
2021-02-05 10:54:12 +01:00
Dexter Chua e706dd4223
Document f2c patches (#1087) 2021-01-10 17:12:48 +08:00
joemarshall 6cc7f9c46d
Make f2c functions return int
This patch makes everything in numpy, scipy and CLAPACK that began life as a fortran subroutine return int, whereas before they were a smattering of void plus lots of int, with a bunch of conflicts where the same function was defined as int in some and void in others. This matters because on upstream emscripten, these packages will not build due to linker conflicts, as the wasm linker can't link a function returning int to a function returning void.

Annoyingly, this has to be int return not void, because whereas a normal fortran subroutine doesn't return anything, there's an obscure feature of fortran 77 called alternative returns which allows subroutines to say they want to return by jumping to some other place in the code. f2c handles this with integer return values.
2021-01-09 17:44:41 +08:00
Michael Droettboom 01b27b37b9 Update to Numpy 1.15.1 2018-09-10 12:55:37 -04:00
Michael Droettboom 30e82a2d86 Add patch 2018-08-23 12:06:14 -04:00
Michael Droettboom 14f5e9b39d Fix #115: Forcibly use the local copy of blas and lapack 2018-08-20 22:44:26 -04:00
Michael Droettboom 17e1562ded MVP of a proper packaging system 2018-06-20 14:54:47 -04:00