Opened 17 months ago
Closed 17 months ago
#31521 closed defect (fixed)
numpy build broken with SAGE_FAT_BINARY=yes
Reported by:  mkoeppe  Owned by:  

Priority:  blocker  Milestone:  sage9.3 
Component:  packages: standard  Keywords:  
Cc:  embray, ghkliem, dimpase, vbraun  Merged in:  
Authors:  Jonathan Kliem  Reviewers:  Matthias Koeppe 
Report Upstream:  N/A  Work issues:  
Branch:  128e8ef (Commits, GitHub, GitLab)  Commit:  128e8ef688fe3cba05b19f39e469cf3832be1e4a 
Dependencies:  #29537  Stopgaps: 
Description
Follow up from #29537.
Change History (8)
comment:1 Changed 17 months ago by
comment:2 Changed 17 months ago by
 Cc dimpase added
comment:3 Changed 17 months ago by
 Cc vbraun added
 Summary changed from cygwin: numpy not portable despite using SAGE_FAT_BINARY=yes to numpy build broken with SAGE_FAT_BINARY=yes
Indeed, cpudispatch
has only been introduced in the 1.20.x series. We are still at 1.19.5.
Wondering how this has possibly passed in previous tests?!
comment:4 Changed 17 months ago by
And I guess the prefix SAGE_
can be removed in the variable names in sage_conf...
comment:5 Changed 17 months ago by
 Branch set to public/31521
 Commit set to 128e8ef688fe3cba05b19f39e469cf3832be1e4a
 Status changed from new to needs_review
Reverting for now until numpy is updated.
New commits:
128e8ef  Revert "do not allow numpy intrinsics when building fat binary"

comment:6 followup: ↓ 7 Changed 17 months ago by
 Component changed from porting: Cygwin to packages: standard
 Reviewers set to Matthias Koeppe
 Status changed from needs_review to positive_review
Thanks!
But we'll need another ticket then to actually fix the nonportability of the build...
comment:7 in reply to: ↑ 6 Changed 17 months ago by
comment:8 Changed 17 months ago by
 Branch changed from public/31521 to 128e8ef688fe3cba05b19f39e469cf3832be1e4a
 Resolution set to fixed
 Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
On macOS, with
SAGE_FAT_BINARY=yes
, I just got: