https://bugzilla.redhat.com/show_bug.cgi?id=1040517 --- Comment #19 from baurthefirst@xxxxxxxxx --- (In reply to Milan Bouchet-Valat from comment #18) > Orion: Yes, LLVM is going to be a problem. I've updated it manually to 3.4, > but I don't know how to make it automatic, and more profoundly there's no > guarantee that Julia will work with any newer versions without changes. So > it may be better to retain the manual update solution. > > I'll also have a look at the network access issue. > > baurthefirst: Thanks, I didn't know about copr, and I wasn't able to use > Koji since utf8proc and openlibm are not present there. I'll have a look. > Since Julia opens libraries at run time, it may indeed try to acces > libopenblas.so rather than libopenblas-r0.2.8.so or the equivalent, and > therefore require opneblas-devel. This should probably be fixed uptsream. > > > Meanwhile, I've filed a bundling exception request at > https://fedorahosted.org/fpc/ticket/427 Have you considered setting JULIA_CPU_TARGET to core2? By default it is set to native, thus causing the issue as I wrote earlier: Target architecture mismatch. Please delete or regenerate sys.{so,dll,dylib} -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review