+1 Got lapack to compile, but no such luck with any "blas" package (like openblas). And that's a requirement for octave, which was what I was aiming at.
I'll share some recipes, tomorrow or so (today is stuffed with other work). On 23-01-19 22:39, Philip Balister wrote: > I care :) > > On 01/23/2019 04:28 PM, Randy MacLeod wrote: >> On 1/23/19 2:54 PM, Smith, Virgil (US) wrote: >>> Is there a current or relatively recent recipe for SciPy and related >>> libraries? >> >> People have worked on it at least once before but found some problems >> with blas and atlas: >> >> https://lists.yoctoproject.org/pipermail/yocto/2018-March/thread.html#40348 >> >> I'd say that there is interest. >> I CCed Peter who started one of the threads >> and BCCed 5 other people who seemed to be interested >> since I didn't want to drag them all into the thread. >> >> >>> >>> Further and more importantly, is having a maintainer for (recipes for) >>> those libraries a priority for the active members of the Project? >>> (i.e. does interest rise above the general welcoming of participants >>> to periodically asking “Hey has anyone put out a call to fill this >>> slot?” if/when the slot is vacant). >> >> It's always nice to have a maintainer but community members sometimes >> keep recipes up to date even if they aren't direct users. >> >>> >>> BTW: If this is the wrong list for this query, please let me know. >> >> It a reasonable list for general discussion. >> If you get to a point where patches are being submitted, >> it should probably go to another list such as: >> >>> >>> Why? We are trying to gauge community interest before making long >>> term plans. >>> >>> We would like to know if this horse is at all likely to have >>> healthcare before betting on it (without sacrificing other patients to >>> obtain the proper veterinary degree and keep up practice to treat it >>> ourselves). >> heh. >> >> Thanks! >> ../Randy >> >>> >>> NOTE: I see from the RRS emails that Derek Straka is currently >>> maintaining the python-numpy recipe. THANK YOU! >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Notice to recipient: This email is meant for only the intended >>> recipient of the transmission, and may be a communication privileged >>> by law, subject to export control restrictions or that otherwise >>> contains proprietary information. If you receive this email by >>> mistake, please notify us immediately by replying to this message and >>> then destroy it and do not review, disclose, copy or distribute it. >>> Thank you in advance for your cooperation. >>> >> >> -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto