Re: [sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Erik Massop
On Tue, 24 Dec 2013 05:04:24 -0800 (PST) Emil Widmann wrote: ... > Additional examples what base means for the most common > architectures would be terrific! ... Additionally there could maybe be a reference to the code, as examples will get outdated. In this case that would be configure_base i

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Volker Braun
Feel free to change it ;-) On Tuesday, December 24, 2013 1:04:24 PM UTC, Emil Widmann wrote: > > http://sagemath.org/doc/installation/source.html#environment-variables > Maybe it is possible to mention this in the docs (SAGE_FAT_BINARIES and > SAGE_ATLAS_ARCH are exclusive) and that SAGE_FAT_BINA

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Emil Widmann
I'd say the working definition of SAGE_FAT_BINARY is "made within the last 10 years". In particular, it implies SAGE_ATLAS_ARCH=base, which is the slowest "generic" target. You can build even slower ones on certain architectures. There is no way to build Sage on every x86 cpu, that would incl

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Volker Braun
On Tuesday, December 24, 2013 8:01:54 AM UTC, Emil Widmann wrote: > > Why is it entirely wrong to set SAGE_ATLAS_ARCH to the empty string > It is not a valid setting. Allowed values are SAGE_ATLAS_ARCH=[threads:n,][static,]arch[,isaext1][,isaext2]...[,isaextN] So if you set it at all then arch i

Re: [sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Volker Braun
I'd say the working definition of SAGE_FAT_BINARY is "made within the last 10 years". In particular, it implies SAGE_ATLAS_ARCH=base, which is the slowest "generic" target. You can build even slower ones on certain architectures. There is no way to build Sage on every x86 cpu, that would incl

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Emil Widmann
Am Montag, 23. Dezember 2013 22:39:21 UTC schrieb Volker Braun: > > Also, fortran is a build-time dependency (but not runtime). You either > install your distro's fortran, or you compile gcc (which includes fortran). > You did both. > OK, this is clear in hindsight, and after reading the documen

Re: [sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Jeroen Demeyer
On 2013-12-24 09:01, Emil Widmann wrote: May I still ask what is "generic" and which processor will be the minimum on the x86 scale that will be supportet with SAGE_FAT_BINARIES? It is SAGE_FAT_BINARY=yes and it should in theory work with all x86 processors, although it's hard to test whether th

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-24 Thread Emil Widmann
Am Montag, 23. Dezember 2013 22:36:34 UTC schrieb Volker Braun: > > On Monday, December 23, 2013 10:07:12 PM UTC, Emil Widmann wrote >> >> *Hiccup 2: SAGE_FAT_BINARIES / SAGE_ATLAS_ARCH conflict* >> > > It seems that you set both, which does not make sense. SAGE_FAT_BINARY=yes > will build a bin

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-23 Thread Volker Braun
The maxima issue is http://trac.sagemath.org/15546 -- 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,

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-23 Thread Volker Braun
Also, fortran is a build-time dependency (but not runtime). You either install your distro's fortran, or you compile gcc (which includes fortran). You did both. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and s

[sage-devel] Re: building sage 6.0 on debian live (squeeze)

2013-12-23 Thread Volker Braun
On Monday, December 23, 2013 10:07:12 PM UTC, Emil Widmann wrote > > *Hiccup 2: SAGE_FAT_BINARIES / SAGE_ATLAS_ARCH conflict* > It seems that you set both, which does not make sense. SAGE_FAT_BINARY=yes will build a binary that we consider "generic". You either build that, or you specify the arc