Does that mean that numpy is a completely broken package, or is that a way to hack it to make it work? If it is broken and will stay that way, why don't we remove it from the recipe list? If that is the case then it's just misleading.
Thanks, Bob On Tue, Jun 28, 2011 at 1:52 AM, Koen Kooi <[email protected]>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 27-06-11 22:42, Paul Menzel wrote: > > Dear Patrik, > > > > > > Am Sonntag, den 10.04.2011, 21:45 +0200 schrieb Patrik Dahlström > (student): > > > > […] > > > >> I am however uncertain on how to proceed with this and could use some > >> assistance. > > > > did you find a “generic” solution for this problem? > > It requires redoing the numpy buildsystem, it is broken by design. I > tried to teach it about crosscompiling and sysroots last year, but gave > up after a few days :( > > regards, > > Koen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFOCXo2MkyGM64RGpERAggYAJ0VMl1Ttg0QGqNCrmBhdlhnp9yPzgCgldQf > d5EbEv+2sn1ssE10DGkigsM= > =Sx4L > -----END PGP SIGNATURE----- > > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > -- University of Illinois at Urbana-Champaign Electrical Engineering [email protected] (630) 306-4018 _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
