[sage-devel] error compiling ntl in sage 7.3.beta8
Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem compiling ntl 9.8.1. Not sure what to include. Just ask. Chris Host system: Linux pmlapsag01 2.6.32-642.1.1.el6.x86_64 #1 SMP Tue May 31 21:57:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/home/sageadm/sage/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../src/configure --prefix=/home/sageadm/sage/local --with-local-prefix=/home/sageadm/sage/local --with-gmp=/home/sageadm/sage/local --with-mpfr=/home/sageadm/sage/local --with-mpc=/home/sageadm/sage/local --with-system-zlib --disable-multilib --disable-nls --enable-languages=c,c++,fortran --disable-libitm Thread model: posix gcc version 4.9.3 (GCC) Applying patches to NTL. config.status: executing libtool commands Configuring NTL. * checking for libtool * libtool (GNU libtool) 2.4.2 Written by Gordon Matzigkeit < ... >, 1996 Copyright (C) 2011 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. * libtool OK * *** checking -march=native flag CXXAUTOFLAGS=" -march=native" *** -march=native works CXXAUTOFLAGS=" -march=native" [ntl-9.8.1.p0] Tuning and building NTL. [ntl-9.8.1.p0] make[3]: Entering directory `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' [ntl-9.8.1.p0] make setup1 [ntl-9.8.1.p0] make[4]: Entering directory `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g -c MakeDescAux.c [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g -L/home/sageadm/sage/local/lib -Wl,-rpath,/home/sageadm/sage/local/lib -o MakeDesc MakeDesc.c MakeDescAux.o -lm [ntl-9.8.1.p0] /tmp/ccPRNw4z.s: Assembler messages: [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:873: Error: no such instruction: `shlx %r12,%rax,%rax' [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:932: Error: no such instruction: `shlx %r12,%rax,%rax' ... [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4374: Error: no such instruction: `shlx %rax,%r15,%r15' [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4791: Error: no such instruction: `shlx %r13,%rdx,%rdx' [ntl-9.8.1.p0] make[4]: *** [setup1] Error 1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Did trac server change its rsa keys?
Trying to `git trac push` I get the following error message. Is it expected
or someone is trying to MITM me?
Traceback (most recent call last):
File "/home/mmarco/git-trac-command/bin/git-trac", line 18, in
cmdline.launch()
File "/home/mmarco/git-trac-command/git_trac/cmdline.py", line 223, in
launch
app.push(ticket_number, remote=args.remote, force=args.force)
File "/home/mmarco/git-trac-command/git_trac/app.py", line 216, in push
self.repo.push(remote, force)
File "/home/mmarco/git-trac-command/git_trac/git_repository.py", line
197, in push
self.git.echo.push('trac', refspec)
File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 341,
in meth
return self.execute(git_cmd, *args, **kwds)
File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 98,
in execute
popen_stderr=subprocess.PIPE)
File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 263,
in _run
raise GitError(result)
git_trac.git_error.GitError: git returned with non-zero exit code (128)
when executing "git push trac
HEAD:refs/heads/u/mmarco/implement_zariski_vankampen_method_to_compute_fundamental_groups_of_complements_of_plane_curves_"
STDERR: @@@
STDERR: @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
STDERR: @@@
STDERR: The RSA host key for trac.sagemath.org has changed,
STDERR: and the key for the corresponding IP address 104.197.143.230
STDERR: is unknown. This could either mean that
STDERR: DNS SPOOFING is happening or the IP address for the host
STDERR: and its host key have changed at the same time.
STDERR: @@@
STDERR: @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
STDERR: @@@
STDERR: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
STDERR: Someone could be eavesdropping on you right now
(man-in-the-middle attack)!
STDERR: It is also possible that a host key has just been changed.
STDERR: The fingerprint for the RSA key sent by the remote host is
STDERR: SHA256:EKc2ZL+lJTCACVtZODKxeCJDuIecTw6r1kJXw9qN/Sg.
STDERR: Please contact your system administrator.
STDERR: Add correct host key in /home/mmarco/.ssh/known_hosts to get
rid of this message.
STDERR: Offending RSA key in /home/mmarco/.ssh/known_hosts:2
STDERR: RSA host key for trac.sagemath.org has changed and you have
requested strict checking.
STDERR: Host key verification failed.
STDERR: fatal: Could not read from remote repository.
STDERR:
STDERR: Please make sure you have the correct access rights
STDERR: and the repository exists.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Did trac server change its rsa keys?
Surely this means exactly what it says, since the IP address of trac
really has changed.
John
On 19 July 2016 at 14:47, mmarco wrote:
> Trying to `git trac push` I get the following error message. Is it expected
> or someone is trying to MITM me?
>
> Traceback (most recent call last):
> File "/home/mmarco/git-trac-command/bin/git-trac", line 18, in
> cmdline.launch()
> File "/home/mmarco/git-trac-command/git_trac/cmdline.py", line 223, in
> launch
> app.push(ticket_number, remote=args.remote, force=args.force)
> File "/home/mmarco/git-trac-command/git_trac/app.py", line 216, in push
> self.repo.push(remote, force)
> File "/home/mmarco/git-trac-command/git_trac/git_repository.py", line 197,
> in push
> self.git.echo.push('trac', refspec)
> File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 341,
> in meth
> return self.execute(git_cmd, *args, **kwds)
> File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 98,
> in execute
> popen_stderr=subprocess.PIPE)
> File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 263,
> in _run
> raise GitError(result)
> git_trac.git_error.GitError: git returned with non-zero exit code (128) when
> executing "git push trac
> HEAD:refs/heads/u/mmarco/implement_zariski_vankampen_method_to_compute_fundamental_groups_of_complements_of_plane_curves_"
> STDERR: @@@
> STDERR: @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
> STDERR: @@@
> STDERR: The RSA host key for trac.sagemath.org has changed,
> STDERR: and the key for the corresponding IP address 104.197.143.230
> STDERR: is unknown. This could either mean that
> STDERR: DNS SPOOFING is happening or the IP address for the host
> STDERR: and its host key have changed at the same time.
> STDERR: @@@
> STDERR: @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> STDERR: @@@
> STDERR: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> STDERR: Someone could be eavesdropping on you right now
> (man-in-the-middle attack)!
> STDERR: It is also possible that a host key has just been changed.
> STDERR: The fingerprint for the RSA key sent by the remote host is
> STDERR: SHA256:EKc2ZL+lJTCACVtZODKxeCJDuIecTw6r1kJXw9qN/Sg.
> STDERR: Please contact your system administrator.
> STDERR: Add correct host key in /home/mmarco/.ssh/known_hosts to get rid
> of this message.
> STDERR: Offending RSA key in /home/mmarco/.ssh/known_hosts:2
> STDERR: RSA host key for trac.sagemath.org has changed and you have
> requested strict checking.
> STDERR: Host key verification failed.
> STDERR: fatal: Could not read from remote repository.
> STDERR:
> STDERR: Please make sure you have the correct access rights
> STDERR: and the repository exists.
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
chris wuthrich wrote: > > Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem > compiling ntl 9.8.1. > > Not sure what to include. Just ask. Huh, dead old toolchain on a recent Intel machine. Update binutils (which include the GNU assember), or disable '-march=native' in NTL. (There's some 'configure' flag to NTL to not use it...) -leif P.S.: That's a known bug (NTL not checking whether the assembler can cope with GCC's output in case of '-march=native'), but this so far has hit us only on MacOS X. > Host system: > Linux pmlapsag01 2.6.32-642.1.1.el6.x86_64 #1 SMP Tue May 31 21:57:07 > UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > > C compiler: gcc > C compiler version: > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/home/sageadm/sage/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/lto-wrapper > Target: x86_64-unknown-linux-gnu > Configured with: ../src/configure --prefix=/home/sageadm/sage/local > --with-local-prefix=/home/sageadm/sage/local > --with-gmp=/home/sageadm/sage/local --with-mpfr=/home/sageadm/sage/local > --with-mpc=/home/sageadm/sage/local --with-system-zlib > --disable-multilib --disable-nls --enable-languages=c,c++,fortran > --disable-libitm > Thread model: posix > gcc version 4.9.3 (GCC) > > > Applying patches to NTL. > > > > config.status: executing libtool commands > > Configuring NTL. > * checking for libtool * > libtool (GNU libtool) 2.4.2 > Written by Gordon Matzigkeit < ... >, 1996 > > Copyright (C) 2011 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. > * libtool OK * > > *** checking -march=native flag > CXXAUTOFLAGS=" -march=native" > *** -march=native works > CXXAUTOFLAGS=" -march=native" > > [ntl-9.8.1.p0] Tuning and building NTL. > [ntl-9.8.1.p0] make[3]: Entering directory > `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' > [ntl-9.8.1.p0] make setup1 > [ntl-9..8.1.p0] make[4]: Entering directory > `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' > [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g -c MakeDescAux.c > [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g > -L/home/sageadm/sage/local/lib -Wl,-rpath,/home/sageadm/sage/local/lib > -o MakeDesc MakeDesc.c MakeDescAux.o -lm > [ntl-9.8.1.p0] /tmp/ccPRNw4z.s: Assembler messages: > [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:873: Error: no such instruction: `shlx > %r12,%rax,%rax' > [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:932: Error: no such instruction: `shlx > %r12,%rax,%rax' > > ... > > [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4374: Error: no such instruction: `shlx > %rax,%r15,%r15' > [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4791: Error: no such instruction: `shlx > %r13,%rdx,%rdx' > [ntl-9.8.1.p0] make[4]: *** [setup1] Error 1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
leif wrote: > chris wuthrich wrote: >> >> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem >> compiling ntl 9.8.1. >> >> Not sure what to include. Just ask. You may give us the output of 'as --version'. > Huh, dead old toolchain on a recent Intel machine. > > Update binutils (which include the GNU assember), or disable > '-march=native' in NTL. (There's some 'configure' flag to NTL to not > use it...) While you cannot pass options directly to NTL's 'configure' (without editing build/pkgs/ntl-*/spkg-install), you could for example do $ env SAGE_FAT_BINARY=yes ./sage -i ntl $ make # continue the build without "fat" binary enabled (I *thought* there was also an "experimental" binutils Sage package, but that doesn't seem to be the case, at least there isn't any on the official Sage mirrors.) > P.S.: That's a known bug (NTL not checking whether the assembler can > cope with GCC's output in case of '-march=native'), but this so far has > hit us only on MacOS X. Cf. https://trac.sagemath.org/ticket/20779#comment:4 ff. -leif >> Host system: >> Linux pmlapsag01 2.6.32-642.1.1.el6.x86_64 #1 SMP Tue May 31 21:57:07 >> UTC 2016 x86_64 x86_64 x86_64 GNU/Linux >> >> C compiler: gcc >> C compiler version: >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/home/sageadm/sage/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/lto-wrapper >> Target: x86_64-unknown-linux-gnu >> Configured with: ../src/configure --prefix=/home/sageadm/sage/local >> --with-local-prefix=/home/sageadm/sage/local >> --with-gmp=/home/sageadm/sage/local --with-mpfr=/home/sageadm/sage/local >> --with-mpc=/home/sageadm/sage/local --with-system-zlib >> --disable-multilib --disable-nls --enable-languages=c,c++,fortran >> --disable-libitm >> Thread model: posix >> gcc version 4.9.3 (GCC) >> >> >> Applying patches to NTL. >> >> >> >> config.status: executing libtool commands >> >> Configuring NTL. >> * checking for libtool * >> libtool (GNU libtool) 2.4.2 >> Written by Gordon Matzigkeit < ... >, 1996 >> >> Copyright (C) 2011 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. >> * libtool OK * >> >> *** checking -march=native flag >> CXXAUTOFLAGS=" -march=native" >> *** -march=native works >> CXXAUTOFLAGS=" -march=native" >> >> [ntl-9.8.1.p0] Tuning and building NTL. >> [ntl-9.8.1.p0] make[3]: Entering directory >> `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' >> [ntl-9.8.1.p0] make setup1 >> [ntl-9..8.1.p0] make[4]: Entering directory >> `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' >> [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g -c MakeDescAux.c >> [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g >> -L/home/sageadm/sage/local/lib -Wl,-rpath,/home/sageadm/sage/local/lib >> -o MakeDesc MakeDesc.c MakeDescAux.o -lm >> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s: Assembler messages: >> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:873: Error: no such instruction: `shlx >> %r12,%rax,%rax' >> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:932: Error: no such instruction: `shlx >> %r12,%rax,%rax' >> >> ... >> >> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4374: Error: no such instruction: `shlx >> %rax,%r15,%r15' >> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4791: Error: no such instruction: `shlx >> %r13,%rdx,%rdx' >> [ntl-9.8.1.p0] make[4]: *** [setup1] Error 1 > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
leif wrote: > leif wrote: >> chris wuthrich wrote: >>> >>> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem >>> compiling ntl 9.8.1. >>> >>> Not sure what to include. Just ask. > > You may give us the output of 'as --version'. P.P.S.: Maybe $ head -25 /proc/cpuinfo and perhaps $ ./sage --sh -c 'gcc -v -Q -march=native -c -x c /dev/null -o /dev/null' 2>&1 | grep ' -m' as well. -leif >> Huh, dead old toolchain on a recent Intel machine. >> >> Update binutils (which include the GNU assember), or disable >> '-march=native' in NTL. (There's some 'configure' flag to NTL to not >> use it...) > > While you cannot pass options directly to NTL's 'configure' (without > editing build/pkgs/ntl-*/spkg-install), you could for example do > > $ env SAGE_FAT_BINARY=yes ./sage -i ntl > $ make # continue the build without "fat" binary enabled > > > (I *thought* there was also an "experimental" binutils Sage package, but > that doesn't seem to be the case, at least there isn't any on the > official Sage mirrors.) > > >> P.S.: That's a known bug (NTL not checking whether the assembler can >> cope with GCC's output in case of '-march=native'), but this so far has >> hit us only on MacOS X. > > Cf. https://trac.sagemath.org/ticket/20779#comment:4 ff. > > > -leif > > >>> Host system: >>> Linux pmlapsag01 2.6.32-642.1.1.el6.x86_64 #1 SMP Tue May 31 21:57:07 >>> UTC 2016 x86_64 x86_64 x86_64 GNU/Linux >>> >>> C compiler: gcc >>> C compiler version: >>> Using built-in specs. >>> COLLECT_GCC=gcc >>> COLLECT_LTO_WRAPPER=/home/sageadm/sage/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/lto-wrapper >>> Target: x86_64-unknown-linux-gnu >>> Configured with: ../src/configure --prefix=/home/sageadm/sage/local >>> --with-local-prefix=/home/sageadm/sage/local >>> --with-gmp=/home/sageadm/sage/local --with-mpfr=/home/sageadm/sage/local >>> --with-mpc=/home/sageadm/sage/local --with-system-zlib >>> --disable-multilib --disable-nls --enable-languages=c,c++,fortran >>> --disable-libitm >>> Thread model: posix >>> gcc version 4.9.3 (GCC) >>> >>> >>> Applying patches to NTL. >>> >>> >>> >>> config.status: executing libtool commands >>> >>> Configuring NTL. >>> * checking for libtool * >>> libtool (GNU libtool) 2.4.2 >>> Written by Gordon Matzigkeit < ... >, 1996 >>> >>> Copyright (C) 2011 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. >>> * libtool OK * >>> >>> *** checking -march=native flag >>> CXXAUTOFLAGS=" -march=native" >>> *** -march=native works >>> CXXAUTOFLAGS=" -march=native" >>> >>> [ntl-9.8.1.p0] Tuning and building NTL. >>> [ntl-9.8.1.p0] make[3]: Entering directory >>> `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' >>> [ntl-9.8.1.p0] make setup1 >>> [ntl-9..8.1.p0] make[4]: Entering directory >>> `/home/sageadm/sage/local/var/tmp/sage/build/ntl-9.8.1.p0/src/ntl/src' >>> [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g -c MakeDescAux.c >>> [ntl-9.8.1.p0] g++ -I../include -I. -march=native -O2 -g >>> -L/home/sageadm/sage/local/lib -Wl,-rpath,/home/sageadm/sage/local/lib >>> -o MakeDesc MakeDesc.c MakeDescAux.o -lm >>> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s: Assembler messages: >>> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:873: Error: no such instruction: `shlx >>> %r12,%rax,%rax' >>> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:932: Error: no such instruction: `shlx >>> %r12,%rax,%rax' >>> >>> ... >>> >>> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4374: Error: no such instruction: `shlx >>> %rax,%r15,%r15' >>> [ntl-9.8.1.p0] /tmp/ccPRNw4z.s:4791: Error: no such instruction: `shlx >>> %r13,%rdx,%rdx' >>> [ntl-9.8.1.p0] make[4]: *** [setup1] Error 1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
Thanks a lot, leif, for the help. I will ask the sysadmin to update binutils. Your idea with SAGE_FAT_BINARY seems to get around the problem, by now. If it still helps for #20779: sageadm@pmlapsag01:~/sage$ as --version GNU assembler version 2.20.51.0.2-5.44.el6 20100205 Copyright 2009 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or later. This program has absolutely no warranty. This assembler was configured for a target of `x86_64-redhat-linux'. -- sageadm@pmlapsag01:~/sage$ head -25 /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 63 model name : Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz stepping: 2 microcode : 46 cpu MHz : 2593.993 cache size : 25600 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 15 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm ida arat epb xsaveopt pln pts dtherm fsgsbase bmi1 avx2 smep bmi2 invpcid bogomips: 5187.98 clflush size: 64 cache_alignment : 64 address sizes : 42 bits physical, 48 bits virtual power management: -- -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Did trac server change its rsa keys?
The key changed with the recent reinstall
On Tuesday, July 19, 2016 at 3:47:26 PM UTC+2, mmarco wrote:
>
> Trying to `git trac push` I get the following error message. Is it
> expected or someone is trying to MITM me?
>
> Traceback (most recent call last):
> File "/home/mmarco/git-trac-command/bin/git-trac", line 18, in
> cmdline.launch()
> File "/home/mmarco/git-trac-command/git_trac/cmdline.py", line 223, in
> launch
> app.push(ticket_number, remote=args.remote, force=args.force)
> File "/home/mmarco/git-trac-command/git_trac/app.py", line 216, in push
> self.repo.push(remote, force)
> File "/home/mmarco/git-trac-command/git_trac/git_repository.py", line
> 197, in push
> self.git.echo.push('trac', refspec)
> File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line
> 341, in meth
> return self.execute(git_cmd, *args, **kwds)
> File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line 98,
> in execute
> popen_stderr=subprocess.PIPE)
> File "/home/mmarco/git-trac-command/git_trac/git_interface.py", line
> 263, in _run
> raise GitError(result)
> git_trac.git_error.GitError: git returned with non-zero exit code (128)
> when executing "git push trac
> HEAD:refs/heads/u/mmarco/implement_zariski_vankampen_method_to_compute_fundamental_groups_of_complements_of_plane_curves_"
> STDERR: @@@
> STDERR: @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
> STDERR: @@@
> STDERR: The RSA host key for trac.sagemath.org has changed,
> STDERR: and the key for the corresponding IP address 104.197.143.230
> STDERR: is unknown. This could either mean that
> STDERR: DNS SPOOFING is happening or the IP address for the host
> STDERR: and its host key have changed at the same time.
> STDERR: @@@
> STDERR: @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> STDERR: @@@
> STDERR: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> STDERR: Someone could be eavesdropping on you right now
> (man-in-the-middle attack)!
> STDERR: It is also possible that a host key has just been changed.
> STDERR: The fingerprint for the RSA key sent by the remote host is
> STDERR: SHA256:EKc2ZL+lJTCACVtZODKxeCJDuIecTw6r1kJXw9qN/Sg.
> STDERR: Please contact your system administrator.
> STDERR: Add correct host key in /home/mmarco/.ssh/known_hosts to get
> rid of this message.
> STDERR: Offending RSA key in /home/mmarco/.ssh/known_hosts:2
> STDERR: RSA host key for trac.sagemath.org has changed and you have
> requested strict checking.
> STDERR: Host key verification failed.
> STDERR: fatal: Could not read from remote repository.
> STDERR:
> STDERR: Please make sure you have the correct access rights
> STDERR: and the repository exists.
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
On Tuesday, July 19, 2016 at 5:35:55 PM UTC+2, leif wrote: > > Huh, dead old toolchain on a recent Intel machine. > Centos/Redhat 6 is from 2010 and supported until 2020... If you want to get good performance for recent hardware you'd need something fresher, of course. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
chris wuthrich wrote: > > Thanks a lot, leif, for the help. > > I will ask the sysadmin to update binutils. Well, in this case Sage built and used its own GCC (currently 4.9.3) because at least /the default one/ on your system is outdated as well. You may ask the sysadmin whether already a newer version is available on your system (you could use for Sage by changing your PATH or setting CC, CPP, CXX and FC accordingly), and if not, ask him to install one (along with newer versions of its prerequisites such as GMP, MPFR, MPC, and other updated toolchain parts such as binutils) to be optionally used for performance reasons (and also e.g. C++11 support). The CPU is a "Haswell-EP" which supports (among other extensions) AVX2 and BMI2 (where "shlx" belongs to), so it's worth to use a more recent compiler on it, as Volker mentioned. -leif > Your idea with SAGE_FAT_BINARY seems to get around the problem, by now. > > If it still helps for #20779: > > sageadm@pmlapsag01:~/sage$ as --version > GNU assembler version 2.20.51.0.2-5.44.el6 20100205 > Copyright 2009 Free Software Foundation, Inc. > This program is free software; you may redistribute it under the terms of > the GNU General Public License version 3 or later. > This program has absolutely no warranty. > This assembler was configured for a target of `x86_64-redhat-linux'. > > > -- > sageadm@pmlapsag01:~/sage$ head -25 /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 63 > model name : Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz > stepping: 2 > microcode : 46 > cpu MHz : 2593.993 > cache size : 25600 KB > physical id : 0 > siblings: 2 > core id : 0 > cpu cores : 2 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 15 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx > pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts xtopology > tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni pclmulqdq ssse3 > fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes > xsave avx f16c rdrand hypervisor lahf_lm abm ida arat epb xsaveopt pln > pts dtherm fsgsbase bmi1 avx2 smep bmi2 invpcid > bogomips: 5187.98 > clflush size: 64 > cache_alignment : 64 > address sizes : 42 bits physical, 48 bits virtual > power management: > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Current best practice for LaTeX of function names
Ralf, I'm finally getting ready to add/standardize LaTeX names for special functions. I wanted to start with elliptic integrals but see that latex_name or _print_latex_ are already defined for all of them. The LaTeX formatting shows at the command line but does not get rendered in notebooks or SageMathCell. Since elliptic integrals are all BuiltinFunction, what would be blocking the rendering of LaTeX? On Wednesday, June 15, 2016 at 1:53:02 AM UTC-7, Ralf Stephan wrote: > > From reading source code, it appears that adding a keyword argument > latex_name to the function initialization is equivalent to defining a > _print_latex_ attribute for the function. There is also the option to > define a _latex_ attribute in addition to _print_latex_. > > Defining a _latex_() method of a Function class will only change the > output > if that function class itself is requested, e.g. > > sage: latex(cos) > mycos > > However, function *calls go through the symbolic/function.pyx machinery, > i.e., you > can use either latex_name in the __init__ or a _print_latex_() method, > but not both. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: error compiling ntl in sage 7.3.beta8
Just FYI - Tom Roby and I ran into this problem today trying to get 7.3.beta8 to build on OS X 10.9. So a fix before 7.3 is released would be good and appreciated. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags
I was running a small script on trac.sagemath.org:12000 that was listening for github pull requests and comments (via github webhooks) and publishing them to trac (via the trac scripts shipped with Sage). Nothing too fancy, but I can't find the code for it at the moment (but it's probably still sitting in that image unless it's been redone since then). I don't remember if I ever pushed anything back to github (which would require write access) but pull requests should get closed when their associated changes get merged into master. On Mon, Jul 18, 2016 at 2:00 PM, Paul Masson wrote: > Samuel, there are a couple pull requests from the middle of 2015 that never > became Trac tickets. The bot appears to have stopped creating tickets before > then. > > There are open pull requests from the end of 2014 that became part of Sage > 6.4. The bot does not appear to close pull requests on GitHub. > > The infrastructure wiki page lists Volker and Harald as the only admins for > GitHub. Are there any others who could close the ten or so open items ready > for closure in the Sage repository? If not, perhaps I'll bug Harald about > it. > > This may of course seem trivial to people, but if Sage is planning to move > to GitHub in the future then then it makes sense to begin addressing GitHub > maintenance more actively. > > > > On Monday, July 18, 2016 at 1:12:31 AM UTC-7, Samuel Lelievre wrote: >> >> There is a bot (called sageb0t) that turns pull requests on GitHub into >> trac tickets. >> >> It might be that the bot also closes pull requests when the corresponding >> tickets >> have been closed on trac and a new public release of Sage happens (github >> pull >> requests are typically against the master branch and public releases are >> when >> this branch gets updated). >> >> The bot is maintained by Robert Bradshaw, he might be able to comment >> more. >> See https://wiki.sagemath.org/Infrastructure >> >> >> Le dimanche 17 juillet 2016 23:06:37 UTC+2, Paul Masson a écrit : >>> >>> Thanks. >>> >>> Another question: who closes Issues and Pull Requests on Github that have >>> been marked ready for closure? >>> >>> On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote: done On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote: > > The mirror actually has three branches. This one hasn't been touched in > over a year: > > https://github.com/sagemath/sage/tree/module-list-cleanup > > Shouldn't it be removed at some point? > > On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote: >> >> The mirror at >> >> https://github.com/sagemath/sage >> >> has only two branches, develop and master. Versions seem to be kept >> as tags. >> >> However, editing sage.yaml of binary-pkg >> >> https://github.com/sagemath/binary-pkg >> >> does not work for tags. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Current best practice for LaTeX of function names
Paul, please open a ticket and Cc: me. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
