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 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 over the week-end. > >> >> Incidentally, it is *NOT* on our webpage ( >> http://www.sagemath.org/doc/developer). Harald, do we have a plan for >> updating the docs to Sage 6? >> > > BTW : As far as I know, Sage 6 has not been "officialy" released. I am > aware of this non-release release by your "Releasing sage 6" post on > sage-release ("Today is a good day to die", indeed...). And the main Sage > Web page still points at 5.13... > >> >> >> >> On Friday, December 20, 2013 6:21:00 PM UTC, Emmanuel Charpentier wrote: >>> >>> 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 >>>> different compile-time features in freetype that can easily conflict with >>>> the system freetype. >>>> >>> >>> Okay. Am I wrong in thinking that a newer version of freetype *might* >>> work around the problem (the real solution, avoiding LD_LIBRARY_PATH, seems >>> to involve a *lot* of work and is way above my current comprehension of >>> sage sources) ? >>> >>> If so, does an adaptation of the sage developper's guide exist for the >>> gi-supported versions of sage (6.0 and up) ? Creating a new spkg for 5.13 >>> seems a bit futile now, and I checked that I could build sage 6.0. >>> >>> In other words, where can I find a bit of git handholding for >>> integrating a "better" freetype in sage ? <Blush> I'm new to git </Blush>. >>> >>> I agree that another workaround might be to *remove* >>> freetype-2.3.5-incompatible fonts from "big machine", but there might be >>> hell to pay with other programs... >>> >>> >>>> The double slashes are fine, // is identical to / in unix paths unless >>>> it is an the beginning. >>>> >>> >>> That's what I thought, but R's dyn.load might be different (however, >>> trying to dyn.load R's X11 library with a corrected path gives the same >>> result as with the original path). >>> >>>> >>>> >>>> >>>> On Wednesday, December 18, 2013 8:23:51 PM UTC, Emmanuel Charpentier >>>> wrote: >>>>> >>>>> 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 is lacking on the >>>>> large one. Any hint ? >>>>> >>>>> 2) The compilation process leads to some strange hardcoded paths. On >>>>> the large machine : >>>>> >>>>> charpent@asus16-ec:/usr/local/sage-5.13$ ./ssage -R >>>>> bash: ./ssage: Aucun fichier ou dossier de ce type >>>>> 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 >>>>> Platform: x86_64-unknown-linux-gnu (64-bit) >>>>> >>>>> R est un logiciel libre livré sans AUCUNE GARANTIE. >>>>> Vous pouvez le redistribuer sous certaines conditions. >>>>> Tapez 'license()' ou 'licence()' pour plus de détails. >>>>> >>>>> R est un projet collaboratif avec de nombreux contributeurs. >>>>> Tapez 'contributors()' pour plus d'information et >>>>> 'citation()' pour la façon de le citer dans les publications. >>>>> >>>>> Tapez 'demo()' pour des démonstrations, 'help()' pour l'aide >>>>> en ligne ou 'help.start()' pour obtenir l'aide au format HTML. >>>>> Tapez 'q()' pour quitter R. >>>>> >>>>> > capabilities() >>>>> jpeg png tiff tcltk X11 aqua http/ftp >>>>> sockets >>>>> FALSE FALSE FALSE FALSE FALSE FALSE TRUE >>>>> TRUE >>>>> libxml fifo cledit iconv NLS profmem cairo >>>>> TRUE TRUE TRUE TRUE TRUE FALSE FALSE >>>>> Message d'avis : >>>>> In doTryCatch(return(expr), name, parentenv, handler) : >>>>> impossible de charger l'objet partagé >>>>> '/usr/local/sage-5.13/local/lib/R//modules//R_X11.so': >>>>> >>>>> These doubled slashes are highly suspicious to me. ISTR having had the >>>>> same problem with orther R packages (most notably with Rcpp-derived >>>>> packages). >>>>> >>>>> /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0: undefined symbol: >>>>> FT_Face_GetCharVariantIndex >>>>> > q("no") >>>>> >>>>> One can check that the needed module **is** here : >>>>> >>>>> charpent@asus16-ec:/usr/local/sage-5.13$ ls -l >>>>> local/lib/R/modules/R_X11.so >>>>> -rwxr-xr-x 1 charpent charpent 341761 déc. 18 20:11 >>>>> local/lib/R/modules/R_X11.so >>>>> >>>>> and is at least of the expected type : >>>>> >>>>> charpent@asus16-ec:/usr/local/sage-5.13$ file >>>>> local/lib/R/modules/R_X11.so local/lib/R/modules/R_X11.so: ELF 64-bit LSB >>>>> >>>>> shared object, x86-64, version 1 (SYSV), dynamically linked, >>>>> BuildID[sha1]=3cbd90661223e67daad0172034908979e7633afa, not stripped >>>>> charpent@asus16-ec:/usr/local/sage-5.13$ >>>>> >>>>> Any hint, anyone ? >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
