On Friday, February 7, 2014 7:31:59 PM UTC+1, François wrote: > > While gold is part of the problem it is not completely its fault in my > opinion. > gold I think default to "as-needed" sage/rings/model. complex_double.pyx > doesn't directly > call cblas so gold doesn't see it as needed and drop it. The problem here > is that libgsl > itself is not linked properly for it to work - regardless of gold. > If you check the readelf -d output for libgsl there is no mention of > libcblas/libgslcblas > in the nedded section. So the libgsl doesn't even know where to find its > undefined symbols. > I guess gold may be made to work here if we can convince it to include > libcblas in the > needed section of complex_double.so. But I think we should fix the > somewhat fishy > stuff in libgsl, sure it is legal and all in that you can link with the > libclas of your choice > and gold may even do the right thing for an executable where all symbols > have to be > resolved but a .so? Well undefined symbols is legal for a library..... > > So I would like to know what libgsl looks like before Jean-Pierre's fix > for cygwin. >
Hum, what did I do? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
