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

2020-09-17 Thread Nicolo' Piazzalunga 

Problem seems now solved.
I updated ticket #30539, where I included extra pari spkgs.

Thanks.

--
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/ec2ce4f1-352d-cc22-4f53-12a2699d35c0%40gmail.com.

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

2020-09-16 Thread Nicolo' Piazzalunga 

Same from gp prompt:

? poldegree(ellmodulareqn(211)[1])
  ***   at top-level: poldegree(ellmodulareqn(211)[1])
  ***   ^--
  *** ellmodulareqn: error opening seadata file: 
`/usr/share/pari/seadata/sea211'.

  ***   Break loop: type 'break' to go back to GP prompt

You're right, there's a permission issue:

ls -l /usr/share/pari/seadata/sea211
-rw-r--r-- 1 root root 194468 Sep 15 12:01 /usr/share/pari/seadata/sea211

Thanks.

On 9/16/20 2:45 PM, Dima Pasechnik wrote:

On Wed, Sep 16, 2020 at 1:33 PM Nicolo' Piazzalunga
 wrote:


It was on a fresh install, see the attached config.log


does

poldegree(ellmodulareqn(211)[1])

work at the gp prompt, interactively (with the same user id as used
for running ./configure)
(more precisely, your gp is found in /bin/, so you might want to check
that /bin/gp and gp are the same
thing if run from the shell)

I guess it might be wrong file permissions for a part of
/usr/share/pari/ - as tests for other data packages there succeed

configure:17333: checking for gp
configure:17351: found /bin/gp
configure:17363: result: /bin/gp
configure:17377: checking for gphelp
configure:17395: found /bin/gphelp
configure:17407: result: /bin/gphelp
configure:17424: checking whether gphelp has access to the documentation
configure:17427: result: yes
configure:17439: checking is pari_elldata installed?
configure:17443: result: yes
configure:17454: checking is pari_galdata installed?
configure:17458: result: yes
configure:17469: checking is pari_galpol installed?
configure:17473: result: yes
configure:17484: checking is pari_seadata installed?
   ***   at top-level: poldegree(ellmodulareqn(211)[1])
   ***   ^--
   *** ellmodulareqn: error opening seadata file:
`/usr/share/pari/seadata/sea211'.

What are the permissions of /usr/share/pari/seadata/sea211 ?
(i.e. the output of
ls -l /usr/share/pari/seadata/sea211
please)





--
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/5eb2af5a-6f49-d6be-bebd-a84f455133a2%40gmail.com.

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

2020-09-16 Thread Nicolo' Piazzalunga 

Thanks. I get:

? default(datadir)
%1 = "/usr/share/pari"

so it seems it is correctly configured, but still not detected..


On 9/15/20 6:59 PM, Dima Pasechnik wrote:



On Tue, Sep 15, 2020 at 2:11 PM Nicolo' Piazzalunga 
mailto:nicolopiazzalu...@gmail.com>> wrote:


I did it.

On 9/8/20 5:39 PM, Dima Pasechnik wrote:
 > sure - can you do this yourself?

It seems sage is still unable to detect my pari-seadata package, even
though the file /usr/share/pari/seadata/sea211 is present on my system.

Do you know what the problem could be?



I think it looks at Pari/GP datadir to locate these files. What's its value?
At GP prompt, type

? default(datadir)

and see (e.g.)

%1 = "/usr/local/share/pari"

in this case GP expects seadata to be in
/usr/local/share/pari/seadata/

HTH
Dima

  configure:17484: checking is pari_seadata installed?
    ***   at top-level: poldegree(ellmodulareqn(211)[1])
    ***                           ^--
    *** ellmodulareqn: error opening seadata file:
`/usr/share/pari/seadata/sea211'.


gp_seadat_check=`echo "poldegree(ellmodulareqn(211)[1])" | $GP -qf 2>>
config.log`
if test x$gp_seadat_check = x212; then
          { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }


Thanks.



--
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/56132297-ac87-c675-72f1-92c33a74c5f3%40gmail.com.

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

2020-09-15 Thread Nicolo' Piazzalunga 

I did it.

On 9/8/20 5:39 PM, Dima Pasechnik wrote:

sure - can you do this yourself?


It seems sage is still unable to detect my pari-seadata package, even 
though the file /usr/share/pari/seadata/sea211 is present on my system.


Do you know what the problem could be?


configure:17484: checking is pari_seadata installed?
  ***   at top-level: poldegree(ellmodulareqn(211)[1])
  ***   ^--
  *** ellmodulareqn: error opening seadata file: 
`/usr/share/pari/seadata/sea211'.



gp_seadat_check=`echo "poldegree(ellmodulareqn(211)[1])" | $GP -qf 2>> 
config.log`

if test x$gp_seadat_check = x212; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 
$as_echo "yes" >&6; }



Thanks.

--
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/d2a4b9ff-9765-e68b-2f83-f63216dd752c%40gmail.com.

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

2020-09-08 Thread Nicolo' Piazzalunga 

Would it be possible to create a new trac ticket with more void spkg's?
I attach a patch for pari subpackages (waiting to be merged in void).
Leaving it open for a while will simplify adding spkg's and building.

Thanks.

--
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/f750e2fa-c832-62eb-c9aa-4ae551704887%40gmail.com.
From 79e7971a1477705a8f1828a0135dd8eea4c4c844 Mon Sep 17 00:00:00 2001
From: Nicolo' Piazzalunga 
Date: Tue, 8 Sep 2020 17:16:31 +0200
Subject: [PATCH] pari-additional packages

---
 build/pkgs/pari/distros/void.txt | 4 
 build/pkgs/pari_elldata/distros/void.txt | 1 +
 build/pkgs/pari_galdata/distros/void.txt | 1 +
 build/pkgs/pari_galpol/distros/void.txt  | 1 +
 build/pkgs/pari_seadata/distros/void.txt | 1 +
 5 files changed, 8 insertions(+)
 create mode 100644 build/pkgs/pari_elldata/distros/void.txt
 create mode 100644 build/pkgs/pari_galdata/distros/void.txt
 create mode 100644 build/pkgs/pari_galpol/distros/void.txt
 create mode 100644 build/pkgs/pari_seadata/distros/void.txt

diff --git a/build/pkgs/pari/distros/void.txt b/build/pkgs/pari/distros/void.txt
index 7c8f04b36a..0a6a6eb296 100644
--- a/build/pkgs/pari/distros/void.txt
+++ b/build/pkgs/pari/distros/void.txt
@@ -1,2 +1,6 @@
 pari
 pari-devel
+pari-elldata
+pari-galdata
+pari-galpol
+pari-seadata
diff --git a/build/pkgs/pari_elldata/distros/void.txt 
b/build/pkgs/pari_elldata/distros/void.txt
new file mode 100644
index 00..540f0b1ab8
--- /dev/null
+++ b/build/pkgs/pari_elldata/distros/void.txt
@@ -0,0 +1 @@
+pari-elldata
diff --git a/build/pkgs/pari_galdata/distros/void.txt 
b/build/pkgs/pari_galdata/distros/void.txt
new file mode 100644
index 00..38ad64bac8
--- /dev/null
+++ b/build/pkgs/pari_galdata/distros/void.txt
@@ -0,0 +1 @@
+pari-galdata
diff --git a/build/pkgs/pari_galpol/distros/void.txt 
b/build/pkgs/pari_galpol/distros/void.txt
new file mode 100644
index 00..e3b41380f4
--- /dev/null
+++ b/build/pkgs/pari_galpol/distros/void.txt
@@ -0,0 +1 @@
+pari-galpol
diff --git a/build/pkgs/pari_seadata/distros/void.txt 
b/build/pkgs/pari_seadata/distros/void.txt
new file mode 100644
index 00..3abdcf7bfc
--- /dev/null
+++ b/build/pkgs/pari_seadata/distros/void.txt
@@ -0,0 +1 @@
+pari-seadata
--
2.28.0

[sage-devel] pari-seadata

2020-09-01 Thread Nicolo' Piazzalunga 
I have a slight confusion: for pari, does sage need the seadata package, 
or is the -small version enough?


Thanks.

--
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/d94cc500-4c2e-9674-4740-ad23a63c8e89%40gmail.com.

[sage-devel] packaging sage on void linux

2020-08-25 Thread Nicolo' Piazzalunga 
We are now able to build sage on void linux by using ./bootstrap, 
./configure and make; everything is installed in some local folder, 
since make install is a no-op.



Trying to package it, using as many system packages as possible, and 
taking advantage of its build and configure features,
is it possible (1) to just move the whole thing, by copying some files 
to the appropriate /usr/bin (or similar) and making some changes?
or is it better (2) to translate the configure/build scripts into the 
xbps-source (Void Linux native packaging system, [1]) language, such 
that for example one can still use ./configure, but what it does is 
instruct xbps-source to build missing packages as system packages with 
appropriate build options?



Thanks.


[1] https://github.com/void-linux/void-packages/blob/master/Manual.md

--
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/5a6bfe5a-a9a9-6838-0068-bda813205d67%40gmail.com.

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

2020-08-22 Thread Nicolo' Piazzalunga 

On 8/21/20 7:19 PM, Samuel Lelievre wrote:
>
> The ticket to upgrade Sage-the-distribution to Python 3.8
> just got positive review:
>
>https://trac.sagemath.org/ticket/27754
>

Thanks. I also give it a positive review, hopefully it'll be merged 
soon. Now on my Void machine sage builds in 30m (previously 1h 30m).



As for doctest errors, it's as before, except misc/gperftools.py failure 
disappeared. Is it to be expected to get these failures when building 
beta8 version?


--
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/eff6581f-f488-175f-c281-b90bd9498b48%40gmail.com.

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

2020-08-21 Thread Nicolo' Piazzalunga 

Finally sage builds successfully on void linux :)
I will add spkg files for pari-seadata etc as soon as the packages are 
approved, this way it does not have to build pari and giac.


Is there a ticket already to use python3.8 from system?

Should I be worried that it fails some doctest?

sage -t --random-seed=0 src/sage/interfaces/interface.py  # 10 doctests 
failed

sage -t --random-seed=0 src/sage/interfaces/r.py  # 191 doctests failed
sage -t --random-seed=0 src/sage/interfaces/giac.py  # 2 doctests failed
sage -t --random-seed=0 src/sage/symbolic/expression.pyx  # 1 doctest failed
sage -t --random-seed=0 src/sage/lfunctions/sympow.py  # 3 doctests failed
sage -t --random-seed=0 src/sage/stats/r.py  # 1 doctest failed
sage -t --random-seed=0 src/sage/misc/sageinspect.py  # 1 doctest failed
sage -t --random-seed=0 src/sage/misc/gperftools.py  # 1 doctest failed
sage -t --random-seed=0 src/sage/repl/ipython_tests.py  # 2 doctests failed
sage -t --random-seed=0 
src/doc/en/prep/Quickstarts/Statistics-and-Distributions.rst  # 6 
doctests failed


Thanks.

--
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/5f45330b-dba0-7450-2c4c-9a6a0624a58d%40gmail.com.

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

2020-08-19 Thread Nicolo' Piazzalunga 

these missing pari/gp parts are just data, easy to packageGood, working on that.

In the meantime, it is useful to add a few pkgs to bootstrap (attached).

--
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/cb342d98-a27e-4b76-c105-ef98ed5bd8c6%40gmail.com.
>From 9229263fff1c25ac197d868b8f056ca53cf3a569 Mon Sep 17 00:00:00 2001
From: Nicolo' Piazzalunga 
Date: Wed, 19 Aug 2020 17:17:07 +0200
Subject: [PATCH] added two

---
 build/pkgs/void-bootstrap.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/build/pkgs/void-bootstrap.txt b/build/pkgs/void-bootstrap.txt
index b8a4585cf1..3b19fa5069 100644
--- a/build/pkgs/void-bootstrap.txt
+++ b/build/pkgs/void-bootstrap.txt
@@ -1,3 +1,4 @@
 # Packages needed for ./bootstrap
 gettext autoconf automake libtool pkg-config
 gettext-devel
+xtools mk-configure
--
2.28.0

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

2020-08-19 Thread Nicolo' Piazzalunga 

On 8/18/20 5:03 PM, Matthias Koeppe wrote:
> Try again after "./bootstrap" (this needs autotools installed)

Thanks, now it checks, but since pari misses some parts, it doesn't 
detect giac either.


## - ##
## Checking whether SageMath should install SPKG giac... ##
## - ##
configure:20077: checking whether any of pari is installed as or will be 
installed as SPKG

configure:20081: result: yes; install giac as well
configure:20296: no suitable system package found for SPKG giac

## - ##
## Checking whether SageMath should install SPKG pari... ##
## - ##
configure:17312: checking whether any of gmp mpir readline is installed 
as or will be installed as SPKG

configure:17321: result: no
configure:17326: checking for gp
configure:17344: found /bin/gp
configure:17356: result: /bin/gp
configure:17370: checking for gphelp
configure:17388: found /bin/gphelp
configure:17400: result: /bin/gphelp
configure:17417: checking whether gphelp has access to the documentation
configure:17420: result: yes
configure:17432: checking is pari_elldata installed?
  ***   at top-level: r=ellinit("11a1");r[11]
  ***   ^-
  *** ellinit: error opening elldata file: `/usr/share/pari/elldata/ell0'.
configure:17439: result: no; cannot use system pari/GP without elldata 
package

configure:17441: Install elldata package and reconfigure.
configure:17443: Otherwise Sage will build its own pari/GP.
configure:17447: checking is pari_galdata installed?
  ***   at top-level: polgalois(x^8-2)[1]
  *** ^---
  *** polgalois: error opening galois file: 
`/usr/share/pari/galdata/COS8_50_47'.
configure:17454: result: no; cannot use system pari/GP without galdata 
package

configure:17456: Install galdata package and reconfigure.
configure:17458: Otherwise Sage will build its own pari/GP.
configure:17462: checking is pari_galpol installed?
  ***   at top-level: galoisgetname(12,1)=="C3 : C4"
  *** ^--
  *** galoisgetname: error opening galpol file: 
`/usr/share/pari/galpol/12/nb'.
configure:17469: result: no; cannot use system pari/GP without galpol 
package

configure:17471: Install galpol package and reconfigure.
configure:17473: Otherwise Sage will build its own pari/GP.
configure:17477: checking is pari_seadata installed?
  ***   at top-level: poldegree(ellmodulareqn(211)[1])
  ***   ^--
  *** ellmodulareqn: error opening seadata file: 
`/usr/share/pari/seadata/sea211'.
configure:17484: result: no; cannot use system pari/GP without seadata 
package

configure:17486: Install seadata package and reconfigure.
configure:17488: Otherwise Sage will build its own pari/GP.
configure:17492: checking whether hyperellcharpoly bug is fixed
configure:17497: result: yes
configure:17508: checking whether bnfisunit bug of pari 2.11.3 is fixed
configure:17513: result: yes
configure:17750: no suitable system package found for SPKG pari

--
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/72f51a7a-f860-d404-7272-872352677738%40gmail.com.

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

2020-08-18 Thread Nicolo' Piazzalunga 

Thanks, I figured out almost all my issues.
Except, only mention of giac in config.log is

giac-1.5.0.87: does not support check for system package

Shouldn't it be able to check it by now?
I attach a patch for R and isl15-devel.

On 8/18/20 3:25 PM, Matthias Koeppe wrote:

config.log has more information on why packages are rejected

On Tuesday, August 18, 2020 at 1:37:09 AM UTC-7, Nicolo' wrote:

After importing
u/mkoeppe/spkg_configure_m4_for_giac
u/mkoeppe/more_voidlinux_txt
and d43730c (should this appear in beta9?),
I still get

the following SPKGs did not find equivalent system packages: arb brial
cddlib cliquer coxeter3 eclib fflas_ffpack flint flintqs fplll gf2x
gfan
givaro gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc m4ri
m4rie mpfi nauty ntl palp pari pari_elldata pari_galdata pari_galpol
pari_nftables pari_seadata pari_seadata_small perl_cpan_polymake_prereq
planarity python3 r rw suitesparse symmetrica sympow tachyon zn_poly

checking for the package system in use... void
configure: hint: installing the following system packages is
recommended
and may avoid building some of the above SPKGs from source:
configure:   $ sudo xbps-install flint imlib2-devel isl16-devel pari
pari-devel python3 python3-devel rw

But these are already installed (notice there's no isl16-devel, maybe
isl15-devel?). In particular,

pari-2.11.4.p0:                              no suitable system
package;
will be installed as an SPKG

giac-1.5.0.87:                               does not support check for
system package; will be installed as an SPKG

python3-3.7.3.p1:                            no suitable system
package;
will be installed as an SPKG

Shouldn't all these be detected by now?

On 8/17/20 7:55 PM, Matthias Koeppe wrote:
 >
 > Yes, https://trac.sagemath.org/ticket/29541
<https://trac.sagemath.org/ticket/29541> is worth trying and needs
review
 >

--
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 
<mailto:sage-devel+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3ee29877-7a7f-46a3-8536-a73aae44773ao%40googlegroups.com 
<https://groups.google.com/d/msgid/sage-devel/3ee29877-7a7f-46a3-8536-a73aae44773ao%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/f5098ce2-574f-2144-0401-05e37e0eb37d%40gmail.com.
>From 9a4ca026b2a145bc8dd29fe761925b9f17ba6f72 Mon Sep 17 00:00:00 2001
From: Nicolo' Piazzalunga 
Date: Tue, 18 Aug 2020 16:38:29 +0200
Subject: [PATCH] added r and edited isl

---
 build/pkgs/isl/distros/void.txt | 2 +-
 build/pkgs/r/distros/void.txt   | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 build/pkgs/r/distros/void.txt

diff --git a/build/pkgs/isl/distros/void.txt b/build/pkgs/isl/distros/void.txt
index 1fbb535066..97c6659d35 100644
--- a/build/pkgs/isl/distros/void.txt
+++ b/build/pkgs/isl/distros/void.txt
@@ -1 +1 @@
-isl16-devel
+isl15-devel
diff --git a/build/pkgs/r/distros/void.txt b/build/pkgs/r/distros/void.txt
new file mode 100644
index 00..4286f428e3
--- /dev/null
+++ b/build/pkgs/r/distros/void.txt
@@ -0,0 +1 @@
+r
--
2.28.0

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

2020-08-18 Thread Nicolo' Piazzalunga 

After importing
u/mkoeppe/spkg_configure_m4_for_giac
u/mkoeppe/more_voidlinux_txt
and d43730c (should this appear in beta9?),
I still get

the following SPKGs did not find equivalent system packages: arb brial 
cddlib cliquer coxeter3 eclib fflas_ffpack flint flintqs fplll gf2x gfan 
givaro gp2c iml isl lcalc libbraiding libgd libsemigroups lrcalc m4ri 
m4rie mpfi nauty ntl palp pari pari_elldata pari_galdata pari_galpol 
pari_nftables pari_seadata pari_seadata_small perl_cpan_polymake_prereq 
planarity python3 r rw suitesparse symmetrica sympow tachyon zn_poly


checking for the package system in use... void
configure: hint: installing the following system packages is recommended 
and may avoid building some of the above SPKGs from source:
configure:   $ sudo xbps-install flint imlib2-devel isl16-devel pari 
pari-devel python3 python3-devel rw


But these are already installed (notice there's no isl16-devel, maybe 
isl15-devel?). In particular,


pari-2.11.4.p0:  no suitable system package; 
will be installed as an SPKG


giac-1.5.0.87:   does not support check for 
system package; will be installed as an SPKG


python3-3.7.3.p1:no suitable system package; 
will be installed as an SPKG


Shouldn't all these be detected by now?

On 8/17/20 7:55 PM, Matthias Koeppe wrote:


Yes, https://trac.sagemath.org/ticket/29541 is worth trying and needs review



--
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/a616df69-a581-be28-75ce-c5c56b10dcd0%40gmail.com.

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

2020-08-17 Thread Nicolo' Piazzalunga 

On 8/17/20 1:34 PM, Nicolo' Piazzalunga wrote:


Giac is already at 1.5.0.87, so perhaps try the new spkg-configure.m4?

Indeed if I try to build /sage-9.2.beta8, it only fails with 
giac-1.5.0.63-p0


--
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/e7917149-78e2-a659-cdb2-0d510a7a0085%40gmail.com.

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

2020-08-17 Thread Nicolo' Piazzalunga 
I have added pari, which I either previously overlooked or has been 
recently added.


Void people should be taking care of renaming docker images.

Giac is already at 1.5.0.87, so perhaps try the new spkg-configure.m4?

On 7/29/20 8:06 PM, Matthias Koeppe wrote:

R builds successfully.

On Wednesday, July 29, 2020 at 9:46:48 AM UTC-7, Nicolo' wrote:

On 7/24/20 7:53 PM, Matthias Koeppe wrote:
 > On Wednesday, July 22, 2020 at 10:21:31 AM UTC-7, Matthias Koeppe
wrote:
 >
 >     I'll run another round of tests with "tox -e
 >     docker-voidlinux-standard" now.
 >
 >
 > It reproduces the build failure of giac-1.5.0.63-p0 that you
reported.
 >
 > Note that although you added the giac system package information,
the
 > system package is not used yet because there is no spkg-configure.m4
 > script for giac.
 >
 > Several ways forward:
 >
 > - https://trac.sagemath.org/ticket/29541
<https://trac.sagemath.org/ticket/29541> spkg-configure.m4 for giac
 >
 > - https://trac.sagemath.org/ticket/29552
<https://trac.sagemath.org/ticket/29552> Upgrade giac to 1.5.0-87
(or 1.6.x)

Thanks.
Let me look into giac.
Still no errors with R? Does it mean it is built, or it fails before it
tries to build it?



--
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/cb8f9305-9fa5-18b4-12f6-7ab80e61e98e%40gmail.com.
>From 27fa52ae37a8b5168ed18a4566147adc2e5ce6a5 Mon Sep 17 00:00:00 2001
From: Nicolo' Piazzalunga 
Date: Mon, 17 Aug 2020 13:23:29 +0200
Subject: [PATCH] added pari

---
 build/pkgs/pari/distros/void.txt | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 build/pkgs/pari/distros/void.txt

diff --git a/build/pkgs/pari/distros/void.txt b/build/pkgs/pari/distros/void.txt
new file mode 100644
index 00..7c8f04b36a
--- /dev/null
+++ b/build/pkgs/pari/distros/void.txt
@@ -0,0 +1,2 @@
+pari
+pari-devel
--
2.28.0

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

2020-07-29 Thread Nicolo' Piazzalunga 

On 7/24/20 7:53 PM, Matthias Koeppe wrote:

On Wednesday, July 22, 2020 at 10:21:31 AM UTC-7, Matthias Koeppe wrote:

I'll run another round of tests with "tox -e
docker-voidlinux-standard" now.


It reproduces the build failure of giac-1.5.0.63-p0 that you reported.

Note that although you added the giac system package information, the 
system package is not used yet because there is no spkg-configure.m4 
script for giac.


Several ways forward:

- https://trac.sagemath.org/ticket/29541 spkg-configure.m4 for giac

- https://trac.sagemath.org/ticket/29552 Upgrade giac to 1.5.0-87 (or 1.6.x) 


Thanks.
Let me look into giac.
Still no errors with R? Does it mean it is built, or it fails before it 
tries to build it?


--
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/00171e64-24f4-9496-aa4d-15fcff976473%40gmail.com.

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

2020-07-24 Thread Nicolo' Piazzalunga 
By the way, I noticed that there is no "latest" tag on the Docker image. 
Perhaps the voidlinux people could add this.


Note that Void Linux is a rolling release.

--
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/644db04f-41fa-11b8-3a6f-4c3d1996587c%40gmail.com.

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

2020-07-22 Thread Nicolo' Piazzalunga 

Sorry, that was likely a typo from me.
Does it work now? is the format ok?

From bfd28b43c42cf2f24427f9ac0fa0c4bcd8dc475e Mon Sep 17 00:00:00 2001
From: nicolo 
Date: Wed, 22 Jul 2020 15:46:41 +0200
Subject: [PATCH] remove glib2 (typo?)

---
 build/pkgs/freetype/distros/void.txt | 1 -
 1 file changed, 1 deletion(-)

diff --git a/build/pkgs/freetype/distros/void.txt 
b/build/pkgs/freetype/distros/void.txt

index d9f02e6c56..8ca004ddd3 100644
--- a/build/pkgs/freetype/distros/void.txt
+++ b/build/pkgs/freetype/distros/void.txt
@@ -1,4 +1,3 @@
 freetype
 harfbuzz
 glib
-glib2
--
2.27.0


On 7/12/20 9:01 PM, Matthias Koeppe wrote:

I am getting the following error:


Aborting!

Package `which' already installed.

Unable to locate 'glib2' in repository pool.

The command '/bin/sh -c xbps-install -Su && xbps-install --yes binutils 
make m4 perl python3 tar bc gcc which gettext autoconf automake libtool 
pkg-config gettext-devel bzip2-devel curl libcurl-devel ecm-devel flint 
freetype harfbuzz glib glib2 glpk-devel gmpxx-devel gsl-devel 
imlib2-devel mpc libmpc-devel mpfr ncurses-devel openblas-devel 
pcre-devel pcre2-devel ppl-devel python3 python3-devel readline-devel rw 
sqlite-devel yasm zeromq-devel' returned a non-zero code: 2





On Sunday, July 12, 2020 at 11:34:31 AM UTC-7, Matthias Koeppe wrote:

Thank you. I have added it to the branch.

By the way, I noticed that there is no "latest" tag on the Docker
image. Perhaps the voidlinux people could add this.

Also, for sending patches here in the group, it's best to use "git
commit" followed by "git format-patch".

On Saturday, July 11, 2020 at 6:14:00 AM UTC-7, Nicolo' wrote:

With this, we should get close to the list of explicitly installed
packages on my machine (attached).



--
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/acf80dbd-5506-9d6f-897e-e11eb6411011%40gmail.com.

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

2020-07-11 Thread Nicolo' Piazzalunga 
With this, we should get close to the list of explicitly installed 
packages on my machine (attached).


On 7/10/20 6:18 PM, Matthias Koeppe wrote:


Thanks. More packages, please



--
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/9519662f-5566-053b-47f0-5b6bf8d4c415%40gmail.com.
diff --git a/build/pkgs/boost/distros/void.txt b/build/pkgs/boost/distros/void.txt
new file mode 100644
index 00..fee2552239
--- /dev/null
+++ b/build/pkgs/boost/distros/void.txt
@@ -0,0 +1 @@
+boost-devel
diff --git a/build/pkgs/bzip2/distros/void.txt b/build/pkgs/bzip2/distros/void.txt
new file mode 100644
index 00..36a1011282
--- /dev/null
+++ b/build/pkgs/bzip2/distros/void.txt
@@ -0,0 +1 @@
+bzip2-devel
diff --git a/build/pkgs/curl/distros/void.txt b/build/pkgs/curl/distros/void.txt
new file mode 100644
index 00..d77ea7c303
--- /dev/null
+++ b/build/pkgs/curl/distros/void.txt
@@ -0,0 +1,2 @@
+curl
+libcurl-devel
diff --git a/build/pkgs/ecm/distros/void.txt b/build/pkgs/ecm/distros/void.txt
new file mode 100644
index 00..fe0995ee0d
--- /dev/null
+++ b/build/pkgs/ecm/distros/void.txt
@@ -0,0 +1 @@
+ecm-devel
diff --git a/build/pkgs/flint/distros/void.txt b/build/pkgs/flint/distros/void.txt
new file mode 100644
index 00..61c2ffe155
--- /dev/null
+++ b/build/pkgs/flint/distros/void.txt
@@ -0,0 +1 @@
+flint
diff --git a/build/pkgs/freetype/distros/void.txt b/build/pkgs/freetype/distros/void.txt
new file mode 100644
index 00..d9f02e6c56
--- /dev/null
+++ b/build/pkgs/freetype/distros/void.txt
@@ -0,0 +1,4 @@
+freetype
+harfbuzz
+glib
+glib2
diff --git a/build/pkgs/glpk/distros/void.txt b/build/pkgs/glpk/distros/void.txt
new file mode 100644
index 00..c689c21fd8
--- /dev/null
+++ b/build/pkgs/glpk/distros/void.txt
@@ -0,0 +1 @@
+glpk-devel
diff --git a/build/pkgs/gmp/distros/void.txt b/build/pkgs/gmp/distros/void.txt
new file mode 100644
index 00..e6ec1a0e22
--- /dev/null
+++ b/build/pkgs/gmp/distros/void.txt
@@ -0,0 +1 @@
+gmpxx-devel
diff --git a/build/pkgs/gsl/distros/void.txt b/build/pkgs/gsl/distros/void.txt
new file mode 100644
index 00..c67d1bde0d
--- /dev/null
+++ b/build/pkgs/gsl/distros/void.txt
@@ -0,0 +1 @@
+gsl-devel
diff --git a/build/pkgs/iml/distros/void.txt b/build/pkgs/iml/distros/void.txt
new file mode 100644
index 00..e1a62af891
--- /dev/null
+++ b/build/pkgs/iml/distros/void.txt
@@ -0,0 +1 @@
+imlib2-devel
diff --git a/build/pkgs/isl/distros/void.txt b/build/pkgs/isl/distros/void.txt
new file mode 100644
index 00..1fbb535066
--- /dev/null
+++ b/build/pkgs/isl/distros/void.txt
@@ -0,0 +1 @@
+isl16-devel
diff --git a/build/pkgs/mpc/distros/void.txt b/build/pkgs/mpc/distros/void.txt
new file mode 100644
index 00..ec2f198bdd
--- /dev/null
+++ b/build/pkgs/mpc/distros/void.txt
@@ -0,0 +1,2 @@
+mpc
+libmpc-devel
diff --git a/build/pkgs/mpfr/distros/void.txt b/build/pkgs/mpfr/distros/void.txt
new file mode 100644
index 00..5bcf2cdfb1
--- /dev/null
+++ b/build/pkgs/mpfr/distros/void.txt
@@ -0,0 +1 @@
+mpfr
diff --git a/build/pkgs/ncurses/distros/void.txt b/build/pkgs/ncurses/distros/void.txt
new file mode 100644
index 00..db3c1f88c1
--- /dev/null
+++ b/build/pkgs/ncurses/distros/void.txt
@@ -0,0 +1 @@
+ncurses-devel
diff --git a/build/pkgs/openblas/distros/void.txt b/build/pkgs/openblas/distros/void.txt
new file mode 100644
index 00..52e4a9f78f
--- /dev/null
+++ b/build/pkgs/openblas/distros/void.txt
@@ -0,0 +1 @@
+openblas-devel
diff --git a/build/pkgs/pcre/distros/void.txt b/build/pkgs/pcre/distros/void.txt
new file mode 100644
index 00..cfc6bffc3e
--- /dev/null
+++ b/build/pkgs/pcre/distros/void.txt
@@ -0,0 +1,2 @@
+pcre-devel
+pcre2-devel
diff --git a/build/pkgs/ppl/distros/void.txt b/build/pkgs/ppl/distros/void.txt
new file mode 100644
index 00..1c5454db76
--- /dev/null
+++ b/build/pkgs/ppl/distros/void.txt
@@ -0,0 +1 @@
+ppl-devel
diff --git a/build/pkgs/python3/distros/void.txt b/build/pkgs/python3/distros/void.txt
new file mode 100644
index 00..0a1b2134e3
--- /dev/null
+++ b/build/pkgs/python3/distros/void.txt
@@ -0,0 +1,2 @@
+python3
+python3-devel
diff --git a/build/pkgs/readline/distros/void.txt b/build/pkgs/readline/distros/void.txt
new file mode 100644
index 00..59df34dd4f
--- /dev/null
+++ b/build/pkgs/readline/distros/void.txt
@@ -0,0 +1 @@
+readline-devel
diff --git a/build/pkgs/rw/distros/void.txt b/build/pkgs/rw/distros/void.txt
new file mode 100644
index 00..16feab0960
--- /dev/null
+++ b/build/pkgs/rw/distros/void.txt
@@ -0,0 +1 @@
+rw
diff --git a/build/pkgs/sqlite/distros/void.txt b/build/pkgs/sqlite/distros/void.txt
new file mode 100644
index 00..6ec2f7b0ba
--- /dev/null
+++

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

2020-07-10 Thread Nicolo' Piazzalunga 

Let us include giac-devel (1.5.0.87):

diff --git a/build/pkgs/giac/distros/void.txt 
b/build/pkgs/giac/distros/void.txt

new file mode 100644
index 00..daf8fd8679
--- /dev/null
+++ b/build/pkgs/giac/distros/void.txt
@@ -0,0 +1,2 @@
+giac-devel
+libgiac

It seems ecl (16.1.3) needs to be patched, as in
https://github.com/void-linux/void-packages/tree/master/srcpkgs/ecl
Shall we test with version 20 or try to work with 16?


On 7/8/20 6:21 PM, Matthias Koeppe wrote:

Also the "giac" build error is confirmed.

On the other hand "r" and "suitesparse" build successfully.

To reproduce the build errors that you reported, information about 
equivalent distribution packages needs to be added to 
build/pkgs/*/distros/void.txt



On Wednesday, July 8, 2020 at 8:10:37 AM UTC-7, Matthias Koeppe wrote:

I can already confirm a build error in the ecl package.
You may want to try with ticket
https://trac.sagemath.org/ticket/22191
 , which makes a major
update to ECL.

On Wednesday, July 8, 2020 at 6:56:02 AM UTC-7, Matthias Koeppe wrote:

Thanks. I have added gettext-devel to
build/pkgs/void-bootstrap.txt on the ticket.
"tox -e docker-voidlinux-standard" is now beginning to build
Sage. I'll let you know if it reproduces the errors that you
reported.


On Wednesday, July 8, 2020 at 5:39:28 AM UTC-7, Nicolo' wrote:

Does adding
libltdl-develpython3-pkgconfig  gettext-devel
help?

On 7/7/20 9:18 PM, Matthias Koeppe wrote:
 > Thanks. I have put your changes on the branch of
 > https://trac.sagemath.org/ticket/30044
 and did some
additional changes.
 >
 > You can now test using:
 >
 > tox -e docker-voidlinux-standard
 >
 >
 > Currently, it fails as follows:
 >
 > src/doc/bootstrap:85: installing
src/doc/en/reference/repl/options.txt
 > gettext and the gettextize program must be installed and
be in
 > your PATH. E.g. Homebrew installs them in
/usr/local/opt/gettext/bin.
 > Bootstrap failed. Either upgrade autotools or run
bootstrap with
 > the -d option to download the auto-generated files instead.
 >
 > This means that some package are missing.

--
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/43be6f39-f9cc-4738-887a-00c2bea3a988o%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/ab215f6e-7552-0184-4e65-14ec74f11ddf%40gmail.com.

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

2020-07-08 Thread Nicolo' Piazzalunga 

Does adding
libltdl-devel   python3-pkgconfig  gettext-devel
help?

On 7/7/20 9:18 PM, Matthias Koeppe wrote:
Thanks. I have put your changes on the branch of 
https://trac.sagemath.org/ticket/30044 and did some additional changes.


You can now test using:

tox -e docker-voidlinux-standard


Currently, it fails as follows:

src/doc/bootstrap:85: installing src/doc/en/reference/repl/options.txt
gettext and the gettextize program must be installed and be in
your PATH. E.g. Homebrew installs them in /usr/local/opt/gettext/bin.
Bootstrap failed. Either upgrade autotools or run bootstrap with
the -d option to download the auto-generated files instead.

This means that some package are missing.


--
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/ef94f493-8541-83d5-509e-cef105465759%40gmail.com.

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

2020-07-07 Thread Nicolo' Piazzalunga 

I tried to edit relevant files, see diff.log attached.
Please check docker-specific files, as I'm not familiar with it.
(The relevant image in docker-hub is /voidlinux/masterdir-x86_64-musl)
I have not yet dealt with equivalent distribution packages, if it's ok I 
will do it once we have no build errors.)

Notice that it uses musl libc and libressl (instead of openssl).
I attach the list of packages installed on the machine I'm building on.

On 7/3/20 6:36 PM, Matthias Koeppe wrote:
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




--
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/2056160d-a1fa-e947-4d85-3f335c13001a%40gmail.com.
diff --git a/build/bin/sage-guess-package-system b/build/bin/sage-guess-package-system
index e414d10c41..33dfeee2d8 100755
--- a/build/bin/sage-guess-package-system
+++ b/build/bin/sage-guess-package-system
@@ -25,6 +25,8 @@ elif zypper --version > /dev/null 2>&1; then
 echo opensuse
 elif apk --version > /dev/null 2>&1; then
 echo alpine
+elif xbps-install --version > /dev/null 2>&1; then
+echo void
 else
 case `uname -s` in
 CYGWIN*)
diff --git a/build/bin/sage-print-system-package-command b/build/bin/sage-print-system-package-command
index fa3f155749..4527cb896e 100755
--- a/build/bin/sage-print-system-package-command
+++ b/build/bin/sage-print-system-package-command
@@ -61,6 +61,10 @@ case $system:$command in
 arch*:install)
 [ -n "$system_packages" ] && echo "${PROMPT}${SUDO}pacman -S $system_packages"
 ;;
+
+void*:install)
+[ -n "$system_packages" ] && echo "${PROMPT}${SUDO}xbps-install $system_packages"
+;;
 *conda*:install)
 [ -n "$system_packages" ] && echo "${PROMPT}conda install $system_packages"
 ;;
diff --git a/build/bin/write-dockerfile.sh b/build/bin/write-dockerfile.sh
index e82d1ea8a5..f0f23225e0 100755
--- a/build/bin/write-dockerfile.sh
+++ b/build/bin/write-dockerfile.sh
@@ -77,6 +77,16 @@ EOF
 EXISTS="pacman -Si"
 INSTALL="pacman -Su --noconfirm"
 ;;
+void*)
+	# https://hub.docker.com/r/voidlinux/masterdir-x86_64-musl
+	cat

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/22191>
 >    * https://trac.sagemath.org/ticket/29617
<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 
<mailto: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 
<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/26f36654-2362-59be-346c-e80fabb7bca1%40gmail.com.

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-02 Thread Nicolo' Piazzalunga 

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/d26696ae-c476-ba52-6929-2f6f192487c1%40gmail.com.

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

2020-07-01 Thread Nicolo' Piazzalunga 

Thanks.
I'm puzzled by 'does not support check for system package'/'no suitable 
system package' in config.log
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?


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

On 2020-07-01 08:36, Dima Pasechnik wrote:


In building giac, you get even more strange error, a missing gammaf function.
(something to do with musl?)


Giac upstream probably needs to

   #define _GNU_SOURCE

to get the gammaf() function with musl, since it's not standardized.



--
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/6eb2b70d-6946-8d8c-6c66-219fd75634db%40gmail.com.