> On Nov 2, 2019, at 10:33 AM, Kurt Mosiejczuk <k...@cranky.work> wrote: > > On Sat, Nov 02, 2019 at 07:03:57AM -0400, Daniel Dickman wrote: > >>>> On Nov 2, 2019, at 2:56 AM, Kurt Mosiejczuk <k...@cranky.work> wrote: >> >>>> 'So the existing py-numpy is unhappy with the 2.7 update and it >>> seems to be clashes between clang and gcc. > >> Should the 2.7 python update be backed out? Or is there some smaller >> fix for the existing numpy version? > > Perhaps it should be backed out. That will also be rather complicated > though. Rolling back to previous and cranking EPOCH doesn’t do the trick?
- Re: WIP: Update of math/py-numpy to 1.16.5 Daniel Dickman
- Re: WIP: Update of math/py-numpy to 1.16.5 Daniel Dickman
- Re: WIP: Update of math/py-numpy to 1.16... Stuart Henderson
- Re: WIP: Update of math/py-numpy to 1.16.5 Jeremie Courreges-Anglas
- Re: WIP: Update of math/py-numpy to 1.16... Stuart Henderson
- Re: WIP: Update of math/py-numpy to 1.16... Daniel Dickman
- Re: WIP: Update of math/py-numpy to ... Marc Espie
- Re: WIP: Update of math/py-numpy... Jeremie Courreges-Anglas
- Re: WIP: Update of math/py-numpy... Daniel Dickman
- Re: WIP: Update of math/py-numpy to 1.16.5 Daniel Dickman
- Re: WIP: Update of math/py-numpy to 1.16.5 Daniel Dickman
- Re: WIP: Update of math/py-numpy to 1.16.5 Stuart Henderson