Problem building GSL in cygwin64

[Frank Garvan]

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

[Francois Bissey]

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

> --
> 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>

[Dima Pasechnik]

I tried to post a message, it got lost during the process (and a message by Samuel).

I wonder whether the people who get sage-develop by email

can repost copies...

[Samuel Lelievre]

Apparently there are two posts with the same subject,

one on sage-support and one on sage-devel. The two

messages you mention are on sage-support at

https://groups.google.com/d/topic/sage-support/m6tGTnuirqY/discussion

[Frank Garvan]

Have attached config.log file

[Dima Pasechnik]

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-*) ?

[Francois Bissey]

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.

François

[Frank Garvan]

Have attached openblas log as requested

FG

[Erik Bray]

On Tue, Jan 24, 2017 at 7:50 PM, Francois Bissey
<francoi...@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.

[Frank Garvan]

As suggested I did the following:

  cd sage
  export SAGE_ATLAS_ARCH=base
  ./configure --with-blas=atlas
  make

Go the following error:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):

* package: libfplll-5.0.3rc0
  log file: /home/Owner/sage/logs/pkgs/libfplll-5.0.3rc0.log
  build directory: /home/Owner/sage/local/var/tmp/sage/build/libfplll-5.0.3rc0


Have attached log file libfplll-5.0.3rc0.log

Thanks
FG

[Jean-Pierre Flori]

The LDConvert error must be some LongDouble stuff not guarded correctly with #if HAS_LONG_DOUBLE (or a variation thereof).
Cygwin does not provide these.
It should be reported upstream.

Actually we have a trac ticket and that has been reported upstream:
https://trac.sagemath.org/ticket/21690

[Erik Bray]

On Thu, Jan 26, 2017 at 5:04 AM, Frank Garvan <fga...@gmail.com> wrote:
> As suggested I did the following:
>
> cd sage
> export SAGE_ATLAS_ARCH=base
> ./configure --with-blas=atlas
> make
>
> Go the following error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
>
> * package: libfplll-5.0.3rc0
> log file: /home/Owner/sage/logs/pkgs/libfplll-5.0.3rc0.log
> build directory:
> /home/Owner/sage/local/var/tmp/sage/build/libfplll-5.0.3rc0

Hi Frank,

There are many known issues currently preventing the main branch of
Sage from building on Cygwin. As Jean-Pierre pointed out this one is
already known and has a ticket for it. But if you got past this issue
there would be several more problems, some of which I've resolved and
some of which still need work (for example, I haven't finished the
fixes for Singular yet; see
https://github.com/Singular/Sources/pull/808

I have been working on Cygwin support for Sage, and the only version
of Sage currently working on Cygwin that I know of is my personal
branch based on Sage 7.4 (before the Singular upgrade) along with a
number of other fixes I've merged in that aren't in the main branch
yet:

https://git.sagemath.org/sage.git/?h=u%2Fembray%2Fcygwin%2Fsagemath-7.4

I also have some build tools I've bee working on that make it easier
to build Sage in Cygwin, but they aren't posted yet. I'm of course
happy to have help with this work, and if you said something about why
you're trying to run Sage in Cygwin I might be able to help more
directly. For now though I'm just trying to save you and others time
by pointing out that what you're trying to do won't work *right now*.

Best,
Erik