On Thu, Jan 26, 2017 at 5:04 AM, Frank Garvan 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 necessar
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
On
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 fi
On Tue, Jan 24, 2017 at 7:50 PM, Francois Bissey
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
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
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/sa
Have attached config.log file
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 >
> 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 wrote:
>
>
> Have attached log file.
>
> Can this be fixed?
>
> Thanks
>
> PS: Running cygwin64 on windows10
> processor: Intel Co
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" gr
