[sage-support] install on maxosx 10.4 intel fails
Installing sage-2.8.13-osx10.4-i386-Darwin.tar.gz fails during untar'ing, with the error tar: sage-2.8.13-i386-Darwin/local/LIB: Cannot create symlink to `lib': File exists Subsequently running sage ends in all sorts of errors - so the missing symlink is an issue. This error occurs on an Intel MacPro, and also a PowerPC MacMini (untar'ing only) Installing the PowerPC version on the MacMini succeeds without error. A problem with the tarball? I'm going to have a play now. First opinions are good. I'm an electronics engineer who occasionally has a need to wrangle some simple maths. For heavy lifting I usually use MathCAD, but Sage seems to handle most of my applications for MathCAD, plus I already use Python. Good work guys - if this proves useful I'll look into ways for us to contribute. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: install on maxosx 10.4 intel fails
On Nov 29, 12:12 pm, joel [EMAIL PROTECTED] wrote: Hello Joel, Installing sage-2.8.13-osx10.4-i386-Darwin.tar.gz fails during untar'ing, with the error tar: sage-2.8.13-i386-Darwin/local/LIB: Cannot create symlink to `lib': File exists What are you using to untar? I wouldn't really trust any utility, especially any graphical one. Subsequently running sage ends in all sorts of errors - so the missing symlink is an issue. This error occurs on an Intel MacPro, and also a PowerPC MacMini (untar'ing only) Any chance you might have gotten a corrupted download? [EMAIL PROTECTED]:/home/was/www/sage/SAGEbin/apple_osx/intel$ md5sum * 61383c29edc62b83d8c19e2f56ddc0c6 sage-2.8.13-osx10.4-i386- Darwin.tar.gz 10d5d3ce209e0f561d60c7e9bef9055a sage-2.8.13-osx10.5-i386- Darwin.tar.gz You should compare the md5sum of the above with the one you get from your tarball. In case it is different please tell us where you downloaded the files from, i.e. which mirror or sagemath.org. [EMAIL PROTECTED]:/home/was/www/sage/SAGEbin/apple_osx/intel$ tar xzf sage-2.8.13-osx10.4-i386-Darwin.tar.gz -C /tmp/Work-mabshoff/ So at least the tarball on sage.math is fine. Installing the PowerPC version on the MacMini succeeds without error. A problem with the tarball? I'm going to have a play now. First opinions are good. I'm an electronics engineer who occasionally has a need to wrangle some simple maths. For heavy lifting I usually use MathCAD, but Sage seems to handle most of my applications for MathCAD, plus I already use Python. Good work guys - if this proves useful I'll look into ways for us to contribute. Excellent. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 29, 7:40 am, Michael Brickenstein [EMAIL PROTECTED] wrote: Hello! The same problem appears here. I suppose, it could be a problem with the NFS home directories. Best regards, Michael (the real Michael) Ok, any chance you could strace a failing sage session? Please also tell us if you are using NFS or some other network filesystem for your home directory. If so does moving the install to /tmp or some other local filesystem fix the issue? Cheers, Michael [the non-real one :)] --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: install on maxosx 10.4 intel fails
I mostly operate from the command line, so all the installation was done from a macosx bash shell. tar is GNU tar version 1.14. I downloaded sage-2.1.13-osx10.4-i386-Darwin.tar.gz from sagemath.org/ SAGEbin/apple_osx/intel md5 checksum is OK tar -zxf sage-2.1.13-osx10.4-i386-Darwin.tar.gz fails with the same error... tar: sage-2.8.13-i386-Darwin/local/LIB: Cannot create symlink to `lib': File exists So I tried tar -ztf sage-2.1.13-osx10.4-i386-Darwin.tar.gz tarlist and then grepping for 'tar: sage-2.8.13-i386-Darwin/local/LIB' and for tar: sage-2.8.13-i386-Darwin/local/lib This shows that both LIB and lib directories exist in the tar listing. The lib directory and contents is put down first, then what I assume is a symbolic link is created from LIB to lib - but I'm not sure. the /local/LIB file/link does not exist in the PowerPC version Could this be something to do with case-insensitivity in the default MacOSX filesystem? All my drives are formatted to Mac OS Extended (Journaled), which would not differentiate between LIB and lib. Trying to create a symbolic link from LIB to lib would effectively be creating a link to itself. Possibly, if the build was only tested on a case-sensitive disk, this would not show up in testing. Or maybe the LIB link is unused, so the PowerPC version does OK without it, but in the Intel version it is causing the untar'ing to fail. Joel On Nov 29, 11:44 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 29, 12:12 pm, joel [EMAIL PROTECTED] wrote: Hello Joel, Installing sage-2.8.13-osx10.4-i386-Darwin.tar.gz fails during untar'ing, with the error tar: sage-2.8.13-i386-Darwin/local/LIB: Cannot create symlink to `lib': File exists What are you using to untar? I wouldn't really trust any utility, especially any graphical one. Subsequently running sage ends in all sorts of errors - so the missing symlink is an issue. This error occurs on an Intel MacPro, and also a PowerPC MacMini (untar'ing only) Any chance you might have gotten a corrupted download? [EMAIL PROTECTED]:/home/was/www/sage/SAGEbin/apple_osx/intel$ md5sum * 61383c29edc62b83d8c19e2f56ddc0c6 sage-2.8.13-osx10.4-i386- Darwin.tar.gz 10d5d3ce209e0f561d60c7e9bef9055a sage-2.8.13-osx10.5-i386- Darwin.tar.gz You should compare the md5sum of the above with the one you get from your tarball. In case it is different please tell us where you downloaded the files from, i.e. which mirror or sagemath.org. [EMAIL PROTECTED]:/home/was/www/sage/SAGEbin/apple_osx/intel$ tar xzf sage-2.8.13-osx10.4-i386-Darwin.tar.gz -C /tmp/Work-mabshoff/ So at least the tarball on sage.math is fine. Installing the PowerPC version on the MacMini succeeds without error. A problem with the tarball? I'm going to have a play now. First opinions are good. I'm an electronics engineer who occasionally has a need to wrangle some simple maths. For heavy lifting I usually use MathCAD, but Sage seems to handle most of my applications for MathCAD, plus I already use Python. Good work guys - if this proves useful I'll look into ways for us to contribute. Excellent. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Hi!
The program is located on a local disc, it is just my home on a NFS
file system.
I tried linking .sage to /tmp/blupper (I hope, that is not a
trademark)
and everything worked.
Then I removed the link and tried again with my normal nfs home and
produced the following strace.
Best regards,
Michael
strace sage
execve(/usr/local/bin/sage, [sage], [/* 28 vars */]) = 0
brk(0) = 0x5be000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba41fcd2000
uname({sys=Linux, node=biberach, ...}) = 0
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=53492, ...}) = 0
mmap(NULL, 53492, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2ba41fcd3000
close(3)= 0
open(/lib/libncurses.so.5, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0
\0\1\0\0\0\200\1\2\0\0\0\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=370728, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba41fce1000
mmap(NULL, 1420648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x2ba41fce2000
mprotect(0x2ba41fd2f000, 1044480, PROT_NONE) = 0
mmap(0x2ba41fe2e000, 61440, PROT_READ|PROT_WRITE, MAP_PRIVATE|
MAP_FIXED|MAP_DENYWRITE, 3, 0x4c000) = 0x2ba41fe2e000
close(3)= 0
open(/lib/libdl.so.2, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0`
\16\0\0\0\0\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=14528, ...}) = 0
mmap(NULL, 2109728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x2ba41fed3000
mprotect(0x2ba41fed5000, 2097152, PROT_NONE) = 0
mmap(0x2ba4200d5000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x2000) = 0x2ba4200d5000
close(3)= 0
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0
\0\1\0\0\0\220\334\1\0\0\0\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1293456, ...}) = 0
mmap(NULL, 3399928, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x2ba4200d7000
mprotect(0x2ba42020d000, 2093056, PROT_NONE) = 0
mmap(0x2ba42040c000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|
MAP_FIXED|MAP_DENYWRITE, 3, 0x135000) = 0x2ba42040c000
mmap(0x2ba420411000, 16632, PROT_READ|PROT_WRITE, MAP_PRIVATE|
MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2ba420411000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba420416000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba420417000
arch_prctl(ARCH_SET_FS, 0x2ba420416dd0) = 0
mprotect(0x2ba42040c000, 16384, PROT_READ) = 0
mprotect(0x2ba4200d5000, 4096, PROT_READ) = 0
mprotect(0x2ba41fed1000, 4096, PROT_READ) = 0
munmap(0x2ba41fcd3000, 53492) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open(/dev/tty, O_RDWR|O_NONBLOCK) = 3
close(3)= 0
brk(0) = 0x5be000
brk(0x5df000) = 0x5df000
getuid()= 1136
getgid()= 1103
geteuid() = 1136
getegid() = 1103
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
gettimeofday({1196340233, 97680}, NULL) = 0
open(/proc/meminfo, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba41fcd3000
read(3, MemTotal: 16411324 kB\nMemFre..., 1024) = 630
close(3)= 0
munmap(0x2ba41fcd3000, 4096)= 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0
uname({sys=Linux, node=biberach, ...}) = 0
stat(/home/michael, {st_mode=S_IFDIR|0700, st_size=9216, ...}) = 0
stat(., {st_mode=S_IFDIR|0700, st_size=9216, ...}) = 0
getpid()= 21204
getppid() = 21203
getpgrp() = 21203
rt_sigaction(SIGCHLD, {0x434dd0, [], SA_RESTORER, 0x2ba420107430},
{SIG_DFL}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open(/usr/local/bin/sage, O_RDONLY) = 3
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fff8adeff80) = -1 ENOTTY
(Inappropriate ioctl for device)
lseek(3, 0, SEEK_CUR) = 0
read(3, #!/bin/sh\n\n# Set SAGE_ROOT to th..., 80) = 80
lseek(3, 0, SEEK_SET) = 0
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
dup2(3, 255)= 255
close(3)
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 29, 1:51 pm, Michael Brickenstein [EMAIL PROTECTED] wrote: Hi! Hi Michael, The program is located on a local disc, it is just my home on a NFS file system. I tried linking .sage to /tmp/blupper (I hope, that is not a trademark) and everything worked. Then I removed the link and tried again with my normal nfs home and produced the following strace. interesting about NFS, the strace output doesn't help much since you only captured the inital sage process. :( Could you run strace with -ff -o sage-something, so that you strace all children and write each process to a logfile? You might have to play a little with the parameters (add -F), but I am fairly certain that I can reproduce this behavior locally if NFS is the culprit. Best regards, Michael Cheers, Michael SNIP --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Michael, there is an issue with sqlite on NFS, specifically from http://www.sqlite.org/faq.html: SQLite uses reader/writer locks to control access to the database. (Under Win95/98/ME which lacks support for reader/writer locks, a probabilistic simulation is used instead.) But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. *This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time.* On Windows, Microsoft's documentation says that locking may not work under FAT filesystems if you are not running the Share.exe daemon. People who have a lot of experience with Windows tell me that file locking of network files is very buggy and is not dependable. If what they say is true, sharing an SQLite database between two or more Windows machines might cause unexpected problems. So: fix you installation ;) Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: install on maxosx 10.4 intel fails
On Nov 29, 2007, at 6:41 AM, joel wrote: I mostly operate from the command line, so all the installation was done from a macosx bash shell. tar is GNU tar version 1.14. I downloaded sage-2.1.13-osx10.4-i386-Darwin.tar.gz from sagemath.org/ SAGEbin/apple_osx/intel md5 checksum is OK tar -zxf sage-2.1.13-osx10.4-i386-Darwin.tar.gz fails with the same error... tar: sage-2.8.13-i386-Darwin/local/LIB: Cannot create symlink to `lib': File exists The tarball seems to be the culprit. I can't see how this will work (from tar tvzf): lrwxrwxrwx was/daemon0 2007-11-21 16:30 sage-2.8.13-i386- Darwin/local/LIB - lib How was this built? Is someone using case-sensitivity on Mac OS X? Tsk tsk tsk... Justin -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income Here lies Lester Moore Two bullets from a .44 No less, no more --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 30, 12:05 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: Michael, there is an issue with sqlite on NFS, specifically fromhttp://www.sqlite.org/faq.html: SQLite uses reader/writer locks to control access to the database. (Under Win95/98/ME which lacks support for reader/writer locks, a probabilistic simulation is used instead.) But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. *This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time.* On Windows, Microsoft's documentation says that locking may not work under FAT filesystems if you are not running the Share.exe daemon. People who have a lot of experience with Windows tell me that file locking of network files is very buggy and is not dependable. If what they say is true, sharing an SQLite database between two or more Windows machines might cause unexpected problems. So: fix you installation ;) Actually, some more info: from http://www.sqlite.org/cvstrac/tktview?tn=1556,31 [begin quote] 2005-Dec-07 14:27:26 by drh: This is a bug in either Gentoo linux or in your setup. SQLite is using the fcntl(F_SETLK) interface and linux is telling SQLite that the file is already locked. Not much SQLite can do about this. In version 3.3.0 (or perhaps in a release soon to follow that) we will be offering a version of SQLite that uses lockfiles rather than fcntl() to control file access. There are disadvantages to the use of filelocks: slower, courser grain access, and stale lockfiles that must be manually deleted following a program crash. But lockfiles will work on network filesystems. 2005-Dec-07 16:20:21 by anonymous: I submitted this ticket: It is not a bug in gentoo. Same behaviour on boxes running different versions of SuSE (static build of my binary, executed on different hosts within the same NFS share). 2005-Dec-08 10:56:01 by anonymous: After realizing that it doesn't mean much if I tranfer a static build from gentoo to SuSE, I rebuild my project from scratch on a SuSE box (sqlite-3.2.7). Again, the results are the same: database locked. Since the NFS is up for about three years, it is hard to assume that there's a config error left?! Any hints are highly appreciated! Regards 2005-Dec-08 13:14:24 by anonymous: Please close this ticket. The solution: I hadn't had nfs-utils installed. After merging those and starting rpc.statd, everythings works as expected. Sorry for the fuss. [begin quote] So once we update sqlite to something more current we should actually build with lock files instead. I don't think it will have a performance impact on our use pattern and it will make things less likely for the user to screw up. Yi has already provided an updated spkg, but that cause segfaults in the sfa doctest. As it turns out by now I suspect that symmetrica is at fault in those cases, but I cannot prove that yet. So stay tuned and use the above work around for now. Cheers, Michael Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: install on maxosx 10.4 intel fails
On Nov 30, 12:11 am, Justin C. Walker [EMAIL PROTECTED] wrote: On Nov 29, 2007, at 6:41 AM, joel wrote: I mostly operate from the command line, so all the installation was done from a macosx bash shell. tar is GNU tar version 1.14. I downloaded sage-2.1.13-osx10.4-i386-Darwin.tar.gz from sagemath.org/ SAGEbin/apple_osx/intel md5 checksum is OK tar -zxf sage-2.1.13-osx10.4-i386-Darwin.tar.gz fails with the same error... tar: sage-2.8.13-i386-Darwin/local/LIB: Cannot create symlink to `lib': File exists The tarball seems to be the culprit. I can't see how this will work (from tar tvzf): lrwxrwxrwx was/daemon0 2007-11-21 16:30 sage-2.8.13-i386- Darwin/local/LIB - lib So can we nuke that symbolic link somehow? How was this built? Is someone using case-sensitivity on Mac OS X? Tsk tsk tsk... :) - William rolled the tarball. I believe he build that binary on fermat which is different from the box he used to roll tarballs on. We don't have admin control on fermat - at least I don't - and it seems unlikely that we can fix the filesystem to be case-insensitive again. Cheers, Michael Justin -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income Here lies Lester Moore Two bullets from a .44 No less, no more --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: install on maxosx 10.4 intel fails
On Nov 29, 2007, at 3:17 PM, mabshoff wrote: On Nov 30, 12:11 am, Justin C. Walker [EMAIL PROTECTED] wrote: On Nov 29, 2007, at 6:41 AM, joel wrote: The tarball seems to be the culprit. I can't see how this will work (from tar tvzf): lrwxrwxrwx was/daemon0 2007-11-21 16:30 sage-2.8.13-i386- Darwin/local/LIB - lib So can we nuke that symbolic link somehow? This should work: - uncompress the tarball - tar -f tarball --delete sage-2.8.13-i386-Darwin/local/LIB - compress again How was this built? Is someone using case-sensitivity on Mac OS X? Tsk tsk tsk... :) - William rolled the tarball. I believe he build that binary on fermat which is different from the box he used to roll tarballs on. We don't have admin control on fermat - at least I don't - and it seems unlikely that we can fix the filesystem to be case-insensitive again. For sure you won't get away with changing the sensitivity of the filesystem :-} (without a backup/restore process). You just have to beware of the trials of case-insensitivity. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income Experience is what you get when you don't get what you want. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: install on maxosx 10.4 intel fails
On Nov 30, 12:31 am, Justin C. Walker [EMAIL PROTECTED] wrote: On Nov 29, 2007, at 3:17 PM, mabshoff wrote: On Nov 30, 12:11 am, Justin C. Walker [EMAIL PROTECTED] wrote: On Nov 29, 2007, at 6:41 AM, joel wrote: The tarball seems to be the culprit. I can't see how this will work (from tar tvzf): lrwxrwxrwx was/daemon0 2007-11-21 16:30 sage-2.8.13-i386- Darwin/local/LIB - lib So can we nuke that symbolic link somehow? This should work: - uncompress the tarball - tar -f tarball --delete sage-2.8.13-i386-Darwin/local/LIB - compress again joel, please try http://sage.math.washington.edu/home/mabshoff/sage-2.8.13-osx10.4-i386-Darwin.tar.gz with 60dd1afb54e093f3c3859274c1aa8dc7 /home/mabshoff/sage-2.8.13-osx10.4- i386-Darwin.tar.gz If this works: William, can you please update the tarball on sagemath.org and mirror it out. 2.8.15 will be out anyways in a couple days, but it might still be worth it. It is also a good idea to make sure that the issue with the symbolic link doesn't happen again. How was this built? Is someone using case-sensitivity on Mac OS X? Tsk tsk tsk... :) - William rolled the tarball. I believe he build that binary on fermat which is different from the box he used to roll tarballs on. We don't have admin control on fermat - at least I don't - and it seems unlikely that we can fix the filesystem to be case-insensitive again. I am an idiot, that box is PPC, but since William updated bsd to 10.5 he is using some other MacIntel to do the 10.4 binaries. Cheers, Michael For sure you won't get away with changing the sensitivity of the filesystem :-} (without a backup/restore process). You just have to beware of the trials of case-insensitivity. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income Experience is what you get when you don't get what you want. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Changing basis in Free Modules (Disguising my question Changing basis in finite fields)
Dear Sage Supporters, As nobody continued to pay attention to the question I asked in sept 3 about how I want to change the field basis permanently, I am using john Cremona's idea to ask my question in another way, in hope to attract more attention: Suppose k is a field. Let define ring k[x]. I extend this ring by adding variable 't' and taking quotient by polynomial 't^4 + t^3 + t^2 + t + 1'. So, I have the ring k[x][t]/(t^4 + t^3 + t^2 + t + 1) which is a free module over k[x]. But again sage use default basis (1, t, t^2, t^3) to represent this ring over k[x]: sage: k = GF(2); sage: R = k['x']; x = R.gen() sage: S = R['t']; t = S.gen() sage: SBar = S.quotient(t^4 + t^3 + t^2 + t + 1, 'a'); a = SBar.gen() sage: print x*a^4 x*a^3 + x*a^2 + x*a + x How can I change this basis to normal basis, so I get: sage: print x*a^4 x*a^4 Thank you very much for your attention. Ahmad --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
