On Tue, Jan 24, 2017 at 7:50 PM, Francois Bissey <francois.bis...@canterbury.ac.nz> wrote: > That was my suspicion. Now does sage-on-cygwin use openblas? > If not that means the corresponding `.pc` files have to be filled > with something appropriate before installing any blas/lapack dependencies. > > The present hack I introduced in gsl and causes this error is to force > the linking of libgsl to our selected cblas. By default upstream > leave it underlinked. The problem with underlinking is that you get > in corner cases when the sage library components using gsl are also > underlinked if you have “-Wl,—as-needed” in your LDFLAGS and you > use the gold linker. And sage won’t start up… > Generally speaking the underlinking is a bad idea in our context. > Adding a “LIBS” at configuration time was the easiest thing to do. > May be it needs to be avoided on cygwin.
I currently build Sage on Cygwin using the system-provided lapack package and ./configure --with-blas=atlas. I don't think I've explicitly gotten it working with a self-built openblas yet but it hasn't been a priority. >> On 25/01/2017, at 03:57, Dima Pasechnik <dimp...@gmail.com> wrote: >> >> >> >> On Tuesday, January 24, 2017 at 2:00:54 PM UTC, Frank Garvan wrote: >> >> Have attached config.log file >> >> Thanks. I think what really happens is that openblas did not install >> correctly, and gsl >> has a dependence on it. >> In more detail, your log says: >> >> configure:3502: gcc -g -O2 -L/home/Owner/sage/local/lib >> -Wl,-rpath,/home/Owner/sage/local/lib conftest.c -lopenblas -lm >&5 >> /usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: >> cannot find -lopenblas >> >> Could you post the corresponding log (SAGEROOT/logs/pkgs/openblas-*) ? >> >> >> >> >> On Tuesday, January 24, 2017 at 3:26:49 AM UTC-5, François wrote: >> Need to see >> /home/Owner/sage/local/var/tmp/sage/build/gsl-2.1.p1/src/config.log >> but I suspect I am responsible. >> >> François >> >> > On 24/01/2017, at 14:51, Frank Garvan <fga...@gmail.com> wrote: >> > >> > >> > Have attached log file. >> > >> > Can this be fixed? >> > >> > Thanks >> > >> > PS: Running cygwin64 on windows10 >> > processor: Intel Core i3-6100 CPU @ 3.70 Ghz >> > RAM: 8.00 GB >> > system type: 64-bit operating system, x64-based processor >> > >> > -- >> > 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+...@googlegroups.com. >> > To post to this group, send email to sage-...@googlegroups.com. >> > Visit this group at https://groups.google.com/group/sage-devel. >> > For more options, visit https://groups.google.com/d/optout. >> > <gsl-2.1.p1.log> >> >> >> -- >> 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 https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. > > -- > 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 https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
