[sage-devel] Transpiling from Mathematica syntax to sage backends

2020-07-03 Thread Rocky Bernstein 
(I posted a much longer and more detailed version of this the other day, 
but I don't see it posted. So here is a shorter version)

I'm curious of any consideration has been giving for transpiling from one 
CAS syntax to another instead of or right before sage.repl.preparse(). 

In particular, I was thinking about using Mathematica syntax. 

If this gets through and there's interest, I can fill in more details.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/50cdac27-8e49-430b-999b-a5b73141a43cn%40googlegroups.com.

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Dima Pasechnik 
On Fri, Jul 3, 2020 at 2:34 PM Nicolo' Piazzalunga
 wrote:
>
> Sure, just let me know what to do.
> In the meantime, let me note that I can build both R-3.6.2 and R-4.0.2
> standalone with ./configure --with-x=no

you can go to the directory where R was being built by Sage
(where exactly you can see in logs/pkgs/r-3*.log file, at the end)
and inspect the parameters to configure used. Then you can try to
build R with these parameters.
Specifically, look into config.log, or run

./config.status --config




>
> On 7/3/20 3:30 PM, Matthias Koeppe wrote:
> > We will need your help to replicate a voidlinux system for testing – see
> > https://trac.sagemath.org/ticket/30044
> >
> > On Thursday, July 2, 2020 at 11:08:17 AM UTC-7, Nicolo' wrote:
> >
> > I can build R-4.0.2 as standalone, why does it fail in Sage?
> > As for ecl, perhaps wait until we can use system one?
> > At a lower priority, config is still not seeing python3, together with
> >
> > arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x gfan
> > givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc
> > m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata pari_galdata
> > pari_galpol pari_nftables pari_seadata pari_seadata_small
> > perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica tachyon
> >
> > On 7/1/20 3:45 PM, Michael Orlitzky wrote:
> >  > On 2020-07-01 09:23, Nicolo' Piazzalunga wrote:
> >  >> Thanks.
> >  >> I'm puzzled by 'does not support check for system package'/'no
> > suitable
> >  >> system package' in config.log
> >  >
> >  > We haven't written the script to detect a system copy of ECL yet.
> > We're
> >  > in the middle of upgrading to a new major version of it, and only
> > after
> >  > that's done will it make sense to detect a system copy (which
> > will have
> >  > to be brand new). See,
> >  >
> >  >* https://trac.sagemath.org/ticket/22191
> > 
> >  >* https://trac.sagemath.org/ticket/29617
> > 
> >  >
> >  >
> >  >> E.g. why is it not finding boost, isl, and why is it building
> > ecl (just
> >  >> to list a few), all of which are installed as system packages?
> >  >
> >  > I think Dima answered your question for these two, but in
> > general, you
> >  > can check config.log to see what decision the ./configure script
> > made
> >  > and why. If you need to dig further, the detection scripts are in
> >  >
> >  >build/pkgs//spkg-configure.m4
> >  >
> >  > in the sage source tree.
> >  >
> >
> > --
> > You received this message because you are subscribed to a topic in the
> > Google Groups "sage-devel" group.
> > To unsubscribe from this topic, visit
> > https://groups.google.com/d/topic/sage-devel/kiEh8JgbWeQ/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> > sage-devel+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/sage-devel/a8663175-7561-4b86-b905-3fd327a153e9o%40googlegroups.com
> > .
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/26f36654-2362-59be-346c-e80fabb7bca1%40gmail.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3P0UXKf9B8UX-qbPFWjUqGvRJrnAPztaP5ppTXe-vG7w%40mail.gmail.com.

[sage-devel] Re: [Bug] Possible Bug in FrobeniusMap for ntl finite fields of characteristic 2

2020-07-03 Thread Dave Morris 
This bug is discussed in trac ticket #28617 
 (which recently received a patch).

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/90133b60-c51a-47b7-ad5c-f2409f03b1a1o%40googlegroups.com.

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Matthias Koeppe 
Edit build/bin/sage-guess-package-system, 
build/bin/sage-print-system-package-command, build/bin/write-dockerfile.sh, 
tox.ini, and add voidlinux.txt files in build/pkgs/
similar to 
https://git.sagemath.org/sage.git/commit?id=eecd68a1a3cd6046a6ae0d4b5eb57895ee34a1ba

More info: 
https://doc.sagemath.org/html/en/developer/portability_testing.html#testing-sage-on-a-different-platform-using-docker

On Friday, July 3, 2020 at 6:34:23 AM UTC-7, Nicolo' wrote:
>
> Sure, just let me know what to do. 
> In the meantime, let me note that I can build both R-3.6.2 and R-4.0.2 
> standalone with ./configure --with-x=no 
>
> On 7/3/20 3:30 PM, Matthias Koeppe wrote: 
> > We will need your help to replicate a voidlinux system for testing – see 
> > https://trac.sagemath.org/ticket/30044 
> > 
> > On Thursday, July 2, 2020 at 11:08:17 AM UTC-7, Nicolo' wrote: 
> > 
> > I can build R-4.0.2 as standalone, why does it fail in Sage? 
> > As for ecl, perhaps wait until we can use system one? 
> > At a lower priority, config is still not seeing python3, together 
> with 
> > 
> > arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x 
> gfan 
> > givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups 
> lrcalc 
> > m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata 
> pari_galdata 
> > pari_galpol pari_nftables pari_seadata pari_seadata_small 
> > perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica 
> tachyon 
> > 
> > On 7/1/20 3:45 PM, Michael Orlitzky wrote: 
> >  > On 2020-07-01 09:23, Nicolo' Piazzalunga wrote: 
> >  >> Thanks. 
> >  >> I'm puzzled by 'does not support check for system package'/'no 
> > suitable 
> >  >> system package' in config.log 
> >  > 
> >  > We haven't written the script to detect a system copy of ECL yet. 
> > We're 
> >  > in the middle of upgrading to a new major version of it, and only 
> > after 
> >  > that's done will it make sense to detect a system copy (which 
> > will have 
> >  > to be brand new). See, 
> >  > 
> >  >* https://trac.sagemath.org/ticket/22191 
> >  
> >  >* https://trac.sagemath.org/ticket/29617 
> >  
> >  > 
> >  > 
> >  >> E.g. why is it not finding boost, isl, and why is it building 
> > ecl (just 
> >  >> to list a few), all of which are installed as system packages? 
> >  > 
> >  > I think Dima answered your question for these two, but in 
> > general, you 
> >  > can check config.log to see what decision the ./configure script 
> > made 
> >  > and why. If you need to dig further, the detection scripts are in 
> >  > 
> >  >build/pkgs//spkg-configure.m4 
> >  > 
> >  > in the sage source tree. 
> >  > 
> > 
> > -- 
> > You received this message because you are subscribed to a topic in the 
> > Google Groups "sage-devel" group. 
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/sage-devel/kiEh8JgbWeQ/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> > sage-...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/sage-devel/a8663175-7561-4b86-b905-3fd327a153e9o%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/sage-devel/a8663175-7561-4b86-b905-3fd327a153e9o%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3dd13c93-6fcb-497b-8f92-fadb402f99d6o%40googlegroups.com.

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Nicolo' Piazzalunga 

Sure, just let me know what to do.
In the meantime, let me note that I can build both R-3.6.2 and R-4.0.2 
standalone with ./configure --with-x=no


On 7/3/20 3:30 PM, Matthias Koeppe wrote:
We will need your help to replicate a voidlinux system for testing – see 
https://trac.sagemath.org/ticket/30044


On Thursday, July 2, 2020 at 11:08:17 AM UTC-7, Nicolo' wrote:

I can build R-4.0.2 as standalone, why does it fail in Sage?
As for ecl, perhaps wait until we can use system one?
At a lower priority, config is still not seeing python3, together with

arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x gfan
givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc
m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata pari_galdata
pari_galpol pari_nftables pari_seadata pari_seadata_small
perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica tachyon

On 7/1/20 3:45 PM, Michael Orlitzky wrote:
 > On 2020-07-01 09:23, Nicolo' Piazzalunga wrote:
 >> Thanks.
 >> I'm puzzled by 'does not support check for system package'/'no
suitable
 >> system package' in config.log
 >
 > We haven't written the script to detect a system copy of ECL yet.
We're
 > in the middle of upgrading to a new major version of it, and only
after
 > that's done will it make sense to detect a system copy (which
will have
 > to be brand new). See,
 >
 >    * https://trac.sagemath.org/ticket/22191

 >    * https://trac.sagemath.org/ticket/29617

 >
 >
 >> E.g. why is it not finding boost, isl, and why is it building
ecl (just
 >> to list a few), all of which are installed as system packages?
 >
 > I think Dima answered your question for these two, but in
general, you
 > can check config.log to see what decision the ./configure script
made
 > and why. If you need to dig further, the detection scripts are in
 >
 >    build/pkgs//spkg-configure.m4
 >
 > in the sage source tree.
 >

--
You received this message because you are subscribed to a topic in the 
Google Groups "sage-devel" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/sage-devel/kiEh8JgbWeQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
sage-devel+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a8663175-7561-4b86-b905-3fd327a153e9o%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/26f36654-2362-59be-346c-e80fabb7bca1%40gmail.com.

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Matthias Koeppe 
We will need your help to replicate a voidlinux system for testing – see 
https://trac.sagemath.org/ticket/30044

On Thursday, July 2, 2020 at 11:08:17 AM UTC-7, Nicolo' wrote:
>
> I can build R-4.0.2 as standalone, why does it fail in Sage? 
> As for ecl, perhaps wait until we can use system one? 
> At a lower priority, config is still not seeing python3, together with 
>
> arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x gfan 
> givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc 
> m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata pari_galdata 
> pari_galpol pari_nftables pari_seadata pari_seadata_small 
> perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica tachyon 
>
> On 7/1/20 3:45 PM, Michael Orlitzky wrote: 
> > On 2020-07-01 09:23, Nicolo' Piazzalunga wrote: 
> >> Thanks. 
> >> I'm puzzled by 'does not support check for system package'/'no suitable 
> >> system package' in config.log 
> > 
> > We haven't written the script to detect a system copy of ECL yet. We're 
> > in the middle of upgrading to a new major version of it, and only after 
> > that's done will it make sense to detect a system copy (which will have 
> > to be brand new). See, 
> > 
> >* https://trac.sagemath.org/ticket/22191 
> >* https://trac.sagemath.org/ticket/29617 
> > 
> > 
> >> E.g. why is it not finding boost, isl, and why is it building ecl (just 
> >> to list a few), all of which are installed as system packages? 
> > 
> > I think Dima answered your question for these two, but in general, you 
> > can check config.log to see what decision the ./configure script made 
> > and why. If you need to dig further, the detection scripts are in 
> > 
> >build/pkgs//spkg-configure.m4 
> > 
> > in the sage source tree. 
> > 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a8663175-7561-4b86-b905-3fd327a153e9o%40googlegroups.com.

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Dima Pasechnik 
On Fri, 3 Jul 2020, 13:33 Nicolo' Piazzalunga, 
wrote:

> Let me clarify: my problem is that Sage still fails to build (r and ecl
> give errors).
> As for ecl, I think I understand the problem (a patch is needed for
> musl), but could ecl trigger failure of r, which I can however build as
> a standalone?
>

you might want to try ecl from

https://trac.sagemath.org/ticket/22191

(by using the branch from that ticket you'd use Sage 9.2.beta2 + that
change)

As to R (which is not related to ecl in any way), I really don't know.
Something with iconv library.



> At this stage, I have no issues building stuff that could have been
> taken from system.
> There are no libgd nor libR available, so it builds them.
> Ecl cannot be taken from system at present.
> Isl is too old, so it builds it.
> Python 3.8.3 is too recent, so it builds it.
> I installed gmpxx-devel 6.2.0.
>
> On 7/3/20 12:39 PM, Dima Pasechnik wrote:
> > Your gmp installation is incomplete, missing C++ support,
> > therefore all the packages that depend on gmp are installed,and not
> > taken from the system.
> > And there are dozens such packages, eg mpfr,ntl, arb, flint, pari,
> eclib...
> >
> > from your config.log:
> >
> > configure:10030: checking gmp.h usability
> > configure:10030: g++ -std=gnu++11 -c -g -O2  conftest.cpp >&5
> > configure:10030: $? = 0
> > configure:10030: result: yes
> > configure:10030: checking gmp.h presence
> > configure:10030: g++ -E -std=gnu++11  conftest.cpp
> > configure:10030: $? = 0
> > configure:10030: result: yes
> > configure:10030: checking for gmp.h
> > configure:10030: result: yes
> > configure:10038: checking gmpxx.h usability
> > configure:10038: g++ -std=gnu++11 -c -g -O2  conftest.cpp >&5
> > conftest.cpp:56:10: fatal error: gmpxx.h: No such file or directory
> >
> > Further, system libgd/gdlib is either not installed, or not
> well-configured:
> >
> > configure:22938: $PKG_CONFIG --exists --print-errors "gdlib >= 2.1"
> > Package gdlib was not found in the pkg-config search path.
> >
> > similarly, R - it needs  libR, maybe a separate component on your system
> >
> > configure:28542: checking for R
> > configure:28549: $PKG_CONFIG --exists --print-errors "libR >= $3.4.4"
> > Package libR was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `libR.pc'
> > to the PKG_CONFIG_PATH environment variable
> >
> > On Fri, Jul 3, 2020 at 10:10 AM Nicolo' Piazzalunga
> >  wrote:
> >>
> >> Sure,
> >> tar xvf sage-9.1.tar.gz
> >> cd sage-9.1
> >> ./configure
> >> gives this.
> >>
> >> On 7/2/20 8:14 PM, Dima Pasechnik wrote:
> >>> On Thu, Jul 2, 2020 at 7:08 PM Nicolo' Piazzalunga
> >>>  wrote:
> 
>  I can build R-4.0.2 as standalone, why does it fail in Sage?
>  As for ecl, perhaps wait until we can use system one?
>  At a lower priority, config is still not seeing python3, together with
> 
>  arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x
> gfan
>  givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc
>  m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata pari_galdata
>  pari_galpol pari_nftables pari_seadata pari_seadata_small
>  perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica
> tachyon
> >>>
> >>> Could you post what you get in config.log after running ./configure
> >>> either on a fresh installation, or after
> >>> make distclean
> >>> ?
> >>>
> 
>  On 7/1/20 3:45 PM, Michael Orlitzky wrote:
> > On 2020-07-01 09:23, Nicolo' Piazzalunga wrote:
> >> Thanks.
> >> I'm puzzled by 'does not support check for system package'/'no
> suitable
> >> system package' in config.log
> >
> > We haven't written the script to detect a system copy of ECL yet.
> We're
> > in the middle of upgrading to a new major version of it, and only
> after
> > that's done will it make sense to detect a system copy (which will
> have
> > to be brand new). See,
> >
> >  * https://trac.sagemath.org/ticket/22191
> >  * https://trac.sagemath.org/ticket/29617
> >
> >
> >> E.g. why is it not finding boost, isl, and why is it building ecl
> (just
> >> to list a few), all of which are installed as system packages?
> >
> > I think Dima answered your question for these two, but in general,
> you
> > can check config.log to see what decision the ./configure script made
> > and why. If you need to dig further, the detection scripts are in
> >
> >  build/pkgs//spkg-configure.m4
> >
> > in the sage source tree.
> >
> 
>  --
>  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 view this discussion on the web visit
>

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Nicolo' Piazzalunga 
Let me clarify: my problem is that Sage still fails to build (r and ecl 
give errors).
As for ecl, I think I understand the problem (a patch is needed for 
musl), but could ecl trigger failure of r, which I can however build as 
a standalone?


At this stage, I have no issues building stuff that could have been 
taken from system.

There are no libgd nor libR available, so it builds them.
Ecl cannot be taken from system at present.
Isl is too old, so it builds it.
Python 3.8.3 is too recent, so it builds it.
I installed gmpxx-devel 6.2.0.

On 7/3/20 12:39 PM, Dima Pasechnik wrote:

Your gmp installation is incomplete, missing C++ support,
therefore all the packages that depend on gmp are installed,and not
taken from the system.
And there are dozens such packages, eg mpfr,ntl, arb, flint, pari, eclib...

from your config.log:

configure:10030: checking gmp.h usability
configure:10030: g++ -std=gnu++11 -c -g -O2  conftest.cpp >&5
configure:10030: $? = 0
configure:10030: result: yes
configure:10030: checking gmp.h presence
configure:10030: g++ -E -std=gnu++11  conftest.cpp
configure:10030: $? = 0
configure:10030: result: yes
configure:10030: checking for gmp.h
configure:10030: result: yes
configure:10038: checking gmpxx.h usability
configure:10038: g++ -std=gnu++11 -c -g -O2  conftest.cpp >&5
conftest.cpp:56:10: fatal error: gmpxx.h: No such file or directory

Further, system libgd/gdlib is either not installed, or not well-configured:

configure:22938: $PKG_CONFIG --exists --print-errors "gdlib >= 2.1"
Package gdlib was not found in the pkg-config search path.

similarly, R - it needs  libR, maybe a separate component on your system

configure:28542: checking for R
configure:28549: $PKG_CONFIG --exists --print-errors "libR >= $3.4.4"
Package libR was not found in the pkg-config search path.
Perhaps you should add the directory containing `libR.pc'
to the PKG_CONFIG_PATH environment variable

On Fri, Jul 3, 2020 at 10:10 AM Nicolo' Piazzalunga
 wrote:


Sure,
tar xvf sage-9.1.tar.gz
cd sage-9.1
./configure
gives this.

On 7/2/20 8:14 PM, Dima Pasechnik wrote:

On Thu, Jul 2, 2020 at 7:08 PM Nicolo' Piazzalunga
 wrote:


I can build R-4.0.2 as standalone, why does it fail in Sage?
As for ecl, perhaps wait until we can use system one?
At a lower priority, config is still not seeing python3, together with

arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x gfan
givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc
m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata pari_galdata
pari_galpol pari_nftables pari_seadata pari_seadata_small
perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica tachyon


Could you post what you get in config.log after running ./configure
either on a fresh installation, or after
make distclean
?



On 7/1/20 3:45 PM, Michael Orlitzky wrote:

On 2020-07-01 09:23, Nicolo' Piazzalunga wrote:

Thanks.
I'm puzzled by 'does not support check for system package'/'no suitable
system package' in config.log


We haven't written the script to detect a system copy of ECL yet. We're
in the middle of upgrading to a new major version of it, and only after
that's done will it make sense to detect a system copy (which will have
to be brand new). See,

 * https://trac.sagemath.org/ticket/22191
 * https://trac.sagemath.org/ticket/29617



E.g. why is it not finding boost, isl, and why is it building ecl (just
to list a few), all of which are installed as system packages?


I think Dima answered your question for these two, but in general, you
can check config.log to see what decision the ./configure script made
and why. If you need to dig further, the detection scripts are in

 build/pkgs//spkg-configure.m4

in the sage source tree.



--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d26696ae-c476-ba52-6929-2f6f192487c1%40gmail.com.




--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9c48c08a-98c7-0ae9-75a1-a373e3f9c3e8%40gmail.com.




--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4efcc301-8778-f16a-43ee-d2706a1b2f56%40gmail.com.

Re: [sage-devel] build errors on void linux

2020-07-03 Thread Dima Pasechnik 
Your gmp installation is incomplete, missing C++ support,
therefore all the packages that depend on gmp are installed,and not
taken from the system.
And there are dozens such packages, eg mpfr,ntl, arb, flint, pari, eclib...

from your config.log:

configure:10030: checking gmp.h usability
configure:10030: g++ -std=gnu++11 -c -g -O2  conftest.cpp >&5
configure:10030: $? = 0
configure:10030: result: yes
configure:10030: checking gmp.h presence
configure:10030: g++ -E -std=gnu++11  conftest.cpp
configure:10030: $? = 0
configure:10030: result: yes
configure:10030: checking for gmp.h
configure:10030: result: yes
configure:10038: checking gmpxx.h usability
configure:10038: g++ -std=gnu++11 -c -g -O2  conftest.cpp >&5
conftest.cpp:56:10: fatal error: gmpxx.h: No such file or directory

Further, system libgd/gdlib is either not installed, or not well-configured:

configure:22938: $PKG_CONFIG --exists --print-errors "gdlib >= 2.1"
Package gdlib was not found in the pkg-config search path.

similarly, R - it needs  libR, maybe a separate component on your system

configure:28542: checking for R
configure:28549: $PKG_CONFIG --exists --print-errors "libR >= $3.4.4"
Package libR was not found in the pkg-config search path.
Perhaps you should add the directory containing `libR.pc'
to the PKG_CONFIG_PATH environment variable

On Fri, Jul 3, 2020 at 10:10 AM Nicolo' Piazzalunga
 wrote:
>
> Sure,
> tar xvf sage-9.1.tar.gz
> cd sage-9.1
> ./configure
> gives this.
>
> On 7/2/20 8:14 PM, Dima Pasechnik wrote:
> > On Thu, Jul 2, 2020 at 7:08 PM Nicolo' Piazzalunga
> >  wrote:
> >>
> >> I can build R-4.0.2 as standalone, why does it fail in Sage?
> >> As for ecl, perhaps wait until we can use system one?
> >> At a lower priority, config is still not seeing python3, together with
> >>
> >> arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x gfan
> >> givaro glpk gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc
> >> m4ri m4rie mpc mpfi mpfr mpir nauty ntl pari pari_elldata pari_galdata
> >> pari_galpol pari_nftables pari_seadata pari_seadata_small
> >> perl_cpan_polymake_prereq planarity ppl python3 r rw symmetrica tachyon
> >
> > Could you post what you get in config.log after running ./configure
> > either on a fresh installation, or after
> > make distclean
> > ?
> >
> >>
> >> On 7/1/20 3:45 PM, Michael Orlitzky wrote:
> >>> On 2020-07-01 09:23, Nicolo' Piazzalunga wrote:
>  Thanks.
>  I'm puzzled by 'does not support check for system package'/'no suitable
>  system package' in config.log
> >>>
> >>> We haven't written the script to detect a system copy of ECL yet. We're
> >>> in the middle of upgrading to a new major version of it, and only after
> >>> that's done will it make sense to detect a system copy (which will have
> >>> to be brand new). See,
> >>>
> >>> * https://trac.sagemath.org/ticket/22191
> >>> * https://trac.sagemath.org/ticket/29617
> >>>
> >>>
>  E.g. why is it not finding boost, isl, and why is it building ecl (just
>  to list a few), all of which are installed as system packages?
> >>>
> >>> I think Dima answered your question for these two, but in general, you
> >>> can check config.log to see what decision the ./configure script made
> >>> and why. If you need to dig further, the detection scripts are in
> >>>
> >>> build/pkgs//spkg-configure.m4
> >>>
> >>> in the sage source tree.
> >>>
> >>
> >> --
> >> 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 view this discussion on the web visit 
> >> https://groups.google.com/d/msgid/sage-devel/d26696ae-c476-ba52-6929-2f6f192487c1%40gmail.com.
> >
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/9c48c08a-98c7-0ae9-75a1-a373e3f9c3e8%40gmail.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1czXVWAE8KAz%2BdE99d3ANhgVz7wdPuEid2e0VbYzNYKA%40mail.gmail.com.