Le vendredi 20 décembre 2013 19:40:58 UTC+1, Volker Braun a écrit :
The new developer manual explains how to use git and the new way to
package stuff. It should be in SAGE_ROOT/src/doct/output/en/developer. Feel
free to ask if you run into any problems...
This is now trac#15561
Dear Volker,
Le mercredi 18 décembre 2013 22:23:21 UTC+1, Volker Braun a écrit :
I get the same error, btw. Your big machine machine has a better freetype
or more/different fonts. The error comes from libharfbuzz, the f.d.o.
OpenType shaper. Sage compiles its own freetype, but there are
The new developer manual explains how to use git and the new way to package
stuff. It should be in SAGE_ROOT/src/doct/output/en/developer. Feel free to
ask if you run into any problems...
Incidentally, it is *NOT* on our webpage
(http://www.sagemath.org/doc/developer). Harald, do we have a
Le vendredi 20 décembre 2013 19:40:58 UTC+1, Volker Braun a écrit :
The new developer manual explains how to use git and the new way to
package stuff. It should be in SAGE_ROOT/src/doct/output/en/developer. Feel
free to ask if you run into any problems...
Thank you ! I'll try to do that
For the record, sage 6.0 is officially released ;-)
On Friday, December 20, 2013 6:49:09 PM UTC, Emmanuel Charpentier wrote:
Le vendredi 20 décembre 2013 19:40:58 UTC+1, Volker Braun a écrit :
The new developer manual explains how to use git and the new way to
package stuff. It should be
A couple more data points :
1) on a smaller machine (but still amd64 and Debian testing), sage 5-13
compilation from sources gave me an R spkg that **has** graphics
capabilities. But for the life of me, I can't pinpoint what is installed on
the small machine that enables those capabilities and
I get the same error, btw. Your big machine machine has a better freetype
or more/different fonts. The error comes from libharfbuzz, the f.d.o.
OpenType shaper. Sage compiles its own freetype, but there are different
compile-time features in freetype that can easily conflict with the system
Looks like the usual LD_LIBRARY_PATH nightmare. Whenever you use system
shared libraries it is a bit of a gamble... The only correct solution is to
not set LD_LIBRARY_PATH.
On Tuesday, December 17, 2013 8:41:52 PM UTC, Emmanuel Charpentier wrote:
I compiled sage from sources on a debian
Three data points, some random musings and a couple questions :
1)
charpent@asus16-ec:/usr/local/sage-5.13$ echo $LD_LIBRARY_PATH
charpent@asus16-ec:/usr/local/sage-5.13$ ./sage -R
R version 3.0.2 (2013-09-25) -- Frisbee Sailing
Copyright (C) 2013 The R Foundation for Statistical Computing
On Tuesday, December 17, 2013 10:14:19 PM UTC, Emmanuel Charpentier wrote:
Again : how do you do that ?
Start with http://trac.sagemath.org/ticket/10572 and then use that to
systematically set rpaths on libraries. There is no easy way...
--
You received this message because you are
10 matches
Mail list logo
