[sage-release] Re: Trouble with gfan

[Simon King]

Hi Dima

On 2021-09-02, Dima Pasechnik  wrote:
> you can install g++7 package on Ubuntu 16.04. (google for instructions).
>
> This should do the trick (after distclean).

I will not work with my old laptop much longer and I suppose that on the
new laptop (with a more recent Ubuntu) the problem will not occur.

Anyway, I wanted to try if/how it is possible to solve the problem on
the old laptop. For the record: "make distclean", 
"./configure --with-system-gcc=no" and "make build" worked. I don't
know if "make distclean" directly followed by "make build" would have
worked, too.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgrelc%24sda%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Jonathan,

On 2021-09-02, 'Jonathan Kliem' via sage-release 
 wrote:
> Dear Simon,
>
> ./configure --help | grep gcc
>
> reveals that you should configure sage with
>
> --with-system-gcc=no
>
> I hope that works for you.

Thank you. In fact I had the idea to do "./configure --help" and look
out for "gcc" a few hours ago, and now it is trying to build.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgqqbv%2418f%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

On 2021-09-01, Matthias Köppe  wrote:
> OK, Simon, there is only one conclusion: Your machine is haunted and you 
> should abandon it.

Witchcraft?? OMG!!

Anyway, from your and Dima's previous suggestions it seems to me that
the trouble might have been caused by a too old version of gcc. Would it
make sense to do "make distclean" and then try again with Sage's own
gcc? If so: Could you remind me the command for forcing Sage to build
(and use) the gcc spkg?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgqj2a%241435%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

On 2021-08-31, Matthias Köppe  wrote:
> This all looks fine. Can you check if anything changes if you remove some 
> items from PATH: 
> In particular /home/king/bin and /home/king/.local/bin and perhaps /snap/bin

./sage -f gfan fails in the same way as before.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgnga9%24101n%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

On 2021-08-30, Matthias Köppe  wrote:
> 1) Could you check if you happen to have a g++ in 
> /home/king/Sage/git/sage/local/bin?  (unlikely because you mentioned 
> earlier that the environment is correct in "sage -sh")

No, /home/king/Sage/git/sage/local/bin/g++ does not exist, and "which
g++" both in a shell and in a sage shell says "/usr/bin/g++".

> 2) If you do (cd 
> '/home/king/Sage/git/sage/local/var/tmp/sage/build/gfan-0.6.2.p1' && 
> '/home/king/Sage/git/sage/sage' --buildsh), what is CXX set to? (Just post 
> the whole output from "env"?)

That's lengthy, but you asked for it...

XDG_VTNR=7
LC_PAPER=en_US.UTF-8
AS=as
SAGE_FAT_BINARY=
SAGE_GMP_PREFIX=/home/king/Sage/git/sage/local
ORIGINAL_CFLAGS=
NNTPSERVER=news.gmane.io
LDFLAGS=-Wl,-rpath-link,/home/king/Sage/git/sage/local/lib 
-L/home/king/Sage/git/sage/local/lib 
-Wl,-rpath,/home/king/Sage/git/sage/local/lib
AR=ar
XDG_SESSION_ID=c2
LC_ADDRESS=en_US.UTF-8
SAGE_LOGS=/home/king/Sage/git/sage/logs/pkgs
SAGE_NTL_PREFIX=/home/king/Sage/git/sage/local
LC_MONETARY=en_US.UTF-8
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/king
CLUTTER_IM_MODULE=xim
SESSION=ubuntu
UNAME=Linux
SAGE_CONFIGURE_FFLAS_FFPACK=
GPG_AGENT_INFO=/home/king/.gnupg/S.gpg-agent:0:1
SAGE_ENV_CONFIG_SOURCED=1
R_MAKEVARS_SITE=/home/king/Sage/git/sage/local/lib/R/share/Makevars.site
TERM=xterm-256color
XDG_MENU_PREFIX=gnome-
SHELL=/bin/bash
VTE_VERSION=4205
CONFIGURED_CFLAGS=
CONFIGURED_CXXFLAGS=
SAGE_VENV=/home/king/Sage/git/sage/local
SAGE_ENV_SOURCED=4
SAGE_GMP_INCLUDE=/home/king/Sage/git/sage/local/include
SAGE_DEBUG=
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
LIBRARY_PATH=/home/king/Sage/git/sage/local/lib
PERL5LIB=/home/king/Sage/git/sage/local/lib/perl5:
MKDIR=mkdir
OPENBLAS_NUM_THREADS=1
SAGE_DOC_MATHJAX=True
F77FLAGS_NON_NATIVE=-O2 -g
SAGE_ORIG_PATH=/home/king/bin:/home/king/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SAGE_CONFIGURE_MPC=--with-mpc=/home/king/Sage/git/sage/local
SAGE_CONFIGURE_NTL=--with-ntl=/home/king/Sage/git/sage/local
WINDOWID=85986144
LC_NUMERIC=en_US.UTF-8
PYTHON_EGG_CACHE=/home/king/.sage//.python-eggs
CYSIGNALS_CRASH_LOGS=/home/king/.sage//crash_logs
CONFIGURED_FCFLAGS=
GNOME_KEYRING_CONTROL=
UPSTART_SESSION=unix:abstract=/com/ubuntu/upstart-session/1000/3031
F77FLAGS_O3_NON_NATIVE=-O3 -g
CXXFLAGS_O3_NON_NATIVE=-O3 -g
GTK_MODULES=gail:atk-bridge:unity-gtk-module
ORIGINAL_FCFLAGS=
LC_ALL=
SAGE_REPO_AUTHENTICATED=ssh://g...@trac.sagemath.org:/sage.git
SAGE_NUM_THREADS=1
SAGE_CONFIGURE_MPFR=--with-mpfr=/home/king/Sage/git/sage/local
DOT_SAGE=/home/king/.sage/
PYTHONUSERBASE=/home/king/.sage//local
SAGE_FREETYPE_PREFIX=/home/king/Sage/git/sage/local
USER=king
LC_TELEPHONE=en_US.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
QT_ACCESSIBILITY=1
SINGULAR_EXECUTABLE=/home/king/Sage/git/sage/local/bin/Singular
CONFIGURED_F77FLAGS=
UNITY_HAS_3D_SUPPORT=true
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
SAGE_CONFIGURE_GMP=--with-gmp=/home/king/Sage/git/sage/local
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
CPATH=/home/king/Sage/git/sage/local/include
SAGE_SHPROMPT_PREFIX=sage-buildsh
DEFAULTS_PATH=/usr/share/gconf/ubuntu.default.path
SESSION_MANAGER=local/klap:@/tmp/.ICE-unix/3565,unix/klap:/tmp/.ICE-unix/3565
SAGE_LOCAL=/home/king/Sage/git/sage/local
MPLCONFIGDIR=/home/king/.sage//matplotlib-1.5.1
MAXIMA_PREFIX=/home/king/Sage/git/sage/local
CXXFLAGS=-O2 -g -march=native
SAGE_REPO_ANONYMOUS=https://gitlab.com/sagemath/dev/tracmirror.git
MAXIMA_USERDIR=/home/king/.sage//maxima

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

Right. Before, I erased the old log and did "sage -i gfan".

Now, I did "sage -f gfan", which failed again. I have posted the new log
under the old url.

Best regards,
Simon

On 2021-08-30, Matthias Köppe  wrote:
> Well, then the gfan.log that you shared cannot possibly come from the same 
> install as the config.log that you shared. Can you run "./sage -f gfan" 
> again?
>
> From your log:
> Building gfan-0.6.2.p1 
> g++ -O2 -g -march=native -DNOCDDPREFIX -DGMPRATIONAL -Wuninitialized 
> -fno-omit-frame-pointer -O2 -g -c src/polynomialgcd.cpp -o 
> src/polynomialgcd.o 
>
> It should say:
> Building gfan-0.6.2.p1
> g++ -std=gnu++11 -O2 -g -march=native -DNOCDDPREFIX -DGMPRATIONAL 
> -Wuninitialized -fno-omit-frame-pointer -O2   -g -c 
> src/polynomialgcd.cpp -o src/polynomialgcd.o
>
>  
> On Monday, August 30, 2021 at 11:21:58 AM UTC-7 Simon King wrote:
>
>> Hi Matthias,
>>
>> On 2021-08-30, Matthias Köppe  wrote:
>> > ./configure correctly determines that it needs to use CXX='g++ 
>> > -std=gnu++11' to work with this old compiler.
>> > Check if you have environment variables CC or CXX set in your global 
>> > environment -- they should be unset; otherwise, they will override the 
>> > values determined by ./configure. (This is nonstandard behavior of our 
>> > build system.)
>>
>> In a shell:
>> king@klap:~/Sage/git/sage$ echo $CC
>>
>> king@klap:~/Sage/git/sage$ echo $CXX
>>
>> So, it is not set.
>> In a Sage shell:
>> (sage-sh) king@klap:sage$ echo $CC
>> gcc
>> (sage-sh) king@klap:sage$ echo $CXX
>> g++ -std=gnu++11
>>
>> This is what it should be, right?
>>
>> Best regards,
>> Simon
>> >
>> > On Sunday, August 29, 2021 at 3:04:34 PM UTC-7 Simon King wrote:
>> >
>> >> Hi Matthias,
>> >>
>> >> the two logs are at https://users.fmi.uni-jena.de/~king/logs/
>> >>
>> >> Best regards,
>> >> Simon
>> >>
>> >> On 2021-08-29, Matthias Köppe  wrote:
>> >> > Singular vendors a part of gfan called gfanlib. Perhaps an 
>> installation 
>> >> of 
>> >> > that is leaking into your build.
>> >> >
>> >> > If you can share your top-level config.log and the full gfan build 
>> log, 
>> >> we 
>> >> > can take a closer look.
>> >> >
>> >> > On Sunday, August 29, 2021 at 11:50:32 AM UTC-7 Simon King wrote:
>> >> >
>> >> >> Hi Matthias,
>> >> >>
>> >> >> On 2021-08-29, Matthias Köppe  wrote:
>> >> >> > On Sunday, August 29, 2021 at 5:44:33 AM UTC-7 Dima Pasechnik 
>> wrote:
>> >> >> >
>> >> >> >> is gfan partially taken from the system? 
>> >> >> >>
>> >> >> >> probably. Ubuntu 16.04 has gfan version 0.5, but Sage needs 
>> 0.6.2. 
>> >> >> >> A system-wide install of old gfan might get in the way.
>> >> >> >
>> >> >> > No, that alone cannot explain it -- we test this configuration. 
>> >> >> > ubuntu-xenial-standard installs the system gfan, then rejects it, 
>> >> then 
>> >> >> > correctly builds gfan.
>> >> >>
>> >> >> What could explain it? Is there a typical application that I might 
>> have
>> >> >> installed and depends on gfan? I mean, it is for Groebner fans. So, 
>> what
>> >> >> *non-mathematical* software would use it? I don't think that I 
>> installed
>> >> >> a mathematical software after the last successful build of Sage.
>> >> >>
>> >> >> Should I try to uninstall gfan, re-install it, and try again? And,
>> >> >> if that fails, uninstall and NOT re-install, but build Sage and hope
>> >> >> that it provides a working gfan?
>> >> >>
>> >> >> Best regards,
>> >> >> Simon
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgjk9g%243p8%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

On 2021-08-30, Matthias Köppe  wrote:
> ./configure correctly determines that it needs to use CXX='g++ 
> -std=gnu++11' to work with this old compiler.
> Check if you have environment variables CC or CXX set in your global 
> environment -- they should be unset; otherwise, they will override the 
> values determined by ./configure. (This is nonstandard behavior of our 
> build system.)

In a shell:
king@klap:~/Sage/git/sage$ echo $CC

king@klap:~/Sage/git/sage$ echo $CXX

So, it is not set.
In a Sage shell:
(sage-sh) king@klap:sage$ echo $CC
gcc
(sage-sh) king@klap:sage$ echo $CXX
g++ -std=gnu++11

This is what it should be, right?

Best regards,
Simon
>
> On Sunday, August 29, 2021 at 3:04:34 PM UTC-7 Simon King wrote:
>
>> Hi Matthias,
>>
>> the two logs are at https://users.fmi.uni-jena.de/~king/logs/
>>
>> Best regards,
>> Simon
>>
>> On 2021-08-29, Matthias Köppe  wrote:
>> > Singular vendors a part of gfan called gfanlib. Perhaps an installation 
>> of 
>> > that is leaking into your build.
>> >
>> > If you can share your top-level config.log and the full gfan build log, 
>> we 
>> > can take a closer look.
>> >
>> > On Sunday, August 29, 2021 at 11:50:32 AM UTC-7 Simon King wrote:
>> >
>> >> Hi Matthias,
>> >>
>> >> On 2021-08-29, Matthias Köppe  wrote:
>> >> > On Sunday, August 29, 2021 at 5:44:33 AM UTC-7 Dima Pasechnik wrote:
>> >> >
>> >> >> is gfan partially taken from the system? 
>> >> >>
>> >> >> probably. Ubuntu 16.04 has gfan version 0.5, but Sage needs 0.6.2. 
>> >> >> A system-wide install of old gfan might get in the way.
>> >> >
>> >> > No, that alone cannot explain it -- we test this configuration. 
>> >> > ubuntu-xenial-standard installs the system gfan, then rejects it, 
>> then 
>> >> > correctly builds gfan.
>> >>
>> >> What could explain it? Is there a typical application that I might have
>> >> installed and depends on gfan? I mean, it is for Groebner fans. So, what
>> >> *non-mathematical* software would use it? I don't think that I installed
>> >> a mathematical software after the last successful build of Sage.
>> >>
>> >> Should I try to uninstall gfan, re-install it, and try again? And,
>> >> if that fails, uninstall and NOT re-install, but build Sage and hope
>> >> that it provides a working gfan?
>> >>
>> >> Best regards,
>> >> Simon
>> >>
>> >>
>> >
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgj7jp%247b6%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

the two logs are at https://users.fmi.uni-jena.de/~king/logs/

Best regards,
Simon

On 2021-08-29, Matthias Köppe  wrote:
> Singular vendors a part of gfan called gfanlib. Perhaps an installation of 
> that is leaking into your build.
>
> If you can share your top-level config.log and the full gfan build log, we 
> can take a closer look.
>
> On Sunday, August 29, 2021 at 11:50:32 AM UTC-7 Simon King wrote:
>
>> Hi Matthias,
>>
>> On 2021-08-29, Matthias Köppe  wrote:
>> > On Sunday, August 29, 2021 at 5:44:33 AM UTC-7 Dima Pasechnik wrote:
>> >
>> >> is gfan partially taken from the system? 
>> >>
>> >> probably. Ubuntu 16.04 has gfan version 0.5, but Sage needs 0.6.2. 
>> >> A system-wide install of old gfan might get in the way.
>> >
>> > No, that alone cannot explain it -- we test this configuration. 
>> > ubuntu-xenial-standard installs the system gfan, then rejects it, then 
>> > correctly builds gfan.
>>
>> What could explain it? Is there a typical application that I might have
>> installed and depends on gfan? I mean, it is for Groebner fans. So, what
>> *non-mathematical* software would use it? I don't think that I installed
>> a mathematical software after the last successful build of Sage.
>>
>> Should I try to uninstall gfan, re-install it, and try again? And,
>> if that fails, uninstall and NOT re-install, but build Sage and hope
>> that it provides a working gfan?
>>
>> Best regards,
>> Simon
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgh096%24bsr%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Dima,

On 2021-08-29, Dima Pasechnik  wrote:
> The error you get is most likely due to an old g++, which chokes on a
> newer C++ construction,
> not due to a version mixup.
>
> What is the g++ version  you are using?
> (or perhaps you use clang?)
>

$ g++ --version
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Is that new enough?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sggvg3%24gcl%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Dima

On 2021-08-29, Dima Pasechnik  wrote:
> I'd start by un-installing system-wide gfan (could it be that you have more 
> system-wide copies of it, e.g. in /usr/local/ ?)
> and try  building then.

I tried to "find /usr/local/ -name *gfan*", which resulted in nothing.

Then I tried "sudo apt remove gfan", which told me that gfan is not
installed! So, I misinterpreted "apt show gfan" (it gave me the
apparently wrong impression that I had it installed.

So, what next? How can I find out whether (and where) gfan is installed
system-wide? And if it is not installed: Shall I try to install gfan 
system-wide,
and try building Sage again?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sggmnp%24kfl%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthias,

On 2021-08-29, Matthias Köppe  wrote:
> On Sunday, August 29, 2021 at 5:44:33 AM UTC-7 Dima Pasechnik wrote:
>
>> is gfan partially taken from the system? 
>>
>> probably. Ubuntu 16.04 has gfan version 0.5, but Sage needs 0.6.2. 
>> A system-wide install of old gfan might get in the way.
>
> No, that alone cannot explain it -- we test this configuration. 
> ubuntu-xenial-standard installs the system gfan, then rejects it, then 
> correctly builds gfan.

What could explain it? Is there a typical application that I might have
installed and depends on gfan? I mean, it is for Groebner fans. So, what
*non-mathematical* software would use it? I don't think that I installed
a mathematical software after the last successful build of Sage.

Should I try to uninstall gfan, re-install it, and try again? And,
if that fails, uninstall and NOT re-install, but build Sage and hope
that it provides a working gfan?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sggktg%24vdn%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Dima,

On 2021-08-29, Dima Pasechnik  wrote:
> On Sun, Aug 29, 2021 at 1:32 PM Simon King  wrote:
>> In particular, the error message I'm getting looks to me like there is 
>> something
>> wrong in the sources (namely: A different number of arguments in the header
>> and in the code) -- is gfan partially taken from the system?
>
> probably. Ubuntu 16.04 has gfan version 0.5, but Sage needs 0.6.2.
> A system-wide install of old gfan might get in the way.

I see. So, I should better focus on installing Sage on my new laptop,
that has a more recent ubuntu.

Thanks and best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgg1k6%24qus%241%40ciao.gmane.io.

[sage-release] Re: Trouble with gfan

[Simon King]

Hi Matthia,

On 2021-08-28, Matthias Köppe  wrote:
> We actually test this platform (ubuntu xenial), and gfan builds correctly. 
> See https://github.com/sagemath/sage/runs/3392764418?check_suite_focus=true
>
> This failure must be caused by something specific to your system - such as 
> some stuff installed into /usr/local or something like that.

What could be the cause? I'm not sure whether I added any stuff since the
last successful build. 

In particular, the error message I'm getting looks to me like there is something
wrong in the sources (namely: A different number of arguments in the header
and in the code) -- is gfan partially taken from the system?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sgfuot%24159%241%40ciao.gmane.io.

[sage-release] Trouble with gfan

[Simon King]

Hi!

I'm afraid it's a long time since I last tried to build SageMath. When I
now checked out the latest develop branch, gfran failed to build.

>From the log:
[gfan-0.6.2.p1]  IntegerVectorList setTemp;for(auto 
c=observedExponents.begin();c!=observedExponents.end();c++)setTemp.push_back(*c);
[gfan-0.6.2.p1] 
  ^
[gfan-0.6.2.p1] In file included from src/field_rationals.h:8:0,
[gfan-0.6.2.p1]  from src/polynomialgcd.cpp:14:
[gfan-0.6.2.p1] src/field.h:81:23: note: candidate: FieldElement 
operator*(const FieldElement&, const FieldElement&)
[gfan-0.6.2.p1]friend FieldElement operator*(const FieldElement ,const 
FieldElement );
[gfan-0.6.2.p1]^
[gfan-0.6.2.p1] src/field.h:81:23: note:   candidate expects 2 arguments, 1 
provided

This is on an older ubuntu (16.04.7), in case that matters.

Is that a known issue? How can I downgrade to a working version of gfan?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/sge09g%24pjf%241%40ciao.gmane.io.

[sage-release] Re: Sage 9.1.beta9 released

[Simon King]

Hi all,

On 2020-03-31, Matthias Köppe  wrote:
>> > I don't know, but I found these instructions: 
>> > https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa 
>> > that also mention what packages should be installed 
>>
>> Excellent! After installing them and doing ./configure, I see this line: 
>>  python3-3.7.3.p1:using system package; SPKG 
>> will not be installed 
>>
>>
> Great, this looks like progress. And thanks for telling me about the 
> deadsnakes ppa, this may be useful at some point.
>  
>
>> So, now I can try whether it works
>>
>>
> If it doesn't, please post the logs, as usual.

It *almost* worked. On Ubuntu 16.04 with Python 3.7.7 installed from a
ppa, I get
sage -t --warn-long 44.6 src/sage/rings/padics/padic_lattice_element.py  # 3 
doctests failed
sage -t --warn-long 44.6 src/sage/interfaces/psage.py  # 1 doctest failed

with SageMath version 9.1.beta9, Release Date: 2020-03-29.

I posted config.log, dochtml.doc, install.log, start.log and test.log
here: https://users.fmi.uni-jena.de/~king/logs/

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/r5vaih%24tn5%241%40ciao.gmane.io.

[sage-release] Re: Sage 9.1.beta9 released

[Simon King]

Dear Matthias,

On 2020-03-31, Matthias Köppe  wrote:
> On Monday, March 30, 2020 at 8:30:34 PM UTC-4, Simon King wrote:
>>
>> > Are you sure your /usr/bin/python comes from that distribution? As far 
>> as I 
>> > can see, xenial only has 3.5.1-3. 
>>
>> I installed python3 after "sudo add-apt-repository ppa:deadsnakes/ppa". 
>> Has that been a mistake? 
>>
>>
> I don't know, but I found these instructions: 
> https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa
> that also mention what packages should be installed

Excellent! After installing them and doing ./configure, I see this line:
 python3-3.7.3.p1:using system package; SPKG will 
not be installed

So, now I can try whether it works (and of course if it doesn't I can
still try sudo apt-get remove python3.7 and change the symlinks
/usr/bin/python and /usr/bin/python3 to my distribution's standard
python3.5).

Thank you for your help!
Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/r5u4kk%243hqb%241%40ciao.gmane.io.

[sage-release] Re: Sage 9.1.beta9 released

[Simon King]

On 2020-03-30, Matthias Köppe  wrote:
> Hi Simon,
>
> On Monday, March 30, 2020 at 6:45:17 PM UTC-4, Simon King wrote:
>> Concerning too old: 
>> $ uname -a 
>> Linux klap 4.15.0-91-generic #92~16.04.1-Ubuntu SMP Fri Feb 28 14:57:22 
>> UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 
>> $ cat /etc/issue 
>> Ubuntu 16.04.6 LTS \n \l 
>>
>> I posted config.log here: https://users.fmi.uni-jena.de/~king/config.log 
>>
>>
> Are you sure your /usr/bin/python comes from that distribution? As far as I 
> can see, xenial only has 3.5.1-3.

I installed python3 after "sudo add-apt-repository ppa:deadsnakes/ppa".
Has that been a mistake? How to undo it?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/r5u2v4%243erc%241%40ciao.gmane.io.

[sage-release] Re: Sage 9.1.beta9 released

[Simon King]

Hi Matthias,

On 2020-03-30, Matthias Köppe  wrote:
> This is outdated. We now generate an up-to-date version of this manual 
> section at boostrapping time. Use "cat src/doc/en/installation/debian*.txt" 
> to print it.
>
> Or re-run configure and take a look at the system package installation 
> hints that it prints at the very end.
>
> (but note that libflint-arb-dev isn't available for me in ubuntu, no 
>> idea why), 
>
>
> Likely your ubuntu is too old.

Thanks. Trying what src/doc/en/installation/debian*.txt tells me:
Note, selecting 'zlib1g-dev' instead of 'libz-dev'
E: Unable to locate package libflint-arb-dev
E: Unable to locate package libplanarity-dev
E: Unable to locate package python3-distutils

Concerning too old:
$ uname -a
Linux klap 4.15.0-91-generic #92~16.04.1-Ubuntu SMP Fri Feb 28 14:57:22 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 16.04.6 LTS \n \l

I posted config.log here: https://users.fmi.uni-jena.de/~king/config.log

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/r5tspm%242q78%241%40ciao.gmane.io.

[sage-release] Re: Sage 9.1.beta9 released

[Simon King]

Hi!

On 2020-03-30, Dima Pasechnik  wrote:
> On Tue, 31 Mar 2020, 03:03 Vincent Delecroix, <20100.delecr...@gmail.com>
> wrote:
>> Le 29/03/2020 à 21:50, Matthias Köppe a écrit :
>> >
>> > Let me remark that this is the first beta that tries to use the system
>> > python3 in a venv (#27824) instead of building our own copy of python3.
>> > Tests of building from scratch or (after "make python3-clean") would be
>> > valuable.
>>
>> Very disappointing

Let me add further disappointments:

After making sure that python3.7.7 is installed on my laptop and after
installing the recommended system packages mentioned in
http://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation
(but note that libflint-arb-dev isn't available for me in ubuntu, no
idea why), I get this in my config.log:

## Checking whether SageMath should install SPKG python3... ##
##  ##
configure:25026: checking whether any of sqlite libpng bzip2 xz libffi is 
installed or will be installed as SPKG
configure:25030: result: yes; install python3 as well
configure:25273: no suitable system package found for SPKG python3

Concerning sqlite, I see this:
## Checking whether SageMath should install SPKG sqlite... ##
## --- ##
configure:24630: checking libsqlite3 >= sqlite3_min_version
configure:24664: g++ -std=gnu++11 -o conftest -g -O2conftest.cpp -lm4rie 
-lgf2x -lreadline -L/usr/lib/x86_64-linux-gnu -lcurl -lbz2 -lgmp -lm  -lntl 
-lsqlite3 >&5
conftest.cpp:69:62: fatal error: sqlite3.h: No such file or directory

So, apparently libsqlite3-dev needs to be installed (it isn't mentioned in the
list of recommended packages), the other stuff (libpng, bzip2, xz,
libffi apparently is installed on my system).

After installing libsqlite3-dev, I get another problem:
##  ##
## Checking whether SageMath should install SPKG python3... ##
##  ##
configure:25026: checking whether any of sqlite libpng bzip2 xz libffi is 
installed or will be installed as SPKG
configure:25035: result: no
configure:25045: checking for python3 >= 3.7.3, < 3.8 with modules sqlite3, 
ctypes, math, hashlib, crypt, readline, socket, zlib, distutils.core
configure:25051: result: 
configure:25066: checking ... whether /usr/bin/python3.7 is good
configure:25200: result: no, the version is in the supported range, and the 
modules can be imported, but distutils cannot build an extension
configure:25066: checking ... whether /usr/bin/python3 is good
configure:25200: result: no, the version is in the supported range, and the 
modules can be imported, but distutils cannot build an extension
configure:25247: result: 
configure:25273: no suitable system package found for SPKG python3

Since it mentions "extensions", I was trying to install cython3. But
this didn't help, distutils still cannot build an extension. So, I tried
to install python3-distutils (but this is not available in ubuntu) and
eventually python3-distutils-extra.

Result:
Still doesn't work.

So, it seems to be that the following updates to the Sage installation
guide should be done:

- Something should be done about libflint-arb-dev
- libsqlite3-dev should be added
- It should be explained what to do concerning the system python3's
  distutils' inability to build extensions.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/r5trb1%243kub%241%40ciao.gmane.io.

Re: [sage-release] Sage 9.0.rc0 released

[Simon King]

On Saturday, December 28, 2019 at 8:41:16 PM UTC+1, Samuel Lelievre wrote:
>
> Le sam. 28 déc. 2019 à 02:12, Samuel Lelièvre: 
> > 
> > Computer, OS, build choices: 
> > 
> > - iMac, Mid 2015 
> > - macOS 10.14.6 Mojave 
> > - build for Python 2 
> > - build Sage's `gcc` and `openssl` packages 
> > - build Sage's Python with its `_ssl` and `_tkinter` modules 
> > 
> > Running `make testlong` gave 2 failing doctests 
> > in the file `src/sage/misc/sageinspect.py`. 
> > 
> > Running the tests for that file again gave 6 failing doctests. 
>
> The key parts seem to be these: 
>
> > ModuleNotFoundError: No module named 
> > '_Users_lelievre__sage_temp_Ghost_80496_tmp_2caqjln__pyx_0' 
>  

No, I rather believe the key part is this:
(build/cythonized/sage/misc/lazy_import.c:3686) 
return self.get_object()(*args, **kwds) 
  File 
"/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
 


You say that you are using Sage with python-2, but according to the path it 
is python-3. Perhaps you upgraded from python-2 to python-3 without make 
distclean? Probably the discussion should be moved to the ticket, #28928

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/13d1e622-ecdd-493f-a607-95ecb249a692%40googlegroups.com.

Re: [sage-release] Sage 9.0.rc0 released

[Simon King]

Hi Samuel,

did you open a ticket for the problem in sageinspect?

Best regards,
Simon

On Saturday, December 28, 2019 at 8:12:31 AM UTC+1, Samuel Lelievre wrote:
>
> Thu 2019-12-26 à 23:24 UTC, Volker Braun: 
> > 
> > 746a826377 (trac/develop, tag: 9.0.rc0) Updated SageMath version to 
> 9.0.rc0 
>
>
> Computer, OS, build choices: 
>
> - iMac, Mid 2015 
> - macOS 10.14.6 Mojave 
> - build for Python 2 
> - build Sage's `gcc` and `openssl` packages 
> - build Sage's Python with its `_ssl` and `_tkinter` modules 
>
> Running `make testlong` gave 2 failing doctests 
> in the file `src/sage/misc/sageinspect.py`. 
>
> Running the tests for that file again gave 6 failing doctests. 
>
> Excerpts from the terminal session follow. 
>
>
> ```bash 
> $ make testlong 
>
> [...] 
>
> -- 
> sage -t --long --warn-long 50.2 src/sage/misc/sageinspect.py  # 2 
> doctests failed 
> -- 
> Total time for all tests: 11201.1 seconds 
> cpu time: 8574.9 seconds 
> cumulative wall time: 10884.3 seconds 
> make: *** [testlong] Error 1 
> ``` 
>
>
> ```bash 
> $ ./sage -t --long --warn-long 50.2 src/sage/misc/sageinspect.py 
> Running doctests with ID 2019-12-27-15-55-47-4a6bf556. 
> Git branch: develop 
> Using --optional=build,dochtml,mpir,python2,sage 
> Doctesting 1 file. 
> sage -t --long --warn-long 50.2 src/sage/misc/sageinspect.py 
> ** 
> File "src/sage/misc/sageinspect.py", line 2132, in 
> sage.misc.sageinspect._sage_getsourcelines_name_with_dot 
> Failed example: 
> cython(''' 
> class A: 
> def __init__(self): 
> "some init doc" 
> pass 
> class B: 
> "some class doc" 
> class A(A): 
> pass 
> ''') 
> Exception raised: 
> Traceback (most recent call last): 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  
>
> line 681, in _run 
> self.compile_and_execute(example, compiler, test.globs) 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  
>
> line 1123, in compile_and_execute 
> exec(compiled, globs) 
>   File " sage.misc.sageinspect._sage_getsourcelines_name_with_dot[3]>", line 
> 10, in  
> ''') 
>   File "sage/misc/lazy_import.pyx", line 353, in 
> sage.misc.lazy_import.LazyImport.__call__ 
> (build/cythonized/sage/misc/lazy_import.c:3686) 
> return self.get_object()(*args, **kwds) 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
>  
>
> line 634, in cython_compile 
> return cython_import_all(tmpfile, get_globals(), **kwds) 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
>  
>
> line 524, in cython_import_all 
> m = cython_import(filename, **kwds) 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
>  
>
> line 504, in cython_import 
> return builtins.__import__(name) 
> ModuleNotFoundError: No module named 
> '_Users_lelievre__sage_temp_Ghost_80496_tmp_2caqjln__pyx_0' 
> ** 
> File "src/sage/misc/sageinspect.py", line 2142, in 
> sage.misc.sageinspect._sage_getsourcelines_name_with_dot 
> Failed example: 
> B.A.__name__ 
> Exception raised: 
> Traceback (most recent call last): 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  
>
> line 681, in _run 
> self.compile_and_execute(example, compiler, test.globs) 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  
>
> line 1123, in compile_and_execute 
> exec(compiled, globs) 
>   File " sage.misc.sageinspect._sage_getsourcelines_name_with_dot[4]>", line 1, 
> in  
> B.A.__name__ 
> NameError: name 'B' is not defined 
> ** 
> File "src/sage/misc/sageinspect.py", line 2144, in 
> sage.misc.sageinspect._sage_getsourcelines_name_with_dot 
> Failed example: 
> B.A.__qualname__ 
> Exception raised: 
> Traceback (most recent call last): 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  
>
> line 681, in _run 
> self.compile_and_execute(example, compiler, test.globs) 
>   File 
> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  
>
> line 1123, in compile_and_execute 
> exec(compiled, globs) 
>   File " sage.misc.sageinspect._sage_getsourcelines_name_with_dot[5]>", line 1, 
> in  
> B.A.__qualname__ 
> NameError: name 'B' is not defined 
> 

[sage-release] Re: Sage 9.0.beta7 released

[Simon King]

Hi Dima,

which one? meataxe or p_group_cohomology? How would either of them
influence the gap packages? And is there a ticket for it?

Best regards,
Simon

On 2019-11-27, Dima Pasechnik  wrote:
> IIRC this comes from Simon King's optional package.
>
> On Wed, 27 Nov 2019, 16:11 John Cremona,  wrote:
>
>> I had this failure (I have gap_packages installed):
>>
>> sage -t --long --warn-long 59.7 src/sage/tests/gap_packages.py
>> **
>> File "src/sage/tests/gap_packages.py", line 8, in sage.tests.gap_packages
>> Failed example:
>> test_packages(pkgs, only_failures=True)# optional - gap_packages
>> Expected:
>>   Status   Package   GAP Output
>> ++-++
>> Got:
>> #I  method installed for Matrix matches more than one declaration
>>   Status   Package   GAP Output
>> ++-++
>> **
>> 1 item had failures:
>>1 of   5 in sage.tests.gap_packages
>> [11 tests, 1 failure, 4.74 s]
>> --
>> sage -t --long --warn-long 59.7 src/sage/tests/gap_packages.py  # 1
>> doctest failed

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/qrntfn%2444ou%241%40blaine.gmane.org.

[sage-release] Re: Sage 8.9.beta8 released

[Simon King]

Hi!

On 2019-08-25, Volker Braun  wrote:
> I'm inclined to name the next version 9.0. In particular, we now have 
> Python 3 support that, while not perfect, is at least usable so we should 
> mark that with a new major version. Also point-9 is a natural place to 
> switch. If you want to voice your opinion on that issue: now is the time ;-)

Since I found an example of a pickle that cannot be unpickled in
Python-3 (and as far as I can see it is independent of optional
packages), I opened #28444. I believe losing data in the transition from
python-2 to python-3 is a blocker.

It seems to me that the error occurs in Python's pickle module, but I am
not sure. In any case, I'd appreciate help on #28444 by Python-3
experts.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/qkjegh%24743i%242%40blaine.gmane.org.

[sage-release] Re: Sage 8.9.beta7 released

[Simon King]

Hi!

With 8.9.beta7 I get the following doctest failure with gap_packages:

$ ./sage -t --warn-long 51.5 src/sage/tests/gap_packages.py 
Running doctests with ID 2019-08-21-21-10-47-72e22124.
Git branch: develop
Using 
--optional=build,ccache,dochtml,frobby,gap_packages,gdb,gfortran,libsemigroups,meataxe,memlimit,mpir,p_group_cohomology,python2,sage
Doctesting 1 file.
sage -t --warn-long 51.5 src/sage/tests/gap_packages.py
**
File "src/sage/tests/gap_packages.py", line 8, in sage.tests.gap_packages
Failed example:
test_packages(pkgs, only_failures=True)# optional - gap_packages
Expected:
  Status   Package   GAP Output
++-++
Got:
#I  method installed for Matrix matches more than one declaration
  Status   Package   GAP Output
++-++
**
1 item had failures:
   1 of   5 in sage.tests.gap_packages
[11 tests, 1 failure, 5.77 s]
--
sage -t --warn-long 51.5 src/sage/tests/gap_packages.py  # 1 doctest failed
--
Total time for all tests: 5.8 seconds
cpu time: 4.2 seconds
cumulative wall time: 5.8 seconds

I wonder if (in addition to gap_packages) the error depends on meataxe,
as the error mentions "Matrix", and meataxe does provide a matrix
implemenation.

See https://trac.sagemath.org/ticket/28378

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/qjk57f%2478m6%241%40blaine.gmane.org.

[sage-release] Re: Sage 8.7 released

[Simon King]

Hi Samuel,

On 2019-04-17, Samuel Lelièvre  wrote:
> After running "./sage -i p_group_cohomology" again, a look
> in $SAGE_ROOT/local/share/singular/LIB/ revealed that the
> missing file dickson.lib had appeared there.

Hooray! :)

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.7 released

[Simon King]

Hi John,

On 2019-03-27, John H Palmieri  wrote:
> "make PKG-clean" should just look at the appropriate package manifest in 
> local/var/lib/sage/installed, for instance the file 
> "p_group_cohomology-3.1". That file contains a list of installed files, and 
> "make PKG-clean" removes those files. It's not doing anything clever with 
> autotools. (It also doesn't work if the manifest is malformed, which until 
> recently was the case on OS X.)

I just had a look at that file, and it seems that everything from the
package is listed, but not from a sub-package that it contains. In any
case, the file dickson.lib that Samuel was asking about is mentioned in
the manifest.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.7 released

[Simon King]

Hi John, hi Samuel,

On 2019-03-27, John H Palmieri  wrote:
>> Regarding the failures in src/sage/tests/modular_group_cohomology.py 
>> related to the optional package p_group_cohomology (details follow), 
>> can others confirm?

I've not seen it. The folder in which certain gap and singular library
files were installed by p_group_cohomology did change in the disctant
past, but I think it did not change in the last couple of versions.

>> Is there a fix? Should I install extra libraries 
>> for Singular?

No. The file that cannot be found (dickson.lib) is part of
p_group_cohomology.

>> What is the proper way to uninstall the optional package 
>> p_group_cohomology if I need an installation that passes all tests 
>> (say, to run a patchbot)? 
>
> "make p_group_cohomology-clean"  should uninstall the package.

Nice, I didn't know that this works. But since p_group_cohomology's
installation is based on autotools (for one subpackage) and pip (for the
main part of the package), uninstallation should in principle be
supported out of the box. I just didn't know how to "open" that box
using Sage...

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: square root very strange in 8.5.beta3

[Simon King]

Hi!

On 2018-11-15, Erik Bray  wrote:
> Perhaps there should be a common suite of unit tests applicable to
> symbolic functions / functions that can return symbolic expressions in
> order to help ensure a consistent interface.  This is all pretty
> embarrassing :(

Could that be a use case of our category framework? I.e., have a
"category of symbolic expressions", whose only object is SR and whose
morphisms are symbolic functions?

The category framework might be able to provide a unified interface.
Disclaimer: It's just an idea, I didn't study any detail.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.4.beta7 released

[Simon King]

Hi Travis,

On 2018-10-03, tsc...@ucdavis.edu  wrote:
> In the file, I can get anywhere between 0 and 6 tests failing. Note that 
> once this works, it never seems to fail. Also, inserting output into the 
> error, n = 255 and self.order() = 9. I suspect the problem is in 
> Matrix_gfpn_dense as this is not a problem when I go to GF(19^2). I should 
> note that I do have meataxe installed, and I suspect people without meataxe 
> will not have this failure.

When you open a ticket for it, please Cc me.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.rc1 released

[Simon King]

On 2018-03-31, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> fb9f38a4ae (tag: 8.2.rc1) Updated SageMath version to 8.2.rc1
> 97a9c3fe1a Trac #25025: Fix jmol package in Cygwin
> 1fe5f21b49 Trac #25021: Update the jmol SPKG with DESTDIR support
> c67129c035 Trac #25055: Upgrade openssl to 1.1.0h
> f756e2ebe9 Trac #21828: Use MemoryAllocator in generic graphs; fixes crash
> e5c848a64c (tag: 8.2.rc0) Updated SageMath version to 8.2.rc0

I tried to send that message before (using slrn), but since it didn't
show up within 30 minutes, I am trying again.

Giac fails to build.

Setting:
$ uname -a
Linux king-C70-B 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 16.04.4 LTS \n \l

Before that, it used to work in some beta branch (don't recall exactly
which one). Then I installed tkinter, did sage -f python2, and "make
start" (which was rebuilding large portions of Sage, of course). It
still worked. However, I could imagine that it is related to installing
tkinter, as Jeroen told me that people have reported it before, but it
couldn't be reproduced.

The giac log is attached at #25076 (although that ticket's topic is not
related with giac).

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.rc1 released

[Simon King]

On 2018-03-31, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> fb9f38a4ae (tag: 8.2.rc1) Updated SageMath version to 8.2.rc1
> 97a9c3fe1a Trac #25025: Fix jmol package in Cygwin
> 1fe5f21b49 Trac #25021: Update the jmol SPKG with DESTDIR support
> c67129c035 Trac #25055: Upgrade openssl to 1.1.0h
> f756e2ebe9 Trac #21828: Use MemoryAllocator in generic graphs; fixes crash
> e5c848a64c (tag: 8.2.rc0) Updated SageMath version to 8.2.rc0

Giac fails to build.

Machine:
$ uname -a
Linux king-C70-B 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 16.04.4 LTS

The log is attached at #25076.

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi!

On 2018-02-11, Ralf Stephan  wrote:
> Update with clang on Linux: sagelib ignores the --stdlib in CXX (#24705)
> and fpylll apparently ignores the --stdlib in CXX and if you give it in the
> CXXFLAGS it uses it only for C not C++ (#24707). So the former is a build
> blocker, the latter a critical because fpylll cannot be imported. I think
> that's it all.

I also get an error at build time, in ratpoints. See #24708.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi François,

On 2018-02-11, François Bissey  wrote:
> It looks like you may have to provide the include path to __cxxabi_config.h.
> I don’t know where ubuntu installs it. On Gentoo libcxx is configured at build
> time with the right location with the “USE” variable I provided.
> So you may have to have
> CXX=“clang++ -I/path/to/cxxabi -stdlib=libc++”

OK, then I'll retry (from scratch, to be on the safe side) with
   CXX="clang++ -I/usr/include/libcxxabi/ --stdlib=libc++"

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi François,

On 2018-02-10, François Bissey  wrote:
> * if you switch from clang+libstdc++ to clang+libc++ (or libcxx depending on
> your distro)

How can I find out which one I have to use? In all my failing attempts,
I tried clang+libc++.

> Ubuntu is probably the most used distro if someone can wipe up some 
> instructions
> on what to install that would help greatly.

Well, so far I was installing clang, clang-dev and libc++abi-dev. The
latter was in order to get __cxxabi_config.h. However, even after
installing libc++abi-dev (which according to a duckduckgo search is
providing the missing header), brial fails to build for the same reason,
it cannot find __cxxabi_config.h.

> For gentoo setting USE="default-compiler-rt default-libcxx compiler-rt libcxx 
> libcxxabi”

I see that you do something special with libcxxabi. Is perhaps something
similar to do on ubuntu concerning the missing __cxxabi_config.h? But
what?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

In the failing compilation, we have

clang++ --stdlib=libc++ [which is what we want]
... -std=c++11 [which comes from brial]
... -c BlockDegLexOrder.cc  -fPIC -DPIC -o .libs/BlockDegLexOrder.o

And the error is then
/usr/include/c++/v1/cxxabi.h:21:10: fatal error: '__cxxabi_config.h'
file not found
#include <__cxxabi_config.h>

So, it seems (after some duckduckgoing) that I also need to install
libc++abi-dev

Hence, I had to install clang, clang-dev, libc++abi-dev so far. These
things should (if clang is supposed to be a serious option for Sage) be
mentioned in the documentation, as prerequisites.

Since I have enough time, I am starting over from scratch (i.e., make
distclean)

Regards,
Simon


On 2018-02-10, Simon King <simon.k...@uni-jena.de> wrote:
> Hi!
>
> After installation of clang-dev, I tried again, but alas, brial failed
> to build again.
>
> Log is at
> http://users.minet.uni-jena.de/cohomology/logs/brial-1.0.1.p2.log
>
> So, I am giving up on it for now.
>
> Best regards,
> Simon
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi!

After installation of clang-dev, I tried again, but alas, brial failed
to build again.

Log is at
http://users.minet.uni-jena.de/cohomology/logs/brial-1.0.1.p2.log

So, I am giving up on it for now.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Dear John,

On 2018-02-10, John Cremona  wrote:
> I installed clang on my ubuntu laptop.  I use synaptic ( a front-end for
> apt & co) for installing stuff as it's easier to search.

Thanks a lot!

When searching for clang-devel in synaptic, I was pointed to
libclang-dev (not -devel). I installed it and will now restart building
Sage with clang. Keeping fingers crossed...

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

On 2018-02-10, Simon King <simon.k...@uni-jena.de> wrote:
> I'll try to search for "clang-devel ubuntu".

No real success, except for some very complicated procedures
given at
https://askubuntu.com/questions/309786/llvm-and-clang-installation-on-ubuntu
and lots of stuff that isn't mentioning ubuntu.

So, probably time to give up the idea of trying Sage with clang on my
laptop.

Best regards,
Simovery complicated procedures
given at
https://askubuntu.com/questions/309786/llvm-and-clang-installation-on-ubuntu
and lots of stuff that isn't mentioning ubuntu.

So, probably time to give up the idea of trying Sage with clang on my
laptop.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi Ralf,

On 2018-02-10, Ralf Stephan  wrote:
> You're missing a devel system package. I have it in clang-devel and
> libc++-devel.

I have libc++-devel (because it seems to be the only "libc++" available
for ubuntu). But clang-devel isn't known to apt-get.

I'll try to search for "clang-devel ubuntu". Unless some people here are
answering more quickly...

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

On 2018-02-10, Ralf Stephan  wrote:
> The linking error with --stdlib=libc++ persists. It appears ntl_ZZ.so is
> built with both libstdc++ and libc++:

At least while building, ntl did not complain, see
  http://users.minet.uni-jena.de/cohomology/logs/ntl-10.3.0.log

However, this time with
  CC=clang CXX="clang++ --stdlib=libc++" make
it is brial that's failing to build. See
  http://users.minet.uni-jena.de/cohomology/logs/brial-1.0.1.p2.log

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

On 2018-02-10, Ralf Stephan  wrote:
> Also clang-5.0.0 cannot compile ppl. clang-3.8 and 4.0.1 are fine.
> https://trac.sagemath.org/ticket/24704

According to my log, ppl-1.2 was built fine. But I guess that's because
I have clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final)

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi Ralf,

On 2018-02-10, Ralf Stephan  wrote:
> Simon do you have libc++ system-installed and given CXX='clang++
> --stdlib=libc++' ?

How would I check whether I have libc++ installed? Resp. how would I
install it? sudo apt-get install libc++ gives loads of errors.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi Ralf,

On 2018-02-10, Ralf Stephan  wrote:
> Simon do you have libc++ system-installed and given CXX='clang++
> --stdlib=libc++' ?

No, I followed the previous advice to give CC=clan CXX=clan++.

Does that mean I should make distclean and start again from scratch?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

On 2018-02-10, Simon King <simon.k...@uni-jena.de> wrote:
> On 2018-02-10, Simon King <simon.k...@uni-jena.de> wrote:
>> Hi François,
>>
>> On 2018-02-10, François Bissey <frp.bis...@gmail.com> wrote:
>>> I’d recommend to work on a separate clone. It is what I have done
>>> on my Gentoo linux box.
>>
>> This is what I did now. It is still in the process of building.
>
> While it was building, I noticed lines such as
>   [python_openid-2.2.5.p0] Found candidate GCC installation:  
> /usr/bin/../lib/gcc/i686-linux-gnu/5.4.0
>
> Does that mean python_openid will in fact not be build with clang?
> Wouldn't that create a mess?

giac fails to build. Log is at
http://users.minet.uni-jena.de/cohomology/logs/giac-1.4.9.45.p1.log

I also copied the python_openid log, so that you can investigate the
"candidate GCC installation" thingy:
http://users.minet.uni-jena.de/cohomology/logs/python_openid-2.2.5.p0.log
If I understand the log correctly, it is in fact using clang for
compilation, though.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi Ralf,

On 2018-02-10, Ralf Stephan  wrote:
> FWIW for me as Pynac dev clang has far superior diagnostics and refactoring
> tools. From other programs I can confirm a speedup of compiled source of at
> least 5%.

Interesting. In threads from 2013, I also found that clang had better
diagnostics, but gcc's optimisation was superior. So, has the latter
changed? I'll see what it will do with my spkgs...

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

On 2018-02-10, Simon King <simon.k...@uni-jena.de> wrote:
> Hi François,
>
> On 2018-02-10, François Bissey <frp.bis...@gmail.com> wrote:
>> I’d recommend to work on a separate clone. It is what I have done
>> on my Gentoo linux box.
>
> This is what I did now. It is still in the process of building.

While it was building, I noticed lines such as
  [python_openid-2.2.5.p0] Found candidate GCC installation:  
/usr/bin/../lib/gcc/i686-linux-gnu/5.4.0

Does that mean python_openid will in fact not be build with clang?
Wouldn't that create a mess?

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi François,

On 2018-02-10, François Bissey  wrote:
> I’d recommend to work on a separate clone. It is what I have done
> on my Gentoo linux box.

This is what I did now. It is still in the process of building.

Will the SageMath installation recall that it was installed with clang?
By that, I mean: What will happen if I do further compilations later,
either with `sage -b`, `sage -i meataxe` or `make build`? Will all three
commands automatically use clang? Or would I still need to prepend
everything with `CC=clang CXX=clang++`?

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.2.beta5 released

[Simon King]

Hi,

I'd like to get some information.

On 2018-02-09, François Bissey  wrote:
>> On 9/02/2018, at 23:03, Ralf Stephan  wrote:
>> 
>> So how to use clang on Linux?

*Why* to use clang in the first place? I am not familiar with it, so I'd
appreciate if you could summarise its advantages and disadvantages.

What I found by my own search: clang's machine code generation is faster than
gcc's. However: Does that also result in faster programs, or just in less
build time? Thanks to ccache, the time to build Sage doesn't matter so much
to me any longer. But I do care about the speed of the resulting programs.

Here are reports that with clang things won't work in different ways
(e.g., IIUC, segfaults in linbox on openSuse). Does that mean clang is
buggy resp. not mature enough, or does that mean clang uncovers real
bugs that are silently ignored by gcc?

And if I want to give it a try: Currently I have a SageMath installation
compiled with gcc. Does it suffice to "make clean" before starting
re-installation of SageMath with clang? Or "make distclean"?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1.rc0 released

[Simon King]

Hi John,

On 2017-11-17, John H Palmieri  wrote:
>> And WHY that change was made! 
>>
>
> If it takes a while to build the documentation, better to start as soon as 
> possible, rather than to wait until the last possible time, right?

If the user's purpose is to use Sage, better make it usable as soon as
possible.

Moreover: Have the for-years-frequently-occurring "sporadic" doc build
failures been fixed at last? Otherwise: Better build as soon as possible
what does reliably build (i.e., sage/src), rather than frustrating the user.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1.rc0 released

[Simon King]

On 2017-11-17, Thierry <sage-googlesu...@lma.metelu.net> wrote:
> On Fri, Nov 17, 2017 at 02:37:37PM +0000, Simon King wrote:
>
>> Is it still possible to build SageMath without documentation ("make start")?
>
>   make build

Thanks!


-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1.beta2 released

[Simon King]

Hi Travis,

On 2017-08-21, tsc...@ucdavis.edu  wrote:
> It is in a cython file, but it is not a cpdef method. However, I think 
> avoiding dict() (and using .iteritems() instead of items() because it is 
> Cython [so it is still Py3 compatible]) for non-sparse polynomials is good. 
> Actually, as you suggest, using the specific data structures would likely 
> be a lot faster. Do you want to start work on this, which I will happily 
> review, or do you want me to?

I am not so sure whether I will tackle specific polynomial types. However,
I think I can provide a speed up of the generic implementation: Instead
of self.dict().items(), one should work with self.list(copy=False), which
is called by self.dict() anyway, thus avoiding the overhead of constructing
a dict and its items:

   sage: R. = SR[]
   sage: p = prod(x+i for i in range(60))
   sage: %timeit R([int(v)%123 for v in p.list(copy=False)])
   100 loops, best of 3: 5.13 ms per loop
   sage: %timeit p.map_coefficients(lambda z: int(z)%123)
   100 loops, best of 3: 11 ms per loop

And that's in Python (= Sage command line), not Cython.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1.beta2 released

[Simon King]

Hi Travis,

On 2017-08-17, tsc...@ucdavis.edu  wrote:
> about half of the time is in
>
> {method 'map_coefficients' of 
> 'sage.rings.polynomial.polynomial_element.Polynomial' objects}
>
> and subfunction calls. I would say a better solution would include 
> improving Polynomial.map_coefficients(). It probably would benefit from 
> more specialized implementations, specifically sparse and dense 
> implementations, as well as cythonization.

What kind of polynomials is involved in that test? libsingular?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Why is gcc built?

[Simon King]

Hi Erik,

On 2017-02-23, Erik Bray  wrote:
> IMHO building Sage should not just forge ahead with building its own
> gcc without asking.  I think it's bad enough that it's a package at
> all, but as long as it is it should be strictly optional, and if the
> version check fails for gcc/gfortran the build should just refuse to
> continue (i.e. `./configure` would exit with an error) providing
> information on what version checks were performed, what failed, and
> mention that if desired sage can be built --with-gcc or something in
> which case it will add gcc to the build.

Sounds like a good idea to me. And could perhaps be generalised towards
a proper modularisation of Sage. In the sense of:
- If Sage is known to work with a system-wide installation of something (such
  as: gcc, blas, r [just to give an example, I don't know if Sage can really
  work with a system-wide blas or r]), then the default should be to use it.
- ./configure tests if these modules are installed in an appropriate
  version. If an appropriate version is not installed, it fails with an
  error and tells the user how to install the stuff.
- The user has the possibility to force Sage to build its own modules.
  Say, by doing `./configure --build="gcc r"`, Sage would build both gcc
  and r (regardless whether they are available on the machine), but
  would still use the existing blas. Of course, the error message mentioned
  in the previous point should tell about the `--build` option.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Why is gcc built?

[Simon King]

Hi Dima,

On 2017-02-22, Dima Pasechnik  wrote:
> Looks like gcc spkg will not be built, just as you want.

OK, then all is good.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Why is gcc built?

[Simon King]

After installing gfortran (not gfortan5 or gfortran5, which doesn't seem to 
exist), I still see various errors in config.log concerning fortran (see 
attachment) --- I don't know if Sage would still build its own gcc, but 
perhaps you can see from the new config.log what would happen.

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
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 7.6.beta4, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure 

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

hostname = king-ThinkPad-T430
uname -m = x86_64
uname -r = 4.4.0-62-generic
uname -s = Linux
uname -v = #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017

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

/bin/arch  = unknown
/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/king/bin
PATH: /home/king/.local/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games
PATH: /snap/bin


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

configure:2313: checking for a BSD-compatible install
configure:2381: result: /usr/bin/install -c
configure:2392: checking whether build environment is sane
configure:2447: result: yes
configure:2598: checking for a thread-safe mkdir -p
configure:2637: result: /bin/mkdir -p
configure:2644: checking for gawk
configure:2660: found /usr/bin/gawk
configure:2671: result: gawk
configure:2682: checking whether make sets $(MAKE)
configure:2704: result: yes
configure:2733: checking whether make supports nested variables
configure:2750: result: yes
configure:2879: checking whether to enable maintainer-specific portions of 
Makefiles
configure:2888: result: yes
configure:2955: checking for root user
configure:2964: result: no
configure:2975: checking build system type
configure:2989: result: x86_64-pc-linux-gnu
configure:3009: checking host system type
configure:3022: result: x86_64-pc-linux-gnu
configure:3136: checking for ar
configure:3152: found /usr/bin/ar
configure:3164: result: yes
configure:3185: checking for m4
configure:3201: found /usr/bin/m4
configure:3213: result: yes
configure:3234: checking for ranlib
configure:3250: found /usr/bin/ranlib
configure:3262: result: yes
configure:3283: checking for strip
configure:3299: found /usr/bin/strip
configure:3311: result: yes
configure:3331: checking for GNU or BSD tar
configure:3379: result: /bin/tar
configure:3390: checking for GNU make
configure:3432: result: /usr/bin/make
configure:3446: checking for latex
configure:3462: found /usr/bin/latex
configure:3474: result: yes
configure:3498: checking for perl
configure:3516: found /usr/bin/perl
configure:3528: result: /usr/bin/perl
configure:3536: checking for Perl version 5.8.0 or later
configure:3547: result: yes
configure:3559: checking for git
configure:3591: result: /usr/bin/git
configure:3687: checking for gcc
configure:3703: found /usr/bin/gcc
configure:3714: result: gcc
configure:3943: checking for C compiler version
configure:3952: gcc --version >&5
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3963: $? = 0
configure:3952: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
5.4.0-6ubuntu1~16.04.4' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-5 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 

[sage-release] Re: Why is gcc built?

[Simon King]

Hi John,

On 2017-02-22, John Cremona  wrote:
> It would be helpful for anyone in Simon's position if, after
> configure, there was a message saying something like "your build will
> be faster if you install the following system-wide: gfortran, ... "
> but I'm sure it will be hard to have such a message apply accurately
> in all situations.

This would be helpful for users doing ./configure separately (which I
didn't). It has simply been my lack of care when reading the manual.

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Why is gcc built?

[Simon King]

PS:

On 2017-02-22, Simon King <simon.k...@uni-jena.de> wrote:
>  Aha. Although I did "apt-get install gcc-fortran", gfortran is not there.

And the reason is that apparently I didn't read the development manual
with enough care. It advises to install gfortran (resp gcc-gfortran on
redhat), and probably I tried gcc-fortran instead (which has failed, so,
I really wonder why I didn't notice).

Anyway, I now have SageMath on yet another laptop, and am looking
forward to SageDays!

Thank you,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Why is gcc built?

[Simon King]

Am Mittwoch, 22. Februar 2017 17:04:21 UTC+1 schrieb Jeroen Demeyer:
>
> On 2017-02-22 16:50, Simon King wrote: 
> > In other words, I still don't see why gcc should be rebuilt (unless the 
> > developer's manual needs update). 
>
> Can you post the config.log file? 
>
>
Voilà!

Cheers,
Simon 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
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 7.6.beta4, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure 

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

hostname = king-ThinkPad-T430
uname -m = x86_64
uname -r = 4.4.0-62-generic
uname -s = Linux
uname -v = #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017

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

/bin/arch  = unknown
/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/king/bin
PATH: /home/king/.local/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games
PATH: /snap/bin


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

configure:2313: checking for a BSD-compatible install
configure:2381: result: /usr/bin/install -c
configure:2392: checking whether build environment is sane
configure:2447: result: yes
configure:2598: checking for a thread-safe mkdir -p
configure:2637: result: /bin/mkdir -p
configure:2644: checking for gawk
configure:2660: found /usr/bin/gawk
configure:2671: result: gawk
configure:2682: checking whether make sets $(MAKE)
configure:2704: result: yes
configure:2733: checking whether make supports nested variables
configure:2750: result: yes
configure:2879: checking whether to enable maintainer-specific portions of 
Makefiles
configure:2888: result: yes
configure:2955: checking for root user
configure:2964: result: no
configure:2975: checking build system type
configure:2989: result: x86_64-pc-linux-gnu
configure:3009: checking host system type
configure:3022: result: x86_64-pc-linux-gnu
configure:3136: checking for ar
configure:3152: found /usr/bin/ar
configure:3164: result: yes
configure:3185: checking for m4
configure:3201: found /usr/bin/m4
configure:3213: result: yes
configure:3234: checking for ranlib
configure:3250: found /usr/bin/ranlib
configure:3262: result: yes
configure:3283: checking for strip
configure:3299: found /usr/bin/strip
configure:3311: result: yes
configure:3331: checking for GNU or BSD tar
configure:3379: result: /bin/tar
configure:3390: checking for GNU make
configure:3432: result: /usr/bin/make
configure:3446: checking for latex
configure:3462: found /usr/bin/latex
configure:3474: result: yes
configure:3498: checking for perl
configure:3516: found /usr/bin/perl
configure:3528: result: /usr/bin/perl
configure:3536: checking for Perl version 5.8.0 or later
configure:3547: result: yes
configure:3559: checking for git
configure:3591: result: /usr/bin/git
configure:3687: checking for gcc
configure:3703: found /usr/bin/gcc
configure:3714: result: gcc
configure:3943: checking for C compiler version
configure:3952: gcc --version >&5
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3963: $? = 0
configure:3952: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
5.4.0-6ubuntu1~16.04.4' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-5 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj

[sage-release] Re: Sage 7.6.beta2 released

[Simon King]

Hi!

On 2017-02-04, Daniel Krenn  wrote:
>> Should 'make ptestlong' ignore the content of 'init.sage'?
>
> +1, I think (without having thought too much about it...)

+1. IIRC, init.sage is about the user's personal configuration
for interactive sessions, and s/he might want to use, say, implicit
multiplication (such that 4x rather than 4*x becomes valid syntax). But
in any task that is not interactive, which includes doctesting, the
interactor's (i.e., user's) personal configuration should be irrelevant.

Cheers,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: sagedev error

[Simon King]

Hi Volker,

On 2015-07-17, Volker Braun vbraun.n...@gmail.com wrote:
 This might be (accidentally) fixed by #18909, if not please open a ticket...

Accidentally? The example in the ticket description looks exactly like
the error I'm getting...

So, it is not in sage-6.8.rc0? Because that's where I get the error.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] sagedev error

[Simon King]

Hi!

With rerere enabled in git (after a suggestion of Volker), I get
Failed example:
alice.pull()
Expected:
Merging the remote branch u/bob/ticket/1 into the local branch ticket/1.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alices_file
CONFLICT (add/add): Merge conflict in alices_file
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are 
finished,
your resolution will be commited.
Finished? [ok/Abort] abort
Got:
Merging the remote branch u/bob/ticket/1 into the local branch ticket/1.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alices_file
CONFLICT (add/add): Merge conflict in alices_file
Recorded preimage for 'alices_file'
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are 
finished, your resolution will be commited.
Finished? [ok/Abort] abort

I think I reported that here before, but did not create a ticket. Did
someone else open a ticket for it?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.7.beta4 released

[Simon King]

Hi Leif,

On 2015-05-13, leif not.rea...@online.de wrote:
 ROFL, reviewing/merging #15642 that is.

 You can safely pull the branch there, then using a mirror.

 Or download the upstream tarballs manually from a mirror (they're in
 spkg/upstream/, not packages/upstream/).

Really?

 wget http://www.sagemath.org/spkg/upstream/pari/pari-2.8-1545-gd04cdd3.tar.gz
--2015-05-13 20:43:20--  
http://www.sagemath.org/spkg/upstream/pari/pari-2.8-1545-gd04cdd3.tar.gz
Auflösen des Hostnamen »www.sagemath.org (www.sagemath.org)«... 199.27.78.133, 
23.235.43.133
Verbindungsaufbau zu www.sagemath.org (www.sagemath.org)|199.27.78.133|:80... 
verbunden.
HTTP-Anforderung gesendet, warte auf Antwort... 404 Not Found
2015-05-13 20:43:23 FEHLER 404: Not Found.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.7.beta4 released

[Simon King]

Hi Leif,

On 2015-05-13, leif not.rea...@online.de wrote:
 ROFL, reviewing/merging #15642 that is.

In other words, the current develop is broken to the extent that one
wouldn't even be able to download stuff without an unreviewed branch?
Sweet.

I am pulling from the latest develop in order to resolve a merge
conflict with #16453. How to do it with a broken develop? Do I
understand correctly: I pull from #15642, build sage, remove the
commits from #15642 (otherwise, these commits would become part of
the to-be-reviewed commits for #16453) and then merge with #16453?

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.7.beta4 released

[Simon King]

Hi!

I get the following error when trying to build SageMath after pulling
develop:

...
patching file Cython/Includes/cpython/weakref.pxd
patching file Cython/Includes/numpy/__init__.pxd
Traceback (most recent call last):
  File stdin, line 35, in module
  File /home/king/Sage/git/sage/local/lib/python/urllib.py, line 240, in 
retrieve
fp = self.open(url, data)
  File /home/king/Sage/git/sage/local/lib/python/urllib.py, line 208, in open
return getattr(self, name)(url)
  File /home/king/Sage/git/sage/local/lib/python/urllib.py, line 359, in 
open_http
return self.http_error(url, fp, errcode, errmsg, headers)
  File /home/king/Sage/git/sage/local/lib/python/urllib.py, line 376, in 
http_error
return self.http_error_default(url, fp, errcode, errmsg, headers)
  File stdin, line 17, in http_error_default
IOError: [Errno 404] Not Found: 
'//www.sagemath.org/packages/upstream/pari/pari-2.8-1545-gd04cdd3.tar.gz'
Error: failed to download package pari-2.8-1545-gd04cdd3.p0
Makefile:643: recipe for target 
'/home/king/Sage/git/sage/local/var/lib/sage/installed/pari-2.8-1545-gd04cdd3.p0'
 failed
make[2]: *** 
[/home/king/Sage/git/sage/local/var/lib/sage/installed/pari-2.8-1545-gd04cdd3.p0]
 Error 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
Unable to find pgen, not compiling formal grammar.
Compiling module Cython.Plex.Scanners ...
Compiling module Cython.Plex.Actions ...
...

Shouldn't it try to download the pari package from http://www.sagemath.org, not 
from //www.sagemath.org?

Best regards,
Simon



-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.6.rc3 released

[Simon King]

Hi Rob,

On 2015-04-13, Rob Beezer goo...@beezer.cotse.net wrote:
 Passed immediately on solo try.  Full log file should be public at: 

 https://cloud.sagemath.com/projects/53b77207-8614-4086-a032-432af4b4cdbd/files/sage-dev-images/sage-6.6.rc3/logs/ptestlong.log

I can't open it.

 sage -t --long --warn-long 114.3 src/sage/modular/modform/ambient.py
 **
 File src/sage/modular/modform/ambient.py, line 812, in 
 sage.modular.modform.ambient.?._compute_hecke_matrix
 Failed example:
 f = t.charpoly()   # long time (4s)
 Expected nothing
 Got:
 you are running out of primes. 1000 coprime primes found

OK, that doesn't look like garbage collection artifact to me...

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Error building sagenb

[Simon King]

Hi Volker,

On 2015-04-07, Volker Braun vbraun.n...@gmail.com wrote:
 See http://trac.sagemath.org/ticket/18131

... which says pip requires ssl.

Does that mean openssl is not enough any more?

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Error building sagenb

[Simon King]

Hi François,

On 2015-04-07, Francois Bissey francois.bis...@canterbury.ac.nz wrote:
 pip came into play here:
 http://trac.sagemath.org/ticket/17913
 basically at least one component (webassets) keep being difficult with
 easy-install and the decision was made to use pip for sagenb.
 You are not the first one to see this and it means you probably don’t openssl
 development packages installed in your host distro.

I did install them today, and I did rebuild pip, namely sage -f pip,
after installing libopenssl-devel. I do not have libgnutls-openssl-devel
and not libopenssl-devel-32bit (I have a 64 bit openSUSE installation).

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Error building sagenb

[Simon King]

Hi Volker,

On 2015-04-07, Volker Braun vbraun.n...@gmail.com wrote:
 Did you compile Sage after installing openssl-devel? Python must build the 
 ssl module. Does import ssl work? 

No, import ssl in sage-python fails with ImportError: No module named
_ssl (note the underscore).

What I did (without success) was make start. So, I take it that make
start would not recognise the presence of openssl-devel, so that I need
to rebuild sage-python by ./sage -f python, and then do make start
again.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Error building sagenb

[Simon King]

Hi Jeroen,

On 2015-04-07, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
 Since pip depends on Python, the following should be enough:

 sage -f python
 make

Yes, that did the job. Thank you very much!

Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.6.rc1 released

[Simon King]

Hi!

git status gives me many unbeobachtete Dateien:
src/sage/categories/category.c
src/sage/categories/category_with_axiom.c
src/sage/misc/inputhook.c
src/sage/misc/readline_extra_commands.c
src/sage/rings/padics/padic_base_coercion.c
src/sage/rings/padics/padic_base_generic_element.c
src/sage/rings/residue_field.c
src/sage/structure/bounded_integer_sequences.c

And I get errors in
  sage -t src/sage/dev/sagedev.py

Namely:

File src/sage/dev/sagedev.py, line 1143, in sage.dev.sagedev.SageDev.pull
Failed example:
alice.pull()
Expected:
Merging the remote branch u/bob/ticket/1 into the local branch ticket/1.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alices_file
CONFLICT (add/add): Merge conflict in alices_file
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are 
finished,
your resolution will be commited.
Finished? [ok/Abort] abort
Got:
Merging the remote branch u/bob/ticket/1 into the local branch ticket/1.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alices_file
CONFLICT (add/add): Merge conflict in alices_file
Recorded preimage for 'alices_file'
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are 
finished, your resolution will be commited.
Finished? [ok/Abort] abort
**
File src/sage/dev/sagedev.py, line 3128, in sage.dev.sagedev.SageDev.merge
Failed example:
alice.merge(#1)
Expected:
Merging the remote branch u/bob/ticket/1 into the local branch ticket/2.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alice2
CONFLICT (add/add): Merge conflict in alice2
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are 
finished,
your resolution will be commited.
Finished? [ok/Abort] abort
Got:
Merging the remote branch u/bob/ticket/1 into the local branch ticket/2.
Automatic merge failed, there are conflicting commits.
BLANKLINE
Auto-merging alice2
CONFLICT (add/add): Merge conflict in alice2
Recorded preimage for 'alice2'
BLANKLINE
Please edit the affected files to resolve the conflicts. When you are 
finished, your resolution will be commited.
Finished? [ok/Abort] abort
**

Is that a problem with my local git configuration? If so, how can I
solve it?

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.6.rc1 released

[Simon King]

Hi Volker,

On 2015-03-30, Volker Braun vbraun.n...@gmail.com wrote:
 You can delete the extraneous files.

OK. But how did they come there? I thought that meanwhile there is a
separate folder for compiling Sage code.

 It seems you have the git rerere extension enabled

Indeed I have. So, you can see that I am following your advices
sometimes...

 which leads to a 
 slightly different git output. You could add an appropriate ellipsis to the 
 doctests...

OK, I'll try.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: What to do to build 6.3.beta3?

[Simon King]

Hi Leif,

On 2014-06-07, leif not.rea...@online.de wrote:
 You can simply

 wget http://sagemath.org/packages/upstream/configure/configure-33.tar.gz

 and extract the tarball in $SAGE_ROOT (or just the two [to four] missing 
 files in config/), then retry 'sage -i ecl'.

I think I have already posted that I installed autotools via yast -i
libtool, and this seems to do the trikc.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.3.beta1 released

[Simon King]

Hi Ralf,

On 2014-05-13, Ralf Stephan gtrw...@gmail.com wrote:
 GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core
 but git is in local/bin/?

king@linux-etl7:~/Sage/git/sage which git
/usr/bin/git
sage-sh) king@linux-etl7:sage$ which git
/home/king/Sage/git/sage/local/bin/git

Anyway, this was with 6.3.beta0, and I now retry with beta1.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.3.beta1 released

[Simon King]

Hi again,

On 2014-05-13, Simon King simon.k...@uni-jena.de wrote:
 Anyway, this was with 6.3.beta0, and I now retry with beta1.

Frankly I am disappointed about the current quality of doc-building.

After pulling, make fails with
Note: incremental documentation builds sometimes cause spurious
error messages. To be certain that these are real errors, run
make doc-clean first and try again.
Traceback (most recent call last):
  File /home/king/Sage/git/sage/src/doc/common/builder.py, line 1477, in 
module
getattr(get_builder(name), type)()
  File /home/king/Sage/git/sage/src/doc/common/builder.py, line 276, in 
_wrapper
getattr(get_builder(document), 'inventory')(*args, **kwds)
  File /home/king/Sage/git/sage/src/doc/common/builder.py, line 487, in 
_wrapper
x.get(9)
  File /home/king/Sage/git/sage/local/lib/python/multiprocessing/pool.py, 
line 554, in get
raise self._value
OSError: [misc ] docstring of sage.misc.c3_controlled.HierarchyElement:10: 
WARNING: Inline literal start-string without end-string.

make doc-clean followed by make doc solved the problem. But it really
sucks and consumes an awful amount of time that *most* non-trivial changes
of a branch result in these spurious error messages!

Anyway. Worse is: The tests in sage.dev fail as before. And it seems to
be because of the git that comes with sage: When I use the system git,
then of course git pull works. But in a sage shell, I get:

(sage-sh) king@linux-etl7:sage$ git pull
git: 'pull' ist kein Git-Kommando. Siehe 'git --help'.

Haben Sie das gemeint?
shell

So, both beta0 and beta1 are broken because of the git shipped by
Sage.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.3.beta1 released

[Simon King]

Hi John,

On 2014-05-13, John H Palmieri jhpalmier...@gmail.com wrote:
 In git's 'configure' script, it says:

 libexecdir='${exec_prefix}/libexec'

 and on the few platforms to which I have access, I see libexec, not lib. 
 What platform are you using?

openSuse 12.3

 Do you have any environment variables set 
 which could be interfering with this?

I am not aware of.

Also, it did use to work prior to sage-6.3.beta0, and I have nothing
changed in the environment variables since.

git is in the path (in the sage shell). But nonetheless it does not
know the pull command.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Page with closed tickets for sage-6.1 and sage-6.1.1 does not exist

[Simon King]

Hi!

As it seems, I can't post to sage-announce, where it was announced that
sage-6.1 and sage-6.1.1 have been released. The announcement points to
http://boxen.math.washington.edu/home/release/sage-6.1/tickets.html for
a list of closed tickets, but this URL does not seem to exist on the
server. Similarly for sage-6.1.1.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.

[sage-release] Re: Sage 6.0 released

[Simon King]

Hi Georg,

On 2014-01-18, Georg Grafendorfer georg.grafendor...@gmail.com wrote:
 The search is not over yet, but so far this was found:

 ./hg/s/linux/rhel3_amd64/app/gap/3.4.4/bin/gap-static-linux-i686

 which gap-static-linux-i686 does not yield anything, but one can do

 ggeorg@maschke% which gap
 /usr/local64.hg/bin/gap
 ggeorg@maschke% which gap3
 /usr/local64.hg/bin/gap3

What is the answer if you execute the same in a Sage shell? I.e., do
  sage -sh
and then do
  which gap

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.

[sage-release] Re: Releasing Sage 6.0

[Simon King]

Hi Volker,

On 2013-12-18, Volker Braun vbraun.n...@gmail.com wrote:
 This is the first official release for Sage 6, which from now on will use 
 git and a single unified repository.

Congratulation!

 * The master branch will stay at 6.0 until 6.1 is released
 * The develop branch will soon move on to 6.1.beta0

Does this mean that for doing development work on trac, one should
henceforth do git checkout trac develop rather than git checkout trac
master (or whatever git command is used), or are you just talking about
the master branch of the github repository? Will the trac master stay at
6.0 as well?

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.