Re: [sage-devel] Trouble with pkgconf

2018-06-30 Thread Jeroen Demeyer
Please do the following: $ rm -rf logs # to remove outdated logs $ make build and then post the actual log files of any failing packages. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

Re: [sage-devel] Names of objects in sage

2018-06-30 Thread Thierry
Hi, maybe what you need is to write a _sage_input_ method for those objects, see: sage: M = matrix([[1,2],[3,4]])a ; M [1 2] [3 4] sage: sage_input(M) matrix(ZZ, [[1, 2], [3, 4]]) The first is more readable the second allows copy-paste. Also, you want the string to contain all the information

[sage-devel] Names of objects in sage

2018-06-30 Thread Andrew
For some reason in sage when printing we often use long and laborious names like: sage: LaurentPolynomialRing(ZZ,'q') Univariate Laurent Polynomial Ring in q over Integer Ring sage: LaurentPolynomialRing(GF(5),'q') Univariate Laurent Polynomial Ring in q over Finite Field of size 5 Is there any

Re: [sage-devel] Trouble with pkgconf

2018-06-30 Thread Dima Pasechnik
please post install.log and logs for each of these packages (they are in logs/) -- 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

Re: [sage-devel] Trouble with pkgconf

2018-06-30 Thread rebeccalaurenmiller
I'm getting the following Errors/; ackage: fflas_ffpack-2.3.2 log file: /Users/RebeccaMiller/sage-develop/logs/pkgs/fflas_ffpack-2.3.2.log build directory: /Users/RebeccaMiller/sage-develop/local/var/tmp/sage/build/fflas_ffpack-2.3.2 * package: pkgconf-0.9.7.p0 log file: /Users/Rebecc

Re: [sage-devel] Trouble with pkgconf

2018-06-30 Thread Jeroen Demeyer
On 2018-06-02 17:05, Erik Bray wrote: I have another existing branch that would have fixed it, but that hasn't been merged yet. I think I need to rebase it though. Any news on this? I'm at Sage Days 94 and people are reporting that this error still exists on Sage 8.3.beta7. -- You received