Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread kcrisman
On Wednesday, March 26, 2014 3:58:06 PM UTC-4, John Cremona wrote: On 26 March 2014 18:22, kcrisman kcri...@gmail.com javascript: wrote: I've created http://trac.sagemath.org/ticket/16017 for this libs.mwrank issue, though I still really don't know what the issue is :( Previous

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread kcrisman
Of course, this should not be the reason for your problem since Sage does now use Flint 2.3, and possibly 2.4. I have *not* tested eclib against Flint 2.4 and perhaps I should! Though 2.4.3 still has the nmod_mat module, and eclib builds on most machines. John

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread kcrisman
On Thursday, March 27, 2014 11:23:07 AM UTC-4, kcrisman wrote: Of course, this should not be the reason for your problem since Sage does now use Flint 2.3, and possibly 2.4. I have *not* tested eclib against Flint 2.4 and perhaps I should! Though 2.4.3 still has the nmod_mat

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread John Cremona
On 27 March 2014 17:03, kcrisman kcris...@gmail.com wrote: On Thursday, March 27, 2014 11:23:07 AM UTC-4, kcrisman wrote: Of course, this should not be the reason for your problem since Sage does now use Flint 2.3, and possibly 2.4. I have *not* tested eclib against Flint 2.4 and

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread kcrisman
eclib's test suite passed without errors That sounds good -- you must therefore have a working version of mwrank (and what else would anyone need?) Sriously, this really does mean that the few binaries which eclib builds work OK. Not that I had any doubts! But the problem is

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread leif
kcrisman wrote: Of course, this should not be the reason for your problem since Sage does now use Flint 2.3, and possibly 2.4. I have *not* tested eclib against Flint 2.4 and perhaps I should! Though 2.4.3 still has the nmod_mat module, and eclib builds on most

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread leif
kcrisman wrote: On Thursday, March 27, 2014 1:29:58 PM UTC-4, kcrisman wrote: eclib's test suite passed without errors That sounds good -- you must therefore have a working version of mwrank (and what else would anyone need?) Sriously, this really does

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-27 Thread leif
François Bissey wrote: On Thu, 27 Mar 2014 20:29:29 leif wrote: kcrisman wrote: On Thursday, March 27, 2014 1:29:58 PM UTC-4, kcrisman wrote: eclib's test suite passed without errors That sounds good -- you must therefore have a working version of mwrank (and what

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-26 Thread kcrisman
I've created http://trac.sagemath.org/ticket/16017 for this libs.mwrank issue, though I still really don't know what the issue is :( -- 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

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-25 Thread kcrisman
Why would that cause symbols not to be defined? But this must be it - the flint/src/fq_nmod_mat does indeed not have a profile/ directory so that causes this to happen. Somehow this causes problems in creating the dylib, but I don't understand all that. I'm not convinced.^TM

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-24 Thread kcrisman
On Friday, March 21, 2014 1:09:19 PM UTC-4, kcrisman wrote: On Friday, March 21, 2014 11:56:43 AM UTC-4, John Cremona wrote: Have you tried asking on flint-devel? If their Makefiles don't work on some systems then they should know that. True, but I don't know whether in fact the

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-21 Thread kcrisman
On Thursday, March 20, 2014 8:28:34 PM UTC-4, François wrote: On Thu, 20 Mar 2014 17:25:15 kcrisman wrote: On Thursday, March 20, 2014 5:11:23 PM UTC-4, Jean-Pierre Flori wrote: On Thursday, March 20, 2014 9:44:57 PM UTC+1, François wrote: I think I am starting to get some ideas.

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-21 Thread Jean-Pierre Flori
At first sight the Makefile does not look that bad. (And Makefile.subdirs is not touched, so yours is the same as every other's one.) On Friday, March 21, 2014 1:56:28 PM UTC+1, kcrisman wrote: On Thursday, March 20, 2014 8:28:34 PM UTC-4, François wrote: On Thu, 20 Mar 2014 17:25:15

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-21 Thread kcrisman
I'm going to have a stream-of-consciousness thing here. At first sight the Makefile does not look that bad. (And Makefile.subdirs is not touched, so yours is the same as every other's one.) Nonetheless this is the problem, I think. If you substitute things in line 41 of Makefile.subdirs,

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-21 Thread Jean-Pierre Flori
On Friday, March 21, 2014 4:23:49 PM UTC+1, kcrisman wrote: I'm going to have a stream-of-consciousness thing here. At first sight the Makefile does not look that bad. (And Makefile.subdirs is not touched, so yours is the same as every other's one.) Nonetheless this is the problem, I

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-21 Thread John Cremona
Have you tried asking on flint-devel? If their Makefiles don't work on some systems then they should know that. John On 21 March 2014 15:37, Jean-Pierre Flori jpfl...@gmail.com wrote: On Friday, March 21, 2014 4:23:49 PM UTC+1, kcrisman wrote: I'm going to have a stream-of-consciousness

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-21 Thread kcrisman
On Friday, March 21, 2014 11:56:43 AM UTC-4, John Cremona wrote: Have you tried asking on flint-devel? If their Makefiles don't work on some systems then they should know that. True, but I don't know whether in fact the Makefile doesn't work. Or rather, all I know is this one include

[sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread kcrisman
OS X 10.4 continues... Here is my next build error, this time in linking mwrank in the Sage library. Apparently something wasn't completely compiled in the libflint build? In particular, there is apparently only a libflint.a compiled in my log for the flint spkg (pkg?), though there is both

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread John Cremona
I hope that a Mac expert can help, since I don't use Macs so rely on others to test when I upgrade eclib (which includes mwrank and does indeed depend on Flint). Sorry, John On 20 March 2014 18:54, kcrisman kcris...@gmail.com wrote: OS X 10.4 continues... Here is my next build error, this time

[sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread Jean-Pierre Flori
On Thursday, March 20, 2014 7:54:35 PM UTC+1, kcrisman wrote: OS X 10.4 continues... Here is my next build error, this time in linking mwrank in the Sage library. Apparently something wasn't completely compiled in the libflint build? In particular, there is apparently only a libflint.a

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread kcrisman
On Thursday, March 20, 2014 3:41:27 PM UTC-4, John Cremona wrote: I hope that a Mac expert can help, since I don't use Macs so rely on others to test when I upgrade eclib (which includes mwrank and does indeed depend on Flint). Sorry, John, that is kind of you to say! I'm pretty sure

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread François Bissey
On Thu, 20 Mar 2014 12:46:54 kcrisman wrote: On Thursday, March 20, 2014 3:41:27 PM UTC-4, John Cremona wrote: I hope that a Mac expert can help, since I don't use Macs so rely on others to test when I upgrade eclib (which includes mwrank and does indeed depend on Flint). Sorry, John,

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread François Bissey
On Fri, 21 Mar 2014 09:10:40 François Bissey wrote: On Thu, 20 Mar 2014 12:46:54 kcrisman wrote: On Thursday, March 20, 2014 3:41:27 PM UTC-4, John Cremona wrote: I hope that a Mac expert can help, since I don't use Macs so rely on others to test when I upgrade eclib (which includes

[sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread kcrisman
On Thursday, March 20, 2014 3:45:56 PM UTC-4, Jean-Pierre Flori wrote: On Thursday, March 20, 2014 7:54:35 PM UTC+1, kcrisman wrote: OS X 10.4 continues... Here is my next build error, this time in linking mwrank in the Sage library. Apparently something wasn't completely compiled in

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread kcrisman
On Thursday, March 20, 2014 4:10:40 PM UTC-4, François wrote: On Thu, 20 Mar 2014 12:46:54 kcrisman wrote: On Thursday, March 20, 2014 3:41:27 PM UTC-4, John Cremona wrote: I hope that a Mac expert can help, since I don't use Macs so rely on others to test when I upgrade eclib

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread Bill Hart
These look suspicous: ../Makefile.subdirs:41: no file name for `-include' But I don't know what they mean. I'm not a Mac expert either. :-( Bill. On 20 March 2014 21:18, kcrisman kcris...@gmail.com wrote: On Thursday, March 20, 2014 4:10:40 PM UTC-4, François wrote: On Thu, 20 Mar 2014

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread François Bissey
They are. I just checked on my 10.9.2 machine and I don't have them. That, to me, suggests a variable in the makefile is not defined and -include is taken as a target which doesn't bod well. Francois On Thu, 20 Mar 2014 21:23:41 Bill Hart wrote: These look suspicous:

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread Jean-Pierre Flori
Was it built in parallel? On Thursday, March 20, 2014 9:26:25 PM UTC+1, François wrote: They are. I just checked on my 10.9.2 machine and I don't have them. That, to me, suggests a variable in the makefile is not defined and -include is taken as a target which doesn't bod well.

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread François Bissey
I think I am starting to get some ideas. The missing includes are an essential key to understand the problem. We may need the result of the configuration phase on that machine. The includes statements are present in the following form -include $(patsubst %, %.d, $(PROFS)) with variations, this

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread Jean-Pierre Flori
On Thursday, March 20, 2014 9:44:57 PM UTC+1, François wrote: I think I am starting to get some ideas. The missing includes are an essential key to understand the problem. We may need the result of the configuration phase on that machine. The includes statements are present in the

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-20 Thread kcrisman
On Thursday, March 20, 2014 5:11:23 PM UTC-4, Jean-Pierre Flori wrote: On Thursday, March 20, 2014 9:44:57 PM UTC+1, François wrote: I think I am starting to get some ideas. The missing includes are an essential key to understand the problem. We may need the result of the

[sage-release] Re: Sage 6.2.beta4 released

2014-03-19 Thread Maarten Derickx
When I tried to build it also failed at singular. ld complains about: symbol dyld_stub_binding_helper not found . Googling for this led me to some not very helpful threads that where mostly about that when you try to compile something for IOS you should set target at least a recent enough

[sage-release] Re: Sage 6.2.beta4 released

2014-03-19 Thread Volker Braun
Which version of OSX and Sage, and did you try the branch at the aforementioned ticket? On Wednesday, March 19, 2014 5:41:41 AM UTC-4, Maarten Derickx wrote: When I tried to build it also failed at singular. ld complains about: symbol dyld_stub_binding_helper not found . Googling for this

[sage-release] Re: Sage 6.2.beta4 released

2014-03-19 Thread Maarten Derickx
OSX is 10.9 and I have the problem with sage 6.2.beta4, this is the first time I upgraded my sage using git. I thought I might have just screwed things up with the upgrade procedure. So to test this I cloned a new sage repo in another directory and started building the master branch (which is

[sage-release] Re: Sage 6.2.beta4 released

2014-03-19 Thread John H Palmieri
As Volker asked, does the branch at http://trac.sagemath.org/ticket/15937 help? (If you upgraded Xcode recently, that would have broken the Singular build, and the error message you're getting looks just like the one I got after I had upgraded Xcode.) John On Wednesday, March 19, 2014

[sage-release] Re: Sage 6.2.beta4 released

2014-03-18 Thread kcrisman
On Tuesday, March 18, 2014 2:19:05 PM UTC-4, kcrisman wrote: it might be trickier: basically the system does have sys_errlist, but HAVE_SYS_ERRLIST gets set to undefined by ./configure. Try adding -DHAVE_SYS_ERRLIST to CFLAGS in spkg-install, and see if this fixes the problem. Man,

[sage-release] Re: Sage 6.2.beta4 released

2014-03-18 Thread Volker Braun
On Tuesday, March 18, 2014 2:19:05 PM UTC-4, kcrisman wrote: gcc -g -Wl,-no_pie -o gap ariths.o .. weakptr.o -lm /Users/.../sage-6.2.beta4/local/lib/libgmp.a /usr/bin/ld: unknown flag: -no_pie collect2: error: ld returned 1 exist status I'm searching for stuff about this, maybe

[sage-release] Re: Sage 6.2.beta4 released

2014-03-18 Thread Dima Pasechnik
On 2014-03-18, kcrisman kcris...@gmail.com wrote: On Monday, March 17, 2014 4:19:26 PM UTC-4, Dima Pasechnik wrote: On 2014-03-17, kcrisman kcri...@gmail.com javascript: wrote: On OS X 10.4 PPC, I get the following error. Incidentally, I'm used to GAP compiling toward the very end of

[sage-release] Re: Sage 6.2.beta4 released

2014-03-18 Thread Dima Pasechnik
On 2014-03-18, kcrisman kcris...@gmail.com wrote: On Monday, March 17, 2014 4:19:26 PM UTC-4, Dima Pasechnik wrote: On 2014-03-17, kcrisman kcri...@gmail.com javascript: wrote: On OS X 10.4 PPC, I get the following error. Incidentally, I'm used to GAP compiling toward the very end of

[sage-release] Re: Sage 6.2.beta4 released

2014-03-17 Thread kcrisman
On OS X 10.4 PPC, I get the following error. Incidentally, I'm used to GAP compiling toward the very end of the process on this machine, so I was surprised it showed up relatively early. I'd be grateful for any hints; looks like includes in the wrong order or something, but I may be

[sage-release] Re: Sage 6.2.beta4 released

2014-03-17 Thread Jean-Pierre Flori
On Monday, March 17, 2014 3:35:17 PM UTC+1, kcrisman wrote: On OS X 10.4 PPC, I get the following error. Incidentally, I'm used to GAP compiling toward the very end of the process on this machine, so I was surprised it showed up relatively early. I'd be grateful for any hints; looks

[sage-release] Re: Sage 6.2.beta4 released

2014-03-17 Thread kcrisman
Also, a few questions. 1) We used to be able to just fake an installation by touching a certain file. I assume that touching the log file in logs/pkgs would not suffice here, though? Thanks for those pointers! So... would touching one of the files in the installed list be

[sage-release] Re: Sage 6.2.beta4 released

2014-03-17 Thread Jean-Pierre Flori
On Monday, March 17, 2014 3:46:54 PM UTC+1, kcrisman wrote: Also, a few questions. 1) We used to be able to just fake an installation by touching a certain file. I assume that touching the log file in logs/pkgs would not suffice here, though? Thanks for those pointers! So...

[sage-release] Re: Sage 6.2.beta4 released

2014-03-17 Thread Dima Pasechnik
On 2014-03-17, kcrisman kcris...@gmail.com wrote: On OS X 10.4 PPC, I get the following error. Incidentally, I'm used to GAP compiling toward the very end of the process on this machine, so I was surprised it showed up relatively early. I'd be grateful for any hints; looks like includes

[sage-release] Re: Sage 6.2.beta4 released

2014-03-17 Thread kcrisman
On Monday, March 17, 2014 4:19:26 PM UTC-4, Dima Pasechnik wrote: On 2014-03-17, kcrisman kcri...@gmail.com javascript: wrote: On OS X 10.4 PPC, I get the following error. Incidentally, I'm used to GAP compiling toward the very end of the process on this machine, so I was surprised

[sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread kcrisman
On Tuesday, March 11, 2014 4:08:10 PM UTC-4, Volker Braun wrote: This includes the fix for the parallel build race with python packages, so if you ran into that please test! As usual, the newest beta is the develop branch on our git server. Alternatively, use the tarball at

[sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread Volker Braun
vbraun@boxen:~/release/sage-6.2.beta4$ md5 sage-6.2.beta4.tar.gz The program 'md5' is currently not installed. You can install it by typing: sudo apt-get install sleuthkit -bash: md5: command not found vbraun@boxen:~/release/sage-6.2.beta4$ sha512sum sage-6.2.beta4.tar.gz

[sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread kcrisman
vbraun@boxen:~/release/sage-6.2.beta4$ md5 sage-6.2.beta4.tar.gz The program 'md5' is currently not installed. You can install it by typing: sudo apt-get install sleuthkit -bash: md5: command not found That is the problem! Because my error message for bzip2 says Checksum: a4e60f...

[sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread kcrisman
My md5 works just fine, but apparently sed doesn't with this. And that makes sense, since $ md5 Downloads/974230_1010378741420_571824162_n.jpg MD5 (Downloads/974230_1010378741420_571824162_n.jpg) = bf36ca4308ce426d74d095681ebd5a18 $ md5

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread leif
Volker Braun wrote: vbraun@boxen:~/release/sage-6.2.beta4$ md5 sage-6.2.beta4.tar.gz The program 'md5' is currently not installed. You can install it by typing: sudo apt-get install sleuthkit -bash: md5: command not found leif@boxen:~$ md5sum

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread Jonathan Bober
On Thu, Mar 13, 2014 at 6:45 PM, Volker Braun vbraun.n...@gmail.com wrote: export LC_ALL=C and try again That doesn't make a difference. -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop receiving

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-14 Thread Volker Braun
On Friday, March 14, 2014 7:53:10 PM UTC-4, Jonathan Bober wrote: I don't know why. However, having just spent a bit of time fighting with selinux while setting up apache stuff, I've decided that this must also be some sort of strange selinux issue. Highly unlikely unless you put Sage

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-13 Thread Volker Braun
Why don't you have /dev/stdout? Which operating system? Its supposed to be present in Linux, though not POSXI. On Wednesday, March 12, 2014 9:19:46 PM UTC-4, Jonathan Bober wrote: I built, and all tests passed. However, I can't seen to install packages: jb12407@lmfdb5:~/sage-6.2.beta4$

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-13 Thread Jonathan Bober
I do have /dev/stdout. The error message is correct, however. /dev/stdout is not a directory. (I have no idea why it wants it to be a directory.) On Thu, Mar 13, 2014 at 1:40 PM, Volker Braun vbraun.n...@gmail.com wrote: Why don't you have /dev/stdout? Which operating system? Its supposed to

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-13 Thread Volker Braun
Do you have some wonky locale settings, e.g. UTF8 handed through by ssh to a server that is not unicode aware? On Thursday, March 13, 2014 4:56:14 PM UTC-4, Jonathan Bober wrote: I do have /dev/stdout. The error message is correct, however. /dev/stdout is not a directory. (I have no idea

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-13 Thread Volker Braun
export LC_ALL=C and try again On Thursday, March 13, 2014 6:22:58 PM UTC-4, Jonathan Bober wrote: I suppose that's possible, but I'd be surprised if the server isn't unicode aware. Do you have a suggestion for how I could check this? I tried unsetting the LANG environment variable, which

[sage-release] Re: Sage 6.2.beta4 released

2014-03-12 Thread Dima Pasechnik
I cannot seem to be able to build on OSX 10.6.8 and the usual Sage-supplied gcc even if I do make distclean first. It gets stuck at Singular: ... g++ -O2 -g -fPIC -DLIBSINGULAR -I.. -I/usr/local/src/sage/sage-6.1.rc0/local -pipe -fno-implicit-templates -I..

[sage-release] Re: Sage 6.2.beta4 released

2014-03-12 Thread Dima Pasechnik
On 2014-03-12, Dima Pasechnik dimp...@gmail.com wrote: I cannot seem to be able to build on OSX 10.6.8 and the usual Sage-supplied gcc even if I do make distclean first. It gets stuck at Singular: oops, sorry for noise - wrong PATH, wrong libtool... Please ignore the previous message. -- You

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-12 Thread Jonathan Bober
I built, and all tests passed. However, I can't seen to install packages: jb12407@lmfdb5:~/sage-6.2.beta4$ ./sage -i gap_packages Found local metadata for gap_packages-4.7.4 Attempting to download package gap_packages-4.7.4 Trying to download

Re: [sage-release] Re: Sage 6.2.beta4 released

2014-03-12 Thread John Cremona
On 12 March 2014 18:19, Jonathan Bober jwbo...@gmail.com wrote: I built, and all tests passed. However, I can't seen to install packages: jb12407@lmfdb5:~/sage-6.2.beta4$ ./sage -i gap_packages Found local metadata for gap_packages-4.7.4 Attempting to download package gap_packages-4.7.4