you'd only need to do
git trac config --user USERNAME --pass 'PASSWORD'
once, and it will store the data somewhere...
Somewhere...?!
I wouldn't recommend anyone to use that feature; it's IMHO odd it's even
there.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cur
Simon King wrote:
Why am I asked for my trac password when I just pull? Shouldn't a
password only be required for pushing, but not for pulling?
Depends on the configured protocol (I think); git://... vs. ssh://git@...
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
-
François Bissey wrote:
On Thu, 01 May 2014 23:06:53 leif wrote:
François Bissey wrote:
On Thu, 01 May 2014 22:58:47 leif wrote:
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Using configure is certai
François Bissey wrote:
On Thu, 01 May 2014 22:58:47 leif wrote:
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Using configure is certainly a good option. +1, I like it.
Sage's top-level 'co
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-de
ning /{print
substr($3,2,length($3)-2)}'
/usr/local/lib/pkgconfig
/usr/lib/pkgconfig
/usr/share/pkgconfig
-leif
On 2/05/2014, at 5:38, William Stein wrote:
Hi,
I just spent a while trying to figure out how to get R png graphics to
work again in Sage-6.2rc0 on Ubuntu 14.04. Note th
ng to the /state of the ticket/)?
Just asking...
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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
been released).
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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...@g
John H Palmieri wrote:
On Tuesday, April 29, 2014 6:20:25 PM UTC-7, John H Palmieri wrote:
On Tuesday, April 29, 2014 4:45:35 PM UTC-7, leif wrote:
leif wrote:
> Volker Braun wrote:
>> there is no separate spkg in sage >= 6, its is an optional
leif wrote:
Volker Braun wrote:
there is no separate spkg in sage >= 6, its is an optional pkg but lives
in the git tree.
But the first error seems to be that $SAGE_ROOT/upstream/ doesn't exist
(because it's a binary distribution of Sage I guess), and after that
error, sage-spkg
ds the legacy TOPCOM spkg, and attempts to
install that.
Oskar, you may try to delete the TOPCOM *spkg* in
/Applications/sage/upstream/, and instead place
http://www.sagemath.org/packages/upstream/topcom/topcom-0.17.4.tar.bz2
there.
Afterwards retry 'sage -i topcom'.
-leif
On Tu
seful) "Merged:"
field filled.
Similar for the changelog entries in SPKG.txt files; they provide[d]
different (namely usually higher-level), and easier to access
information than commit logs (and diffs) do.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received t
could take hours,
fail, and render your Sage install useless!!
We don't recommend, but we also don't prevent people from running
os.system("sage -b") or os.system("make") from the Sage prompt.
-leif
On Sunday, April 27, 2014 10:42:36 PM UTC+1, Willia
t we should probably just require HOME to be set *unless*
DOT_SAGE is already set.
(Using Sage shouldn't need $HOME, while building Sage might still, e.g.
ECL by default wanted to look into $HOME when building Maxima, because
we [used to] run it without '--norc'...)
-leif
--
()
Jan Groenewald wrote:
Do you have a URL for me of the bug / fixes?
https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/968766
https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/972648
-leif
On 20 April 2014 16:26, leif mailto:not.rea...@online.de>> wrote:
Jan Groenewald
Jean-Pierre Flori wrote:
On Tuesday, April 22, 2014 5:42:44 PM UTC+2, leif wrote:
>> (Release of 4.9.0 is scheduled for Tuesday, so we'll presumably
face it
>> soon in some distros.)
I'm updating an Ubuntu LTS and it seems gcc 4.9 is shipped with it (I
did n
leif wrote:
leif wrote:
Is there already a ticket for issues with GCC 4.9?
I think I'll open a (small) metaticket soon.
Did so: http://trac.sagemath.org/ticket/16208
Although it's (currently) not a metaticket; I also haven't pushed the
patches yet, but will do so soon.
B
ces/ (7) is
the limiting factor.
-leif
2014-04-22 12:56 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>:
Hello Miguel,
If you need support in Sage you should use the sage-support
googlegroups or ask.sagemath.org. The sage-devel mailing list is about
development and bug re
leif wrote:
Is there already a ticket for issues with GCC 4.9?
I think I'll open a (small) metaticket soon.
(Release of 4.9.0 is scheduled for Tuesday, so we'll presumably face it
soon in some distros.)
Depending on when Sage 6.2 gets released, we may also release some 6.1.2
esting, it would presumably be best to just (try to) install Sage
from the PPA onto a *virgin* Tahr (and/or Pangolin etc.) [picture
that!], and optionally run the full test suite, or just play with it.
-leif
On 21 April 2014 11:28, leif mailto:not.rea...@online.de>> wrote:
Jan
Jan Groenewald wrote:
I am suprised at these not being contained in sage:
Ahem, run that from within a Sage subshell?
(We don't set DT_RUNPATH, but currently rely on sage-env setting up
LD_LIBRARY_PATH appropriately.)
0 root@kontiki:/usr/lib/sagemath/local/bin#for i in *; do ldd $i | egrep
Jan Groenewald wrote:
On 20 April 2014 14:50, leif mailto:not.rea...@online.de>> wrote:
P.S.: Beat the Ubuntu guys for not releasing fixed versions of
Ubuntu/Linaro GCC 4.6.3 for Precise. (They still ship the broken
1ubuntu5 IIRC, although the fixes had been there two yea
ken w.r.t. '-O3' and
AMD's XOP instructions, but that's a different story.)
More to come...
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To uns
Jan Groenewald wrote:
On 19 April 2014 17:15, leif mailto:not.rea...@online.de>> wrote:
Depends: build-essential, gfortran [probably also m4]
Are build-essential and m4 not only from-source build dependencies? I
would maybe move them to Suggests: Is there runtime functionality, a
fu
. not installed
Type 'sage -i package_name' to download and install a package.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
Kannappan Sampath wrote:
On Apr 19, 2014, at 11:17 PM, leif wrote:
Kannappan Sampath wrote:
Hah, nice catch! I did not try either of them and that helps find out more:
Apples-MacBook-Pro:~ apple$ sage --kash
/Users/apple/sage/local/bin/kash: line 4: ./kash3: Bad CPU type in
executable
I
leif wrote:
Kannappan Sampath wrote:
Apples-MacBook-Pro:~ apple$ sage --kash
/Users/apple/sage/local/bin/kash: line 4: ./kash3: Bad CPU type in
executable
I get the above. I am using Sage Version 6.2.beta7, Release Date:
2014-04-08.
So, how do I proceed with this one.
Replace the CPU?
(No
-08.
So, how do I proceed with this one.
Replace the CPU?
(No idea. Probably upload the build log of the kash spkg somewhere,
such that the Darwinists can take a look at.)
I also don't know how to solve (or avoid) the precision error PARI
throws (once kash works).
-leif
On Apr 19,
n other
distros like Arch Linux and OpenSuSE).
-leif
Where Depends is strict, to even start the program, while Recommends is
for all but outlier cases, e.g. a lot of functionality could be broken,
all usual installations come with those, and Suggests is for what many
people would use with it.
Ca
sh3-2008-07-31.p0']
Did you check whether
$ ./sage --kash
and
sage: from sage.interfaces.all import kash
work?
(And btw., which version of Sage are you using?)
-leif
P.S.:
sage: K.galois_group('gap')
Galois group Transitive group number 9 of degree 13 of the Numb
bviously isn't taken care of
everywhere.
-leif
salvus@salvus-base: ~ salvus@salvus-base:~$ sage -f database_gap
Found local metadata for database_gap-4.7.4
Found local sources at
/usr/local/sage/sage-6.2.beta8/upstream/database_gap-4.7.4.tar.bz2
Checksum: 6e5f63df55881
leif wrote:
Jeroen Demeyer wrote:
On 2014-04-12 18:08, Simon King wrote:
So, is rm -rf "$SAGE_LOCAL/lib/python/site-packages/SQLAlchemy*"
the wrong thing to do, i.e., a bug?
Yes, it is wrong, the * in the quotes will not be expanded.
And that's in Sage's original spkg-i
should at least fix that.
Sorry for blindly copy-pasting the broken 'rm' line, didn't notice at
all... m)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" g
Simon King wrote:
How can I get the checksum.ini file right?
./sage --sh -c sage-fix-pkg-checksums
(May take a while; so you may take a look at
$SAGE_ROOT/src/bin/sage-fix-pkg-checksums and just do what's done there
for sqlalchemy-0.9.4 ... ;-) )
-leif
--
() The ASCII Ribbon Cam
ust do what Sage's spkg-install does, namely
rm -rf "$SAGE_LOCAL/lib/python/site-packages/SQLAlchemy*"
before installing SQLAlchemy 0.9.4 from a Sage subshell, as you did
before. But that way you might end up with again Sage's old version if
you later upgrade other parts of
leif wrote:
On 10.04.2014 04:03, 张彪 wrote:
I follow the steps in the "Git the Hard Way" of
http://www.sagemath.org/doc/developer/manual_git.html.
but an Error occurs.
--
My computer and operating system:
4 Intel(R) Core(TM) i5-3470S CPU
Dima Pasechnik wrote:
On 2014-04-10, leif wrote:
[...]
Yep, it doesn't "figure it out", it hardcodes 'libtool' on Darwin:
ix86Mac-darwin)
AC_CHECK_LIB(dl, dlopen)
if test "$ac_cv_lib_dl_dlopen" = yes; then
leif wrote:
leif wrote:
Volker Braun wrote:
It builds fine on bsd with 10.6. Maybe you need to update your XCode?
I guess his libtool in PATH is simply not Apple's...
So presumably an upstream bug.
P.S.: From Singular's spkg-install:
if [ "$UNAME" = "Darwin
leif wrote:
Volker Braun wrote:
It builds fine on bsd with 10.6. Maybe you need to update your XCode?
I guess his libtool in PATH is simply not Apple's...
So presumably an upstream bug.
P.S.: From Singular's spkg-install:
if [ "$UNAME" = "Darwin" ]; then
Volker Braun wrote:
It builds fine on bsd with 10.6. Maybe you need to update your XCode?
I guess his libtool in PATH is simply not Apple's...
So presumably an upstream bug.
-leif
On Thursday, April 10, 2014 3:04:37 PM UTC+2, Dima Pasechnik wrote:
I am stuck on singular on OSX 1
services using OpenSSL.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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-deve
et another instance of "Sage's readline breaks programs linked to a
newer system libreadline"?
(If so, we'd have to once again update the "logic" in readline's
spkg-install. Or finally make readline a prerequisite...)
-leif
real
older releases which still use 0.9.x versions aren't
affected.
-leif
[1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel&
7;,\` .section
__DATA,__const')"],POST)
OBJECT_FORMAT="-f macho64" ;;
*-w64-mingw*|*-*-cygwin*)
OBJECT_FORMAT="-f x64" ;;
-leif
On 6 April 2014 18:03, leif mailto:not.rea...@online.de>> wrote:
leif wrote:
Ok,
leif wrote:
Ok, here's minimalist's quick'n'dirty temporary solution;
minimally-invasive in that it touches only one file and affects only
Darwin x86_64 :-) :
--- mpir-2.7.0-alpha2/configure.ac
+++ mpir-2.7.0-alpha2/configure.ac
@@ -2843,15 +2843,18 @@
leif wrote:
leif wrote:
Bill Hart wrote:
I don't know how to fix that.
The line in question is:
.section .data.rel.ro.local,"aw",@progbits
Ahem, that's an *ELF* section name (along with its attributes)...
It is complaining that .data.rel.ro.local is too lo
leif wrote:
Bill Hart wrote:
I don't know how to fix that.
The line in question is:
.section .data.rel.ro.local,"aw",@progbits
Ahem, that's an *ELF* section name (along with its attributes)...
It is complaining that .data.rel.ro.local is too long.
Yeah,
by past versions of their assembler!
It probably should be reported as a bug to the binutils people, since it
is going to stop a lot of code compiling on Macs. The linker hint should
have been chosen with a shorter name.
Well, if at all, to Apple... B)
-leif
On 5 April 2014 23:14, leif mailt
CXX="g++"
CXXFLAGS="-m64 -O2 -march=core2 -mtune=core2"
MPN_PATH=" x86_64/nehalem/westmere x86_64/nehalem x86_64 generic"
(This is bsd.math at UW; [vanilla] MPIR 2.6.0 passed 'make check'
(without --enable-cxx) with this configuration.)
alphas unpack into mpir-2.7.0/ . And the HTML links for
alpha2 refer to the alpha1... ;-) [Shouldn't make a difference on
systems other than Windows though, I guess, and for those there's a zip
file without an HTML link.]
-leif
Cygwin/MinGW/Cygwin64/MinGW64:
wget http://mpir.org/m
Dox wrote:
I could try to change something... However, What is the way to provide a
patch? Is it through github?
http://sagemath.org/doc/developer/walk_through.html#submitting-a-change
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you
makes me wonder whether being neighbouring is
(ir)reflexive...
(Some of my alter egos agree, while some of course don't, depending on
whether they know each other and/or themselves.)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because yo
leif wrote:
Emmanuel Charpentier wrote:
Trying to compile sage on an old laptop (Toshiba Core2 + 2 Gb RAM +
Debian testing). I'm compiling with MAKE="make -j2 -l 3". End of the
(second attempt to) compilation :
ular compilation log, but I cant join
them now (the damn "attach files" dialog doesn't appear in my Google page,
probably because I just joined this group...).
Any pointers ?
That's an upstream bug, see #14737 (preliminary .p8 spkg available there).
-leif
--
() The ASC
ecially it doesn't break *building* Sage.
(Besides that, the cause of the error is pretty obvious I think -- in
contrast to the PPL issue.)
-leif
On Monday, June 24, 2013 10:36:54 AM UTC-4, leif wrote:
And the only other spkg that frequently causes trouble (although
recently much le
used if present and recent enough).
-leif
On Monday, June 24, 2013 9:53:34 AM UTC-4, leif wrote:
The PPL spkg should really make sure it doesn't break (the system-wide)
GCC before installing its libraries... (and perhaps otherwise create
symlinks to the system-wide PPL libs
the system-wide)
GCC before installing its libraries... (and perhaps otherwise create
symlinks to the system-wide PPL libs; not sure whether the headers would
be compatible, i.e., if Sage's could be used in case ppl-devel isn't
installed).
-leif
On Monday, June 24, 2013 7:3
ost the "config.log"?
Yes, please... ;-)
(/home/phantogom/sage-5.10/spkg/build/pynac-0.2.6/src/config.log)
-leif
> Found package pynac-0.2.6 in spkg/standard/pynac-0.2.6.spkg
> pynac-0.2.6
>
> Extracting package /home/ph
for the sake of no trailing whitespace, there's none.
Well, one trailing blank is actually part of the prompt of the empty
continuation line, so you presumably shouldn't remove it.
Or did I get you wrong?
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You rec
[1] such reports end up on is meanwhile linked
to from the Sage trac wiki page though.)
-leif
[1] http://spreadsheets.google.com/pub?key=pCwvGVwSMxTzT6E2xNdo5fA
(It seems we even get error reports for the *other* Sage software there!
XD )
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
grats!
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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.
/issue17843
quote: "Apparently the file triggers a warning in several anti virus
programs because it looks like a zip bomb."
Can we update to python 2.7.5? That would fix this problem:
http://www.python.org/download/releases/2.7.5/
That's #14600, merged into Sage 5.11.bet
leif wrote:
Keshav Kini wrote:
Stefan writes:
I'd ask for p[6:], that's the expected use and consistent with the
previous line which tests for '... ' (note the space).
I agree with that - I was just miming the .lstrip() after 'sage:' found
in previous li
Keshav Kini wrote:
Stefan writes:
I'd ask for p[6:], that's the expected use and consistent with the previous
line which tests for '... ' (note the space).
I agree with that - I was just miming the .lstrip() after 'sage:' found
in previous lines. I'll f
kcrisman wrote:
The shrillness level has gotten a
little higher than really necessary, certainly than customary on this list.
We haven't seen illustrations of the effect of the @bushy_tail
decorators yet... :P
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
-
Volker Braun wrote:
Right now there is not really anything, thats a question of
what the find_stat roadmap is.
But I don't see a need for that unless there
is any need for it.
+1
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because yo
available / listed in the "experimental"
category.]
Or maybe (haven't looked at it yet) it violates the conventions for
spkgs (in that it modifies the Sage library)?
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you ar
tions, too.)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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...@googlegr
ing Sage's toolchain failed (unless perhaps
'-k' was given to 'make').
-leif
On Sunday, June 16, 2013 8:02:33 AM UTC-4, Wai Man Chung wrote:
Dear all,
I am building Sage 5.9 from source code
mmarco wrote:
Thanks, that seems to work.
sudo -u mmarco update {wiki,faq,Installation_Guide,...}
-leif
On 12 jun, 04:02, "Nicolas M. Thiery"
wrote:
On Sat, Jun 08, 2013 at 03:54:58AM -0700, mmarco wrote:
I tried to do that, and it gives some problems.
I don't know wh
.c:13:
../factory/cf_gmp.h:2501:28: fatal error: bits/c++config.h: No such file
or directory
#include
^
compilation terminated.
make[4]: *** [weight0.o] Error 1
This is an upstream Singular bug; see #14737 [1].
-leif
[1] http://trac.sagemath.org/sage_trac/ticket
table 5.7, or
5.9.beta4+) version to upgrade from.
But the final 5.10 will (hopefully) get out soon anyway (although you
could upgrade from 5.10.rc1, say, later, too).
I'd recommend building 5.10.rc1 from scratch (and upgrading /that/
later) though... ;-)
-leif
--
() The ASCII Ribbo
leif wrote:
leif wrote:
leif wrote:
Looks like reinstalling the Sage library spkg would meanwhile also
trigger the rebuild of *all* extension modules; not sure since when
though... (seen with Sage 5.10.beta5 at least)
Yep. This is because #14570, merged into Sage 5.10.beta4, completely
leif wrote:
leif wrote:
Looks like reinstalling the Sage library spkg would meanwhile also
trigger the rebuild of *all* extension modules; not sure since when
though... (seen with Sage 5.10.beta5 at least)
Yep. This is because #14570, merged into Sage 5.10.beta4, completely
breaks sage-sync
(i.e., shipping links to
*system* libraries, or including /some/ version).
-leif
The current answers look more like the usual "No, because it's different
from what we do now!" than like a technical discussion...
Snark on #sagemath
--
() The ASCII Ribbon Campaign
/\ Hel
leif wrote:
leif wrote:
leif wrote:
Ursula Whitcher wrote:
...
gcc -std=gnu99 -shared -fopenmp -o libR.so CConverters.o
CommandLineArgs.o Rdynload.o Renviron.o RNG.o agrep.o apply.o
arithmetic.o array.o attrib.o base.o bind.o builtin.o character.o
coerce.o colors.o complex.o connections.o
and a trivial patch to the Sage
library).
-leif
[1] http://trac.sagemath.org/sage_trac/ticket/14706
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
Volker Braun wrote:
On Saturday, June 8, 2013 6:31:40 PM UTC+1, leif wrote:
... which isn't tuned for the specific machine.
au contraire, full tuned. Of course using some pre-tuned values, for
which you need a recent enough Core i7.
So you're saying they're shipping
are different
implementations / libraries only work (or worked, tried that a while
ago) with *static* ATLAS libraries.
The ATLAS documentation (or website at least) is a mess as well, so I'm
unable to provide links here.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You re
Volker Braun wrote:
On Saturday, June 8, 2013 5:23:57 PM UTC+1, leif wrote:
Btw., there's still not even a script to save the once built [shared]
ATLAS libraries for use by another Sage installation.
And such a script would be totally pointless if there were static
libraries flo
a script to save the once built [shared]
ATLAS libraries for use by another Sage installation.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
TERM setting.
-leif
This makes the
pexpect interface fail.
On 7 jun, 16:41, leif wrote:
mmarco wrote:
On a different (but related) subject: is it possible to interface
instances of Maple/Mathematica/etc on a different machine through ssh?
That /should/ transparently work if you just cre
lso
reuse parts of the patchbot code.]
> Or if this was a feature that more than one person would use, someone
> could write a checker and mailer into the post-receive hook in trac's
> repo.
Well, I will probably use it a lot, so why not implementing it too ? :-)
A server-side solut
@host -c
program_name' (for each of the programs you want to use remotely).
-leif
It would be a good thing to have, for example, for people using the
virtualbox appliance, but have these programs installed on their host
machine.
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Ma
would be a cool feature
That shouldn't be too hard to implement (I'm not volunteering though).
On the other hand, you currently don't even get a notification when
someone adds/changes an attachment to a ticket you're already cc'ed
on... ;-)
-leif
P.S.: An
What is this file (for), where does it originate from, do we still need it?
It's in .hgignore, and dates back to July 9th 2012.
Cf. http://trac.sagemath.org/sage_trac/ticket/13245#comment:19 .
Thanks,
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received
John Cremona wrote:
On 6 June 2013 15:28, leif wrote:
John Cremona wrote:
While reviewing #13591 I noticed that two functions on point on
elliptic curves over number fields are spelled incorrectly:
schemes/elliptic_curves/ell_point.py:2600:def
archimedian_local_height(self
issues...
The most prominent perhaps being Möbius, where we have moebius (correct)
as well as mobius, both with many more occurrences than archimedian.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Grou
leif wrote:
leif wrote:
Ursula Whitcher wrote:
...
gcc -std=gnu99 -shared -fopenmp -o libR.so CConverters.o
CommandLineArgs.o Rdynload.o Renviron.o RNG.o agrep.o apply.o
arithmetic.o array.o attrib.o base.o bind.o builtin.o character.o
coerce.o colors.o complex.o connections.o context.o
leif wrote:
Ursula Whitcher wrote:
...
gcc -std=gnu99 -shared -fopenmp -o libR.so CConverters.o
CommandLineArgs.o Rdynload.o Renviron.o RNG.o agrep.o apply.o
arithmetic.o array.o attrib.o base.o bind.o builtin.o character.o
coerce.o colors.o complex.o connections.o context.o cov.o cum.o dcf.o
FLAGS="-L/home/whitchua/sage-5.10.rc0/local/lib" ./sage -i
spkg/standard/r-2.15.2.p2.spkg
and if that worked, resume the normal build with
$ make
(Or before reissuing 'make' / 'sage -i ...', do e.g. 'export MAKE="make
-j8"' to speed up things
Jeff wrote:
Tried a 3 GB swap file, same error. I will wait for the official release
of 5.10. Thanks for the suggestions though.
Note that you could [try to] build 5.10.rc0 now, and when the final gets
out, simply run 'sage --upgrade' (which shouldn't involve much rebuil
pparently not building in parallel, which requires
exporting MAKE='make -jN', N the max. number of jobs.)
On the bright side, I haven't had any ATLAS errors yet!
On the other hand, we have no idea [yet] what went wrong in the first
place... ;-)
Out of curiosity: What does
Volker Braun wrote:
For the record, the end of install.log is exactly the same excluding the
"tee: write error".
On Tuesday, June 4, 2013 12:45:32 AM UTC+1, leif wrote:
Cosmic ray?
I just re-ran the whole build and got it again
Weird. Did you change anything w.r.t. previ
s NTL is a standard spkg, it would be nice to skip the step "gf2x is an
optional spkg (and we provide an optional NTL spkg using it)".
Just for the record:
There's a new NTL spkg (only fixing hardcoded 'make') at
http://trac.sagemath.org/sage_trac/ticket/14692
(Curr
leif wrote:
Jeroen Demeyer wrote:
Just for information, these packages still use make instead of $MAKE:
- atlas (upstream all over the place)
- boehm_gc (in spkg-install)
- cliquer (in spkg-install)
- iml (in spkg-install, #748)
- ntl (upstream)
Fixed NTL spkg coming soon (#14692). (Now
/home/release/sage-5.10.rc0/sage-5.10.rc0.tar
tar xf sage-5.10.rc0.tar
cd sage-5.10.rc0
make
If you just want the new ATLAS spkg:
$ ./sage -i
http://boxen.math.washington.edu/home/release/sage-5.10.rc0/sage-5.10.rc0/spkg/standard/atlas-3.10.1.p0.spkg
$ make
-leif
--
() The ASCII Ribbon Cam
.log
The file appears to be truncated (although about 19 MB); the interesting
parts should be at the end...
You may try reinstalling ATLAS with SAGE_ATLAS_ARCH=fast or
SAGE_ATLAS_ARCH=base though (see [1]), i.e.
$ export SAGE_ATLAS_ARCH=...
$ make
-leif
[1] http://sagemath.org/d
h it but I will try it today.
If you're not compiling a sage with a very recent libm4rie, 1GB+0.5GB
will *not* be enough.
Let me remind you what Leif wrote earlier: M4RIE got upgraded in Sage
5.10.beta1.
Unfortunately the new spkg at
http://trac.sagemath.org/sage_trac/ticket/14336 also need
nux ppc64) I get one failure (not
noise?!) with GCC 4.6.3 (but not 4.3.4):
make[2]: Entering directory
`/home/leif/src/gsl-1.15.90-build.silius-gcc-4.6.3/poly'
FAIL: z1.real, 15th-order polynomial (-1.00044 observed vs 1
expected) [159]
FAIL: z2.real, 15th-order polynomial (1.
501 - 600 of 1271 matches
Mail list logo
