[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[John H Palmieri]

Sorry, that's wrong. Try:

./sage -f zlip  <-- This is the correction
./sage -f python2
./sage -f python3
make

See also https://trac.sagemath.org/ticket/26899.

  John


On Sunday, February 17, 2019 at 10:40:59 PM UTC-8, John H Palmieri wrote:
>
> Please try:
>
> ./sage -f zip
> ./sage -f python2
> ./sage -f python3
>
> and if those work, try 'make' again.
>
>   John
>
>
> On Sunday, February 17, 2019 at 6:11:51 PM UTC-8, Andrew wrote:
>>
>> I have been unable to compile sage for a while on both an imac and a 
>> macbook pro that are running mojave (clearly my mistake for installing 
>> it...). I have installed the system headers, so that's unlikely to be the 
>> problem. 
>>
>> Everytime that I try to compile I get stuck on:
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: pip-18.1
>>   log file: /usr/local/src/sage/logs/pkgs/pip-18.1.log
>>   build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
>>
>> The build directory may contain configuration files and other potentially
>> helpful information. WARNING: if you now run 'make' again, the build
>> directory will, by default, be deleted. Set the environment variable
>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>
>> I am running: 
>>
>> ProductName:Mac OS X
>> ProductVersion:10.14.3
>> BuildVersion:18D109
>> Xcode 10.1
>> Build version 10B61
>>
>> The logs after: makedistcean && make are too big to attach but if 
>> interested you can find them at 
>> http://www.maths.usyd.edu.au/u/mathas/install.log.
>>
>> Any hints would be greatly appreciated.
>>
>> Andrew
>>
>

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

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[John H Palmieri]

Please try:

./sage -f zlib
./sage -f python2
./sage -f python3

and if those work, try 'make' again.

  John



On Sunday, February 17, 2019 at 6:11:51 PM UTC-8, Andrew wrote:
>
> I have been unable to compile sage for a while on both an imac and a 
> macbook pro that are running mojave (clearly my mistake for installing 
> it...). I have installed the system headers, so that's unlikely to be the 
> problem. 
>
> Everytime that I try to compile I get stuck on:
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: pip-18.1
>   log file: /usr/local/src/sage/logs/pkgs/pip-18.1.log
>   build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> I am running: 
>
> ProductName:Mac OS X
> ProductVersion:10.14.3
> BuildVersion:18D109
> Xcode 10.1
> Build version 10B61
>
> The logs after: makedistcean && make are too big to attach but if 
> interested you can find them at 
> http://www.maths.usyd.edu.au/u/mathas/install.log.
>
> Any hints would be greatly appreciated.
>
> Andrew
>

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

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[John H Palmieri]

Please try:

./sage -f zip
./sage -f python2
./sage -f python3

and if those work, try 'make' again.

  John


On Sunday, February 17, 2019 at 6:11:51 PM UTC-8, Andrew wrote:
>
> I have been unable to compile sage for a while on both an imac and a 
> macbook pro that are running mojave (clearly my mistake for installing 
> it...). I have installed the system headers, so that's unlikely to be the 
> problem. 
>
> Everytime that I try to compile I get stuck on:
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: pip-18.1
>   log file: /usr/local/src/sage/logs/pkgs/pip-18.1.log
>   build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> I am running: 
>
> ProductName:Mac OS X
> ProductVersion:10.14.3
> BuildVersion:18D109
> Xcode 10.1
> Build version 10B61
>
> The logs after: makedistcean && make are too big to attach but if 
> interested you can find them at 
> http://www.maths.usyd.edu.au/u/mathas/install.log.
>
> Any hints would be greatly appreciated.
>
> Andrew
>

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

[sage-devel] Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

I have been unable to compile sage for a while on both an imac and a 
macbook pro that are running mojave (clearly my mistake for installing 
it...). I have installed the system headers, so that's unlikely to be the 
problem. 

Everytime that I try to compile I get stuck on:

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

* package: pip-18.1
  log file: /usr/local/src/sage/logs/pkgs/pip-18.1.log
  build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

I am running: 

ProductName:Mac OS X
ProductVersion:10.14.3
BuildVersion:18D109
Xcode 10.1
Build version 10B61

The logs after: makedistcean && make are too big to attach but if 
interested you can find them at 
http://www.maths.usyd.edu.au/u/mathas/install.log.

Any hints would be greatly appreciated.

Andrew

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

Re: [sage-devel] Error copying files for gfortan-7.2.0

[Dima Pasechnik]

This is very strange - it looks as if ./configure does set the build
to use gcc and gfortran (both versions 7.3.1)
from the system, and yet a (failed) attempt to build gfortran is made.

Perhaps some stale files? Did you run
make distclean
before doing ./configure+make ?


On Sun, Feb 17, 2019 at 5:47 PM Andreas Hermann  wrote:
>
> In the meantime I have upgraded my operating system to the more recent 
> OpenSuse Leap 15.0.
> I am having again the same problem as I have described above.
> With "./configure FC=gfortran-7" and then "make" I get the same error as 
> above.
> I have attached config.log and I would still appreciate your help.
>
> --
> 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.

Re: [sage-devel] Error copying files for gfortan-7.2.0

[Andreas Hermann]

In the meantime I have upgraded my operating system to the more recent 
OpenSuse Leap 15.0.
I am having again the same problem as I have described above.
With "./configure FC=gfortran-7" and then "make" I get the same error as 
above.
I have attached config.log and I would still appreciate your help.

-- 
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.
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by Sage configure 8.6, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure FC=gfortran-7

## - ##
## Platform. ##
## - ##

hostname = linux-xhno
uname -m = x86_64
uname -r = 4.12.14-lp150.12.45-default
uname -s = Linux
uname -v = #1 SMP Mon Jan 14 20:29:59 UTC 2019 (7a62739)

/usr/bin/uname -p = x86_64
/bin/uname -X = unknown

/bin/arch  = x86_64
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /home/andreas/bin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/lib/mit/sbin


## --- ##
## Core tests. ##
## --- ##

configure:2424: loading site script /usr/share/site/x86_64-unknown-linux-gnu
| #!/bin/sh
| # Site script for configure. It is resourced via $CONFIG_SITE environment 
varaible.
| 
| # If user did not specify libdir, guess the correct target:
| # Use lib64 for 64 bit bi-arch targets, keep the default for the rest.
| if test "$libdir" = '${exec_prefix}/lib' ; then
| 
|   ac_config_site_64bit_host=NONE
| 
|   case "$host" in
|   "" )
|   # User did not specify host target.
|   # The native platform x86_64 is a bi-arch platform.
|   # Try to detect cross-compilation to inferior architecture.
| 
|   # We are trying to guess 32-bit target compilation. It's not as 
easy as
|   # it sounds, as there is possible several intermediate 
combinations.
|   ac_config_site_cross_to_32bit_host=NONE
| 
|   # User defined -m32 in CFLAGS or CXXFLAGS or CC or CXX:
|   # (It's sufficient for 32-bit, but alone may cause mis-behavior 
of some checks.)
|   case "$CFLAGS $CXXFLAGS $CC $CXX" in
|   *-m32*)
|   ac_config_site_cross_to_32bit_host=YES
|   ;;
|   esac
| 
|   # Running with linux32:
|   # (Changes detected platform, but not the toolchain target.)
|   case "`/bin/uname -i`" in
|   x86_64 | ppc64 | s390x | aarch64 )
|   ;;
|   * )
|   ac_config_site_cross_to_32bit_host=YES
|   ;;
|   esac
| 
|   if test "x$ac_config_site_cross_to_32bit_host" = xNONE; then
|   ac_config_site_64bit_host=YES
|   fi
| 
|   ;;
|   *x86_64* | *ppc64* | *s390x* | *aarch64* )
|   ac_config_site_64bit_host=YES
|   ;;
|   esac
| 
|   if test "x$ac_config_site_64bit_host" = xYES; then
|   libdir='${exec_prefix}/lib64'
|   fi
| fi
| 
| # If user did not specify libexecdir, set the correct target:
| # Nor FHS nor openSUSE allow prefix/libexec. Let's default to prefix/lib.
| 
| if test "$libexecdir" = '${exec_prefix}/libexec' ; then
|   libexecdir='${exec_prefix}/lib'
| fi
| 
| # Continue with the standard behavior of configure defined in AC_SITE_LOAD:
| if test "x$prefix" != xNONE; then
|   ac_site_file1=$prefix/share/config.site
|   ac_site_file2=$prefix/etc/config.site
| else
|   ac_site_file1=$ac_default_prefix/share/config.site
|   ac_site_file2=$ac_default_prefix/etc/config.site
| fi
| for ac_site_file in "$ac_site_file1" "$ac_site_file2"
| do
|   test "x$ac_site_file" = xNONE && continue
|   if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then
|   { $as_echo 
"/usr/share/site/x86_64-unknown-linux-gnu:${as_lineno-$LINENO}: loading site 
script $ac_site_file" >&5
| $as_echo "/usr/share/site/x86_64-unknown-linux-gnu: loading site script 
$ac_site_file" >&6;}
|   sed 's/^/| /' "$ac_site_file" >&5
|   . "$ac_site_file" \
|   || { { $as_echo 
"/usr/share/site/x86_64-unknown-linux-gnu:${as_lineno-$LINENO}: error: in 
\`$ac_pwd':" >&5
| $as_echo "/usr/share/site/x86_64-unknown-linux-gnu: error: in \`$ac_pwd':" 
>&2;}
| as_fn_error $? "failed to 

[sage-devel] Re: Building Sage 8.6 on Red Hat Enterprise Linux Server release 6.6 : mpir 3.0 error

[Samuel Lelievre]

Sun 2019-02-19 16:41:04 UTC+1, Sz Tengely:
>
> I try to build SageMath and I got the following error message:
>
> Setting up build directory for
> mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0
> Error: Unknown file type: /xxx/mpir-3.0.0-xxx.tar.bz2

This error suggests the need to install bzip2 to be able to extract
this bzip2 compressed tarball.

To install bzip2 under RHEL, it should be enough to run in a terminal:

sudo yum install bzip2

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

[sage-devel] Building Sage 8.6 on Red Hat Enterprise Linux Server release 6.6 : mpir 3.0 error

[Sz Tengely]

I try to build SageMath and I got the following error message:

Setting up build directory for 
mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec708
68.p0
Error: Unknown file type: 
/Lustre01/home/castor/sage-8.6/upstream/mpir-3.0.0-644
faf502c56f97d9accd301965fc57d6ec70868.tar.bz2
Finished extraction
/Lustre01/home/castor/sage-8.6/build/bin/sage-spkg: line 648: cd: src: No 
such f
ile or directory
No patch files found in ../patches
Error: There is no spkg-install script, no setup.py, and no configure
script, so I do not know how to install 
/Lustre01/home/castor/sage-8.6/upstream/
mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.tar.bz2.

and the appropriate part of install.log is given by:

Error building Sage.

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

* package: mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0
  log file: 
/Lustre01/home/castor/sage-8.6/logs/pkgs/mpir-3.0.0-644faf502c56f97d
9accd301965fc57d6ec70868.p0.log
  build directory: 
/Lustre01/home/castor/sage-8.6/local/var/tmp/sage/build/mpir-
3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0

As far as I see mpir is optional. Is there a way to disable it during the 
build procedure?
Thank you for the suggestions in advance.
Szabolcs

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

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Emmanuel Charpentier]

A couple of remarks :

Le dimanche 17 février 2019 13:17:12 UTC+1, Dima Pasechnik a écrit :
>
>
>
> On Sun, 17 Feb 2019 12:48 Emmanuel Charpentier   wrote:
>
>>
>>
>> Le dimanche 17 février 2019 09:34:10 UTC+1, Dima Pasechnik a écrit :
>>>
>>> Our plan is to enable the use of the system R install in Sage - for this 
>>> we need to understand whether there would be any problems for rpy2 if R 
>>> used a different, from the one in Sage, Blas library.
>>>
>>
We should be cautious with this one :

0.8.2 is our current reference because, AFAICT, it is the last version of 
rpy2 that supports Python2. If/when our plans to switch to Python3 succed 
(at last !), we should explore its newer versions. And switch to them if 
practical. But their requirements for numerics may vary...

Quite probably : In order to use the rjags 
>>  package 
>> (interface to the JAGS  Bayesian 
>> modelling sampler, I had to use the Sage shell in order to compile and 
>> install a version of JAGS in $SAGE_LOCAL : the system JAGS choked on 
>> BLAS/LAPACK calls not available in Sage's libraries.
>>
>> Things would be much simpler if Sage used the systemwide numeric 
>> libraries. I *think* that this is possible when these libraries are ATLAS : 
>> pointing SAGE_ATLAS_LIB to the systemwide ATLAS library makes Sage use 
>> them. ISTR that Erik Madison Bray recommended this to compile Sage on 
>> Cygwin (but I lost the reference to the relevant Sage Wiki post...). 
>>
>> My question was to know if this is possible when openblas provides the 
>> systemwide numerical libraries...
>>
>
> Not at the moment, but there are plans to make it possible.
> One should do more spkg-configure.m4 along the lines of #27212, where this 
> is done for gmp and mpir.
>

Is that possible for all of the current packages in Sage-the distribution ? 
Depending on one set (or possibly a coice of sets) of numerical libraries 
would allow us to get rid of them in Sage-the-distribution, which should 
lighten it considerably...

On Sat, 16 Feb 2019 13:40 Emmanuel Charpentier > wrote:
>>
>>> Trac#27303  needs review.

 Le samedi 16 février 2019 10:47:05 UTC+1, François Bissey a écrit :
>
>
>
> > On 16/02/2019, at 22:40, Emmanuel Charpentier <
> emanuel.c...@gmail.com> wrote: 
> > 
> > I see (modulo the legendary readability of m4, which has been 
> compared to line noise or a cat's nap on the keyboard...). 
> > 
>
> Any language is a bit like that when you don’t know it to be fair. 
> And you can produce line noise in most programming languages 
> but I’d pick perl and lisp over m4 for that. 
>
> Do open a ticket for sqlite upgrade, there may be other interesting 
> reasons to upgrade. 
>
> There may already be a ticket for making sqlite optional and if 
> you think m4 is looks like line noise you probably should leave 
> it to the pros.

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

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

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

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Emmanuel Charpentier]

Indeed.

Thanks for coming to the rescue of my aging neurons...

Le dimanche 17 février 2019 13:24:12 UTC+1, Samuel Lelievre a écrit :
>
> Sun 2019-02-17 12:48:52 UTC+1, Emmanuel Charpentier:
> >
> > Things would be much simpler if Sage used the systemwide numeric
> > libraries. I *think* that this is possible when these libraries are 
> ATLAS:
> > pointing SAGE_ATLAS_LIB to the systemwide ATLAS library makes
> > Sage use them. ISTR that Erik Madison Bray recommended this to
> > compile Sage on Cygwin (but I lost the reference to the relevant
> > Sage Wiki post...). 
>
> You might be referring to this page on the Sage Trac Wiki:
>
> https://trac.sagemath.org/wiki/Cygwin64Port#BuildingSage
>
>

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

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Samuel Lelievre]

Sun 2019-02-17 12:48:52 UTC+1, Emmanuel Charpentier:
>
> Things would be much simpler if Sage used the systemwide numeric
> libraries. I *think* that this is possible when these libraries are ATLAS:
> pointing SAGE_ATLAS_LIB to the systemwide ATLAS library makes
> Sage use them. ISTR that Erik Madison Bray recommended this to
> compile Sage on Cygwin (but I lost the reference to the relevant
> Sage Wiki post...). 

You might be referring to this page on the Sage Trac Wiki:

https://trac.sagemath.org/wiki/Cygwin64Port#BuildingSage

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

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Timo Kaufmann]

Am Sonntag, 17. Februar 2019 12:48:52 UTC+1 schrieb Emmanuel Charpentier:
>
>
>
> Le dimanche 17 février 2019 09:34:10 UTC+1, Dima Pasechnik a écrit :
>>
>> Our plan is to enable the use of the system R install in Sage - for this 
>> we need to understand whether there would be any problems for rpy2 if R 
>> used a different, from the one in Sage, Blas library.
>>
>
> Quite probably : In order to use the rjags 
>  package 
> (interface to the JAGS  Bayesian 
> modelling sampler, I had to use the Sage shell in order to compile and 
> install a version of JAGS in $SAGE_LOCAL : the system JAGS choked on 
> BLAS/LAPACK calls not available in Sage's libraries.
>
> Things would be much simpler if Sage used the systemwide numeric 
> libraries. I *think* that this is possible when these libraries are ATLAS : 
> pointing SAGE_ATLAS_LIB to the systemwide ATLAS library makes Sage use 
> them. ISTR that Erik Madison Bray recommended this to compile Sage on 
> Cygwin (but I lost the reference to the relevant Sage Wiki post...). 
>
> My question was to know if this is possible when openblas provides the 
> systemwide numerical libraries...
>

Setting `LD_DEBUG=libs` shows you which libraries are used at runtime. 
`LD_PRELOAD` can be useful to force the use of a particular blas 
implementation. 
 

>  
>
>> On Sat, 16 Feb 2019 13:40 Emmanuel Charpentier > wrote:
>>
>>> Trac#27303  needs review.
>>>
>>> Le samedi 16 février 2019 10:47:05 UTC+1, François Bissey a écrit :



 > On 16/02/2019, at 22:40, Emmanuel Charpentier  
 wrote: 
 > 
 > I see (modulo the legendary readability of m4, which has been 
 compared to line noise or a cat's nap on the keyboard...). 
 > 

 Any language is a bit like that when you don’t know it to be fair. 
 And you can produce line noise in most programming languages 
 but I’d pick perl and lisp over m4 for that. 

 Do open a ticket for sqlite upgrade, there may be other interesting 
 reasons to upgrade. 

 There may already be a ticket for making sqlite optional and if 
 you think m4 is looks like line noise you probably should leave 
 it to the pros.
>>>
>>> -- 
>>> 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.
>>>
>>

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

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Dima Pasechnik]

On Sun, 17 Feb 2019 12:48 Emmanuel Charpentier <
emanuel.charpent...@gmail.com wrote:

>
>
> Le dimanche 17 février 2019 09:34:10 UTC+1, Dima Pasechnik a écrit :
>>
>> Our plan is to enable the use of the system R install in Sage - for this
>> we need to understand whether there would be any problems for rpy2 if R
>> used a different, from the one in Sage, Blas library.
>>
>
> Quite probably : In order to use the rjags
>  package
> (interface to the JAGS  Bayesian
> modelling sampler, I had to use the Sage shell in order to compile and
> install a version of JAGS in $SAGE_LOCAL : the system JAGS choked on
> BLAS/LAPACK calls not available in Sage's libraries.
>
> Things would be much simpler if Sage used the systemwide numeric
> libraries. I *think* that this is possible when these libraries are ATLAS :
> pointing SAGE_ATLAS_LIB to the systemwide ATLAS library makes Sage use
> them. ISTR that Erik Madison Bray recommended this to compile Sage on
> Cygwin (but I lost the reference to the relevant Sage Wiki post...).
>
> My question was to know if this is possible when openblas provides the
> systemwide numerical libraries...
>

Not at the moment, but there are plans to make it possible.
One should do more spkg-configure.m4 along the lines of #27212, where this
is done for gmp and mpir.


>
>> On Sat, 16 Feb 2019 13:40 Emmanuel Charpentier > wrote:
>>
>>> Trac#27303  needs review.
>>>
>>> Le samedi 16 février 2019 10:47:05 UTC+1, François Bissey a écrit :



 > On 16/02/2019, at 22:40, Emmanuel Charpentier 
 wrote:
 >
 > I see (modulo the legendary readability of m4, which has been
 compared to line noise or a cat's nap on the keyboard...).
 >

 Any language is a bit like that when you don’t know it to be fair.
 And you can produce line noise in most programming languages
 but I’d pick perl and lisp over m4 for that.

 Do open a ticket for sqlite upgrade, there may be other interesting
 reasons to upgrade.

 There may already be a ticket for making sqlite optional and if
 you think m4 is looks like line noise you probably should leave
 it to the pros.
>>>
>>> --
>>> 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.
>>>
>> --
> 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.

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Emmanuel Charpentier]

Le dimanche 17 février 2019 09:34:10 UTC+1, Dima Pasechnik a écrit :
>
> Our plan is to enable the use of the system R install in Sage - for this 
> we need to understand whether there would be any problems for rpy2 if R 
> used a different, from the one in Sage, Blas library.
>

Quite probably : In order to use the rjags 
 package 
(interface to the JAGS  Bayesian 
modelling sampler, I had to use the Sage shell in order to compile and 
install a version of JAGS in $SAGE_LOCAL : the system JAGS choked on 
BLAS/LAPACK calls not available in Sage's libraries.

Things would be much simpler if Sage used the systemwide numeric libraries. 
I *think* that this is possible when these libraries are ATLAS : pointing 
SAGE_ATLAS_LIB to the systemwide ATLAS library makes Sage use them. ISTR 
that Erik Madison Bray recommended this to compile Sage on Cygwin (but I 
lost the reference to the relevant Sage Wiki post...). 

My question was to know if this is possible when openblas provides the 
systemwide numerical libraries...
 

> On Sat, 16 Feb 2019 13:40 Emmanuel Charpentier   wrote:
>
>> Trac#27303  needs review.
>>
>> Le samedi 16 février 2019 10:47:05 UTC+1, François Bissey a écrit :
>>>
>>>
>>>
>>> > On 16/02/2019, at 22:40, Emmanuel Charpentier  
>>> wrote: 
>>> > 
>>> > I see (modulo the legendary readability of m4, which has been compared 
>>> to line noise or a cat's nap on the keyboard...). 
>>> > 
>>>
>>> Any language is a bit like that when you don’t know it to be fair. 
>>> And you can produce line noise in most programming languages 
>>> but I’d pick perl and lisp over m4 for that. 
>>>
>>> Do open a ticket for sqlite upgrade, there may be other interesting 
>>> reasons to upgrade. 
>>>
>>> There may already be a ticket for making sqlite optional and if 
>>> you think m4 is looks like line noise you probably should leave 
>>> it to the pros.
>>
>> -- 
>> 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.
>>
>

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

Re: [sage-devel] Is there a way to force Sage to use system's openblas ?

[Dima Pasechnik]

Our plan is to enable the use of the system R install in Sage - for this we
need to understand whether there would be any problems for rpy2 if R used a
different, from the one in Sage, Blas library.

On Sat, 16 Feb 2019 13:40 Emmanuel Charpentier <
emanuel.charpent...@gmail.com wrote:

> Trac#27303  needs review.
>
> Le samedi 16 février 2019 10:47:05 UTC+1, François Bissey a écrit :
>>
>>
>>
>> > On 16/02/2019, at 22:40, Emmanuel Charpentier 
>> wrote:
>> >
>> > I see (modulo the legendary readability of m4, which has been compared
>> to line noise or a cat's nap on the keyboard...).
>> >
>>
>> Any language is a bit like that when you don’t know it to be fair.
>> And you can produce line noise in most programming languages
>> but I’d pick perl and lisp over m4 for that.
>>
>> Do open a ticket for sqlite upgrade, there may be other interesting
>> reasons to upgrade.
>>
>> There may already be a ticket for making sqlite optional and if
>> you think m4 is looks like line noise you probably should leave
>> it to the pros.
>
> --
> 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.