> Sure, that cannot hurt.
Well, it's now #15787.
http://trac.sagemath.org/ticket/15787
Nathann
--
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+un
On Wednesday, February 5, 2014 12:32:56 PM UTC+1, Nathann Cohen wrote:
>
> > Those are the multi-threaded (pthread) versions. It is preferable if you
> > have them, though we can of course just work with the single-threaded
> > version.
>
> Oh. I see. Do I patch the manual then ?
>
Sure, that
> Those are the multi-threaded (pthread) versions. It is preferable if you
> have them, though we can of course just work with the single-threaded
> version.
Oh. I see. Do I patch the manual then ?
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-relea
Those are the multi-threaded (pthread) versions. It is preferable if you
have them, though we can of course just work with the single-threaded
version.
On Wednesday, February 5, 2014 11:15:16 AM UTC, Nathann Cohen wrote:
>
> > "make" doesn't know about changed environment variables, so you eith
> "make" doesn't know about changed environment variables, so you either
> recompile from scratch or keep using your current install.
Okayokay. Then what do we do with the manual ? Do you also think that
we can remove "libptf77blas" and "libptcblas" from the list of files
needed by atlas ?
Nathan
"make" doesn't know about changed environment variables, so you either
recompile from scratch or keep using your current install.
On Wednesday, February 5, 2014 10:59:55 AM UTC, Nathann Cohen wrote:
>
> > If SAGE_ATLAS_LIB is set then we don't compile atlas. If the system
> atlas
> > libraries
> If SAGE_ATLAS_LIB is set then we don't compile atlas. If the system atlas
> libraries don't work then you'll get an error later on, of course.
Okay... Would "make" be enough to have Sage notice that a
different Atlas is to be used and that everything now has to be
recompiled with the new one
If SAGE_ATLAS_LIB is set then we don't compile atlas. If the system atlas
libraries don't work then you'll get an error later on, of course.
On Wednesday, February 5, 2014 10:52:11 AM UTC, Nathann Cohen wrote:
>
> > I'd say [1] is wrong and the *pt* files are optional.
> > For sure the debian l
> I'd say [1] is wrong and the *pt* files are optional.
> For sure the debian libatlas-base-dev (approximate name) is enough.
Oh. Is there a way for me to test that Sage uses debian's files
without any problem and does not build its own atlas again ? Ideally
without rebuilding all of Sage :-P
If
On Wednesday, February 5, 2014 11:46:23 AM UTC+1, Nathann Cohen wrote:
>
> > Atlas compile time mostly depends on whether atlas has pre-computed
> defaults
> > for your cpu, not so much on the CPU speed. If it bothers you, use the
> > SAGE_ATLAS_LIB environment variable to use a system/previou
> Atlas compile time mostly depends on whether atlas has pre-computed defaults
> for your cpu, not so much on the CPU speed. If it bothers you, use the
> SAGE_ATLAS_LIB environment variable to use a system/previously-compiled
> library
HMmm Looks like debian's packages do not contain the
"libp
Atlas compile time mostly depends on whether atlas has pre-computed
defaults for your cpu, not so much on the CPU speed. If it bothers you, use
the SAGE_ATLAS_LIB environment variable to use a system/previously-compiled
library
On Tuesday, February 4, 2014 8:05:36 PM UTC, Emmanuel Charpentier
I tried installing "the classic way", i. e. from the tarball (as mirrored
at Paris-VI university).
On a "big laptom" (Core i7, 16 GB RAM) under Debian testing, a parallel
compilation (export MAKE="make -j8 -l10" ; time make ssl) t took almost 4
hours :
real215m37.165s
user369m27.220s
sy
On 2014-02-03 12:57, Volker Braun wrote:
--author='Release Manager'
OK, I will add this option.
--
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+un
So... is the release script not being used any more to at least add to the
release log? "So and so many new contributors" etc? This would be really
really unfortunate, and I think Jeroen even put his script in a public
place it could easily be used by someone knowledgeable about release
manag
On Monday, February 3, 2014 12:04:58 PM UTC, John Cremona wrote:
>
> I deleted all of src/doc/output and re-made, and the problem went away.
>
You can also "make doc-clean"
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from t
On 3 February 2014 09:42, John Cremona wrote:
> After pulling the latest develop commits from trac and doing make, I
> get errors building the docs, starting at
>
>
> [combinat ] /home/jec/sage/src/doc/en/reference/combinat/algebra.rst:4:
> WARNING: toctree contains reference to nonexisting docume
In b554827a94872c3e62cd7311c22e28d38e635ffc Travis started a new branch on
top of a rebased tree, or the master tree was yanked from under his feet.
In any case, it shouldn't happen again but there is no point in beating
yourself up over mistakes that were made.
On Monday, February 3, 2014 9:51
On 2014-02-02 23:18, Harald Schilly wrote:
Are there already somewhere the release notes? And if not, does anybody
have an idea where the script for creating it is?
There are some issues, both of them causing extra tickets to appear in
the changelog:
1) There are duplicate commits for variou
After pulling the latest develop commits from trac and doing make, I
get errors building the docs, starting at
[combinat ] /home/jec/sage/src/doc/en/reference/combinat/algebra.rst:4:
WARNING: toctree contains reference to nonexisting document
u'sage/combinat/free_module'
How should I fix that?
Are there already somewhere the release notes? And if not, does anybody
have an idea where the script for creating it is?
Harald
--
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,
All binary builds are now finished.
Harald: please mirror...
--
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
Thanks for all the comments. Until we have dealt with the issue of
moving after building, I'll just build from scratch.
John
On 31 January 2014 11:19, Dima Pasechnik wrote:
> On 2014-01-31, John Cremona wrote:
>> Good! Now here is a question I have been waiting to ask:
>>
>> We know know that
Most binaries are now at
http://boxen.math.washington.edu/home/buildbot/binaries/, two more to come.
--
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-releas
I would just build /usr/local/sage-x.y.z and then switch the symlink. That
way you can also have multiple old Sage versions around if you want to. You
can share the upstream folder if you make it a symlink to a common
directory.
On Friday, January 31, 2014 9:15:55 AM UTC, John Cremona wrote:
>
On 2014-01-31, John Cremona wrote:
> Good! Now here is a question I have been waiting to ask:
>
> We know know that it is Not A Good Idea to build Sage in one place and
> move it, so when I install Sage system-wode on the machines I
> administer, which I only do for full releases (not betas etc),
Good! Now here is a question I have been waiting to ask:
We know know that it is Not A Good Idea to build Sage in one place and
move it, so when I install Sage system-wode on the machines I
administer, which I only do for full releases (not betas etc), I have
been building it where I want it (in
On Thu, Jan 30, 2014 at 10:08 PM, Volker Braun wrote:
> Source tarball is here (to be uploaded to the mirrors):
Cool! I've already started to move it to the mirrors.
Harald
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from t
28 matches
Mail list logo
