[sage-support] Re: Error related with singular, gap and resultant
Dear William, On Mar 5, 11:51 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > OK, I just tried to replicate your problem above on sage.math (64-bit linux), > 32-bit athlon linux, and 32-bit OS X 10.5, and in every case your code above > works fine -- i.e., nothing goes wrong.Can you really reliably replicate > this problem from a clean start of Sage? Meanwhile i tried on a different machine, and you are right: It seems to be machine dependent. Below are informations about OS and CPU. Concerning your guess that the Singular process may have crashed: How can i find out if this is the case? Yours Simon - The error occurs for sage 2.10.2 and 2.10.3.rc1 (installed from source) in a replicable way (after any restart of sage) in the setting > uname -a Linux mpc739 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux > cat /etc/issue Welcome to openSUSE 10.2 (X86-64) - Kernel \r (\l). > cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 55 model name : AMD Athlon(tm) 64 Processor 3700+ stepping: 2 cpu MHz : 1000.000 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up pni lahf_lm bogomips: 2011.52 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp --- The error does *not* occur for sage 2.10.2 (optained from sage - upgrade) in the setting > uname -a Linux mpc721 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux > cat /etc/issue Welcome to openSUSE 10.2 (X86-64) - Kernel \r (\l). > cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : Dual Core AMD Opteron(tm) Processor 270 stepping: 2 cpu MHz : 2000.000 cache size : 1024 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips: 3989.50 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : Dual Core AMD Opteron(tm) Processor 270 stepping: 2 cpu MHz : 2000.000 cache size : 1024 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips: 3989.50 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp processor : 2 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : Dual Core AMD Opteron(tm) Processor 270 stepping: 2 cpu MHz : 1800.000 cache size : 1024 KB physical id : 1 siblings: 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips: 3590.55 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp processor : 3 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : Dual Core AMD Opteron(tm) Processor 270 stepping: 2 cpu MHz : 1800.000 cache size : 1024 KB physical id : 1 siblings: 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips: 3590.55 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 b
[sage-support] FreeBSD Linux Emulation
I've had some luck running the sage-2.10.2-linux-32bit-debian-i686-Linux
binaries under FreeBSD 6.3-RELEASE (manually upgraded) using linux emulation
(linux_base-fc-4_10 = fedora core 4.10 distribution files); basic calculus
and arithmetic work from the interactive shell, the notebook runs with 3D
and Tachyon plotting, jsmath, etc.
What I did:
* make sure linux kernel module was compiled into FreeBSD and is loaded
with kldstat; I also had linprocfs but i'm not sure it's required.
* install emulators/linux_base
* as root symbolically link /usr/bin/bash to /bin/bash in freeBSD
* unzip/tar sage-2.10.2-linux-32bit-debian-i686-Linux.tar.gz, enter dir,
edit 'sage' to set SAGE_ROOT
* run ./sage
I didn't even have to use brandelf!
The biggest problem i'm having now is the same as Petr Muzikar from an old
sage-newbie post:
http://groups.google.com/group/sage-newbie/browse_thread/thread/8bb27a07e5c3
1c08
Basically when trying to plot() from shell or notebook matplotlib throws an
integer literal error (trace at end of email). I haven't really tried
debugging this yet; is there a known solution or should I dig in?
I also tried compiling sage-2.10.{1,2} from sources following the wiki
(http://wiki.sagemath.org/freebsd) and had a variety of issues (atlas,
lapack, ...); I tried swapping in the lapack i'd compiled previously for
scipy but had no love. I don't have good debug info about that now, i'll be
more precise when I have more time (those ATLAS compiles are
piinful).
Would it be appropriate for me to start a freebsd wiki page on the trac?
Should I submit new tickets for compilation problems/patches/workarounds or
just glom on to #1638?
-bryan
##
plot() issue (from notebook):
> plot(lambda a: sin(.3*a),(0.01,0.99))
Traceback (most recent call last):
File "", line 1, in
File "/usr/home/bnewbold/.sage/sage_notebook/worksheets/admin/0/code/7.py",
line 4, in
plot(lambda a:
sin(RealNumber(\u0027.3\u0027)*a),(RealNumber(\u00270.01\u0027),RealNumber(\u00270.99\u0027)))
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/sympy/plotting/",
line 1, in
File "sage_object.pyx", line 92, in
sage.structure.sage_object.SageObject.__repr__
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/sage/plot/plot.py",
line 734, in _repr_
self.show()
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/sage/plot/plot.py",
line 1242, in show
aspect_ratio=aspect_ratio)
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/sage/plot/plot.py",
line 1342, in save
from matplotlib.figure import Figure
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/figure.py",
line 10, in
from axes import Axes, Subplot, PolarSubplot, PolarAxes
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/axes.py",
line 13, in
from matplotlib import axis as maxis
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/axis.py",
line 20, in
from font_manager import FontProperties
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/font_manager.py",
line 1129, in
_rebuild()
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/font_manager.py",
line 1120, in _rebuild
fontManager = FontManager()
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/font_manager.py",
line 910, in __init__
self.afmdict = createFontDict(self.afmfiles, fontext='afm')
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/font_manager.py",
line 509, in createFontDict
font = afm.AFM(fh)
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/afm.py",
line 294, in __init__
parse_afm(fh)
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/afm.py",
line 282, in parse_afm
dcmetrics_ascii, dcmetrics_name = _parse_char_metrics(fh)
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/afm.py",
line 167, in _parse_char_metrics
bbox = _to_list_of_ints(vals[3][2:])
File
"/home/bnewbold/code/sage/sage-2.10.2-linux-32bit-debian-i686-Linux/local/lib/python2.5/site-packages/matplotlib/afm.py",
line 47, in _to_list_of_ints
return [_to_int(val) for val in s.split()]
ValueError: invalid li
[sage-support] Re: Spline question
On Wed, Mar 5, 2008 at 8:10 PM, dean moore <[EMAIL PROTECTED]> wrote: > Well, I've been tempted to do something with a machine gun ... > > Grabbed m4-1.4.10 & unpacked it. Still get the same error, "SAGE BUILD > ERROR: > Command 'm4' not found" when cd-ing into sage's directory & typing make, as > described > in the installation guide. > > Seems to unpack m4 "right there," and not in another directory. Thinking of > questions of > finding it, tried unpacking in sage's directory. Ditto. Something with my > path? Won't let > me put it in root directory. > > Also tried sudo apt-get install m4. "Couldn't find package m4." Did you put a period at the end of the command line? Did you setup apt ever? You may have to edit /etc/apt/sources.list > Shouldn't this stuff come with ubuntu 7.10? No, it is a compiler tool, and the Ubuntu CD is a fairly minimal Linux install --it's just what you need to get work done, not to build new software. You'll need these packages: g++, make, m4, ranlib William > Dean > > --- > > > > On Wed, Mar 5, 2008 at 4:05 PM, William Stein <[EMAIL PROTECTED]> wrote: > > > > On Wed, Mar 5, 2008 at 12:31 PM, dean moore <[EMAIL PROTECTED]> > wrote: > > > Not sending this to the whole group -- no reason. > > > > > > Sure, will document it let you know when I have something "nice." The > word > > > "spline" > > > seems to occur in two pages I find. > > > > Thanks! > > > > > > > > > > In other news, I finally dual-booted my computer Microsoft-Linux & was > > > trying to install > > > sage from source. No m4. Running Ubuntu 7.10. I type which m4 in a > > > terminal & next > > > line is blank. > > > > > > While it's not a big deal to grab a package & install it, I want to make > > > sure I have the > > > right thing. Is this the m4 referred at < > > > http://en.wikipedia.org/wiki/GNU_m4 >? What > > > I'm guessing; please correct me be I wrong. > > > > > > Might be another documentation thing. My first searches led me to a > machine > > > gun, > > > probably not a component of sage. > > > > Yes, you need the m4 mentioned above. There may be other packages > > you need -- refer to the README.txt. Do > > > > [EMAIL PROTECTED]:~$ sudo apt-get install m4 > > > > to install m4 on ubuntu. Unfortunately, at present a machine gun > > can't be used in lieu m4 when building Sage. > > > > -- William > > > > > > > > > > > > > > > > > > > > On Wed, Mar 5, 2008 at 1:13 PM, William Stein <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 5, 2008 at 10:57 AM, dean moore <[EMAIL PROTECTED]> > > > wrote: > > > > > Thanks! That worked nicely. > > > > > > > > > > But should this type of thing be documented, as others may face > this? > > > > > > > > > > Dean > > > > > > > > > > > > > Sure! Could you just take the current docs for spline?, modifying > them > > > the > > > > way you wish they were regarding the above issues, and put the result > > > > as a response to this email? > > > > > > > > William > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > William Stein > > Associate Professor of Mathematics > > University of Washington > > http://wstein.org > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: MAC PC configuration problem.
On Wed, Mar 5, 2008 at 6:31 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > > William Stein wrote: > > On Wed, Mar 5, 2008 at 7:55 AM, Neal Laurance <[EMAIL PROTECTED]> wrote: > >> I have just installed SAGE on my MAC book, and it works fine there. But > >> I would like to use it from my desk PC (Windows XP). The PC has a bigger > >> display. I opened Firefox on the PC, entered the local IP address of the > >> MAC (192.168.1.103) and I get an acknowledgment from the Apache Web > >> server. Then I tried 192.168.1.103:8000, trying to connect with the SAGE > >> session running on my MAC. No luck. It times out. > > > > You *must* explicitly start the notebook like this: > > > > sage: notebook(address="192.168.1.103") > > > > where 192.168.1.103 is the external address of your laptop. > > If you don't do this the notebook will _only_ listen to connection > > from localhost (i.e., your laptop), as a security precaution. > > > That's funny. Just typing notebook() lets me access from a remote > server just fine! Is that a bug? Yes, and a really scary one at that. Out of curiosity do you have the same behavior if you do: sage: notebook(secure=False) That would be _actually_ scary. > > Neal, make sure you are going to https://192.168... (note the https). > > Jason > > > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: MAC PC configuration problem.
William Stein wrote: > On Wed, Mar 5, 2008 at 7:55 AM, Neal Laurance <[EMAIL PROTECTED]> wrote: >> I have just installed SAGE on my MAC book, and it works fine there. But >> I would like to use it from my desk PC (Windows XP). The PC has a bigger >> display. I opened Firefox on the PC, entered the local IP address of the >> MAC (192.168.1.103) and I get an acknowledgment from the Apache Web >> server. Then I tried 192.168.1.103:8000, trying to connect with the SAGE >> session running on my MAC. No luck. It times out. > > You *must* explicitly start the notebook like this: > > sage: notebook(address="192.168.1.103") > > where 192.168.1.103 is the external address of your laptop. > If you don't do this the notebook will _only_ listen to connection > from localhost (i.e., your laptop), as a security precaution. That's funny. Just typing notebook() lets me access from a remote server just fine! Is that a bug? Neal, make sure you are going to https://192.168... (note the https). Jason --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mixed 32/64 bit .o files under Linux PowerPC
On Wed, Mar 5, 2008 at 4:40 PM, Sameer <[EMAIL PROTECTED]> wrote: > > William, > Thanks a lot for your suggestion. I had not set it. Some more > problems with the compile on powerpc Linux. I get: > ./lisp.run -on-error appease -B . -N locale -E 1:1 -Efile UTF-8 - > Eterminal UTF-8 -norc -m 1800KW -x "(and (load \"init.lisp\") (sys:: > %saveinitmem) (ext::exit)) (ext::exit t)" > i i i i i i i ooooo o o > I I I I I I I 8 8 8 8 8 o 88 > I \ `+' / I 8 8 8 888 >\ `-+-' / 8 8 8 o 8 > `-__|__-'8 8 8 8 8 > |8 o 8 8 o 8 8 > --+-- o8oo ooo8ooo o 8 > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > Copyright (c) Sam Steingold, Bruno Haible 2001-2006 > > ;; Loading file defseq.lisp ... > ;; Loaded file defseq.lisp > ;; Loading file backquote.lisp ... > ;; Loaded file backquote.lispmake[2]: *** [interpreted.mem] > Segmentation fault > > make[2]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > build/clisp-2.41.p12/src/src' > Silly permissions error with first make of clisp. > Do a 'make' again, since second 'make' works. > Error building clisp. > > real30m10.186s > user29m17.033s > sys 0m42.184s > sage: An error occurred while installing clisp-2.41.p12 > > Please email sage-devel http://groups.google.com/group/sage-devel > explaining the problem and send the relevant part of > of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your > computer, operating system, etc. > If you want to try to fix the problem, yourself *don't* just cd to > /usr/local/PET/src/build/sage-2.10.2/spkg/build/clisp-2.41.p12 and > > type 'make'. > Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" > in order to set all environment variables correctly, then cd to > /usr/local/PET/src/build/sage-2.10.2/spkg/build/clisp-2.41.p12 > > (When you are done debugging, you can type "exit" to leave the > subshell.) > make[1]: *** [installed/clisp-2.41.p12] Error 1 > > make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' > > real98m24.666s > user95m9.979s > sys 2m30.678s > + '[' all = all -a 2 = 0 ']' It's a bummer clisp didn't build. We only use it for maxima, so if you can install any version of clisp on your system (e.g., using your normal package tools), then sage will use that to build Maxima. There is no binary linking between sage and maxima/clisp, however you won't get far in Sage without having maxima on your system. > build/sage-2.10.2> > > next. If I try and execute the sage executable at this stage, I get: > build/sage-2.10.2> /usr/local/PET/src/build/sage-2.10.2/sage > -- > | SAGE Version 2.10.2, Release Date: 2008-02-22 | > | Type notebook() for the GUI, and license() for information.| > -- > Setting permissions of DOT_SAGE directory so only you can read and > write it. > > init2.c:37: assertion failed: ((64 - 0)+0) == (((64 - 0)+0)/8) * 8 && > sizeof(mp_limb_t) == (((64 - 0)+0)/8) > /usr/local/PET/src/build/sage-2.10.2/local/bin/sage-sage: line 212: > 13965 Segmentation fault sage-ipython -c "$SAGE_STARTUP_COMMAND;" > "$@" That's gmp, since init2.c is: gmp-4.2.1/mpz/init2.c It seems that something is miscompiled about your gcc. I'm sure this has something to do with 64/32-bit issues. Which Linux distribution are you using? Maybe you could switch to Debian, which might be saner than whatever you are currently using. > > build/sage-2.10.2> > >Thanks, >- Sameer > > > On Mar 5, 2:42 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > > > On Wed, Mar 5, 2008 at 1:45 PM, Sameer <[EMAIL PROTECTED]> wrote: > > > > > Hi Michael, > > >The other problem I am facing on powerpc Linux is with compiling > > > with Fortran. Some parts of SAGE accept gfortran and others do not. > > > > It is definitely possible to build all of Sage only using gfortran, since > many > > people do that (who want to avoid g95 binaries for example). Did you > > set SAGE_FORTRAN and SAGE_FORTAN_LIB? > > > > That said, of course we have _not_ ported Sage officially to ppc 64bit > linux, > > so expect troubles. > > > > By the way, you can skip building any component of Sage by simplying > > touching a certain file (which tells Sage that the component built, even > > if it didn't). e.g., try this: > > > >cd SAGE_ROOT > >touch spkg/installed/r-2.6.1.p14 >
[sage-support] Re: Mixed 32/64 bit .o files under Linux PowerPC
William, Thanks a lot for your suggestion. I had not set it. Some more problems with the compile on powerpc Linux. I get: ./lisp.run -on-error appease -B . -N locale -E 1:1 -Efile UTF-8 - Eterminal UTF-8 -norc -m 1800KW -x "(and (load \"init.lisp\") (sys:: %saveinitmem) (ext::exit)) (ext::exit t)" i i i i i i i ooooo o o I I I I I I I 8 8 8 8 8 o 88 I \ `+' / I 8 8 8 888 \ `-+-' / 8 8 8 o 8 `-__|__-'8 8 8 8 8 |8 o 8 8 o 8 8 --+-- o8oo ooo8ooo o 8 Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2006 ;; Loading file defseq.lisp ... ;; Loaded file defseq.lisp ;; Loading file backquote.lisp ... ;; Loaded file backquote.lispmake[2]: *** [interpreted.mem] Segmentation fault make[2]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ build/clisp-2.41.p12/src/src' Silly permissions error with first make of clisp. Do a 'make' again, since second 'make' works. Error building clisp. real30m10.186s user29m17.033s sys 0m42.184s sage: An error occurred while installing clisp-2.41.p12 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem, yourself *don't* just cd to /usr/local/PET/src/build/sage-2.10.2/spkg/build/clisp-2.41.p12 and type 'make'. Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" in order to set all environment variables correctly, then cd to /usr/local/PET/src/build/sage-2.10.2/spkg/build/clisp-2.41.p12 (When you are done debugging, you can type "exit" to leave the subshell.) make[1]: *** [installed/clisp-2.41.p12] Error 1 make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' real98m24.666s user95m9.979s sys 2m30.678s + '[' all = all -a 2 = 0 ']' build/sage-2.10.2> next. If I try and execute the sage executable at this stage, I get: build/sage-2.10.2> /usr/local/PET/src/build/sage-2.10.2/sage -- | SAGE Version 2.10.2, Release Date: 2008-02-22 | | Type notebook() for the GUI, and license() for information.| -- Setting permissions of DOT_SAGE directory so only you can read and write it. init2.c:37: assertion failed: ((64 - 0)+0) == (((64 - 0)+0)/8) * 8 && sizeof(mp_limb_t) == (((64 - 0)+0)/8) /usr/local/PET/src/build/sage-2.10.2/local/bin/sage-sage: line 212: 13965 Segmentation fault sage-ipython -c "$SAGE_STARTUP_COMMAND;" "$@" build/sage-2.10.2> Thanks, - Sameer On Mar 5, 2:42 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Mar 5, 2008 at 1:45 PM, Sameer <[EMAIL PROTECTED]> wrote: > > > Hi Michael, > > The other problem I am facing on powerpc Linux is with compiling > > with Fortran. Some parts of SAGE accept gfortran and others do not. > > It is definitely possible to build all of Sage only using gfortran, since many > people do that (who want to avoid g95 binaries for example). Did you > set SAGE_FORTRAN and SAGE_FORTAN_LIB? > > That said, of course we have _not_ ported Sage officially to ppc 64bit linux, > so expect troubles. > > By the way, you can skip building any component of Sage by simplying > touching a certain file (which tells Sage that the component built, even > if it didn't). e.g., try this: > > cd SAGE_ROOT > touch spkg/installed/r-2.6.1.p14 > > then type make to continue your Sage install. It will fail with rpy, > but you can also skip that similiarly. R and rpy do not link with > Sage in a binary way, so you should be able to build all the rest > of Sage after skipping the build of R and rpy, and then you can get > going with actually using Sage, then come back to R/Rpy if you're > particularly interested in Statistics (that's what those packages > are for). > > > Here is what I see: > > checking for Fortran 77 libraries of sage_fortran... > > checking how to get verbose linking output from gcc -std=gnu99... -v > > checking for C libraries of gcc -std=gnu99... -L/usr/local/PET/src/ > > build/sage-2.10.2/local/lib/ -L/usr/local/PET/src/build/sage-2.10.2/ > > local/lib/../lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2 -L/usr/lib/ > > gcc/powerpc64-suse-linux/4.1.2/../../../../powerpc64-suse-linux/lib/../ > > lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib -L/ > > lib/../lib -L/usr/lib/../lib
[sage-support] Re: Minimum installation size
On Mar 5, 2008, at 2:47 PM, Martin Albrecht wrote: > >> A couple of questions: >> >> What's the problem with deleting static libraries after the build? >> They aren't used once the compilation is done. > > If you touch e.g. integer.pyx and "sage -b" you'll need libgmp.a, > that's all. > If nothing gets ever compiled you are good. However, adding a block > "%cython" > to the notebook is sufficient to trigger a compilation. Ah, rats. Of course. But for those not interested in *any* development, or who are just 'python' (not 'cython') hackers, they won't be needed. You are right...removing static libraries is a touchy area. >> Also: I don't think you can strip dynamic libraries safely. Maybe >> the "non-external" symbols, if your linker/librarian supports it. >> Did I misunderstand your suggestion? > > Really? So "strip *.so" will break something? I didn't know that. Try it on a friend's system: strip /usr/lib/libc.so :=} If you do, better have a clear path to the door... Dynamic libraries are referenced all the time during an app's execution. Anytime it makes a (new) library call, it is made through a 'stub' that invokes the dynamic loader to fix it up and bind it to an address in the library (so subsequent calls are direct). That requires the symbol table of the library be intact. The details vary between systems, but that's the basic idea. FWIW, some tool chains let you strip "non-essential" symbols (those not needed for linking), and that might be worth exploring. I don't know that all 'strip' mechanisms support this. Most Unixy systems have this capability. Check the man pages. Justin -- Justin C. Walker, Curmudgeon-At-Large, Director Institute for the Enhancement of the Director's Income The path of least resistance: it's not just for electricity any 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: mympi in addition to mpi4py as optional package in sage?
On Wed, Mar 5, 2008 at 7:22 AM, AEatUALR <[EMAIL PROTECTED]> wrote: > > Do you see the mympi python/mpi module showing up as an optional > package in sage? > > http://peloton.sdsc.edu/~tkaiser/mympi/ > > I see openmpi and mpi4py there (which is great). Do you have any interest in being the official maintainer of the mympi spkg for sage? Do you actually use mympi with Sage right now? Just curious. A minimum for something to be an optional spkg is that there is actual demand, e.g., by more than 0 users. william --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Spline question
On Wed, Mar 5, 2008 at 12:31 PM, dean moore <[EMAIL PROTECTED]> wrote: > Not sending this to the whole group -- no reason. > > Sure, will document it let you know when I have something "nice." The word > "spline" > seems to occur in two pages I find. Thanks! > > In other news, I finally dual-booted my computer Microsoft-Linux & was > trying to install > sage from source. No m4. Running Ubuntu 7.10. I type which m4 in a > terminal & next > line is blank. > > While it's not a big deal to grab a package & install it, I want to make > sure I have the > right thing. Is this the m4 referred at < > http://en.wikipedia.org/wiki/GNU_m4 >? What > I'm guessing; please correct me be I wrong. > > Might be another documentation thing. My first searches led me to a machine > gun, > probably not a component of sage. Yes, you need the m4 mentioned above. There may be other packages you need -- refer to the README.txt. Do [EMAIL PROTECTED]:~$ sudo apt-get install m4 to install m4 on ubuntu. Unfortunately, at present a machine gun can't be used in lieu m4 when building Sage. -- William > > > > On Wed, Mar 5, 2008 at 1:13 PM, William Stein <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > On Wed, Mar 5, 2008 at 10:57 AM, dean moore <[EMAIL PROTECTED]> > wrote: > > > Thanks! That worked nicely. > > > > > > But should this type of thing be documented, as others may face this? > > > > > > Dean > > > > > > > Sure! Could you just take the current docs for spline?, modifying them > the > > way you wish they were regarding the above issues, and put the result > > as a response to this email? > > > > William > > > > > > > > > > > > > > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Error related with singular, gap and resultant
On Wed, Mar 5, 2008 at 1:38 PM, Simon King <[EMAIL PROTECTED]> wrote:
>
> Dear sage supporters,
>
> a strange error occurs in sage 2.10.2 in the following way:
>
> sage: R. = QQ[]
> sage: f = x^3 + x + 1; g = x^3 - x - 1
> sage: r = f.resultant(g)
> sage: R.__dict__
> {'_PolynomialRing_general__cyclopoly_cache': {},
> '_PolynomialRing_general__generator': x,
> '_PolynomialRing_general__is_sparse': False,
> '_PolynomialRing_general__polynomial_class':
> 'sage.rings.polynomial.polynomial_element_generic.Polynomial_rational_dense'>,
> '_PolynomialRing_singular_repr__singular': // characteristic : 0
> // number of vars : 1
> //block 1 : ordering lp
> // : namesx
> //block 2 : ordering C,
> '_has_singular': True}
>
> Ok so far. Now we use the gap interface and experience a bad surprise:
>
> sage: gap(R.base_ring())
> Rationals
> sage: R.__dict__
> {'_PolynomialRing_general__cyclopoly_cache': {},
> '_PolynomialRing_general__generator': x,
> '_PolynomialRing_general__is_sparse': False,
> '_PolynomialRing_general__polynomial_class':
> 'sage.rings.polynomial.polynomial_element_generic.Polynomial_rational_dense'>,
> '_PolynomialRing_singular_repr__singular': print(sage0);
> // characteristic : 0
> // number of vars : 1
> //block 1 : ordering lp
> // : namesx
> //block 2 : ordering C,
> '_has_singular': True}
>
> See how R.__dict__['PolynomialRing_singular_repr__singular'] has
> changed!
> In the first part of the session, it contained a ring, but now it
> contains print(sage0).
>
> Even worse: Although sage0 used to be the identifier of the singular
> ring associated with R, we now get
> sage: singular('sage0')
> print(sage8);
> sage: sage: singular('sage0')
> print(sage9);
> sage: sage: singular('sage0')
> print(sage10);
> and so on!
>
> So, the singular interface seems to be completely messed up. I have no
> idea where this behaviour comes from.
>
> Note that the line
> sage: r = f.resultant(g)
> is essential. When this line is replaced by, e.g.,
> sage: singular(R)
> the error does not occur. Also, when we first say gap(R.base_ring())
> and then compute the resultant, everything is alright.
>
> Perhaps this helps to detect the bug.
>
> Any idea? Shall i open a ticket?
OK, I just tried to replicate your problem above on sage.math (64-bit linux),
32-bit athlon linux, and 32-bit OS X 10.5, and in every case your code above
works fine -- i.e., nothing goes wrong.Can you really reliably replicate
this problem from a clean start of Sage?What is your exact hardware
and OS? The error behavior you get suggests to me that maybe the Singular
process crashes and is restarted or something like that, but I'm not sure...
Regarding whether or not your problem would be a bug,
*anything* that's not obviously supposed to mess up the interfaces
that does mess them up (without a big error appearing) is a bug,
and I want to fix it. I'm really glad if you can reliably replicate the
problem, since that makes it vastly easier to fix.
William
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Minimum installation size
> A couple of questions: > > What's the problem with deleting static libraries after the build? > They aren't used once the compilation is done. If you touch e.g. integer.pyx and "sage -b" you'll need libgmp.a, that's all. If nothing gets ever compiled you are good. However, adding a block "%cython" to the notebook is sufficient to trigger a compilation. > Also: I don't think you can strip dynamic libraries safely. Maybe > the "non-external" symbols, if your linker/librarian supports it. > Did I misunderstand your suggestion? Really? So "strip *.so" will break something? I didn't know that. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _www: http://www.informatik.uni-bremen.de/~malb _jab: [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
Jason Grout wrote: > William Stein wrote: >> On Wed, Mar 5, 2008 at 2:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote: >>> dean moore wrote: >>> > When I was writing some other code this came out; finally decided to >>> > report it. Do the following >>> > in an online SAGE notebook: >>> > >>> > /1+1/ >>> > >>> > We get two. Now run the following: >>> > >>> > /# Limaçon >>> > 1+1 >>> > / >>> > Get: >>> > >>> > /Exception (click to the left for traceback): >>> > ... >>> > SyntaxError: Non-ASCII character '\xe7' in file >>> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but >>> > no encoding declared; see http://www.python.org/peps/pep-0263.html for >>> > details >>> > >>> > Traceback (most recent call last): >>> > File "", line 1, in >>> > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4 >>> > SyntaxError: Non-ASCII character '\xe7' in file >>> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but >>> > no encoding declared; see http://www.python.org/peps/pep-0263.html for >>> > details/ >>> > >>> > --- >>> > >>> > /Sacre bleu!/ It's in a comment! Looking at the error & the web site >>> > it may be a Python thing & untouchable. >>> > But can we get around this? Shouldn't our French friends (and countless >>> > others) be able to use SAGE? >>> >>> >>> Apparently we can set the encoding of a python source file with a >>> comment like: >>> >>> # -*- coding: utf_8 -*- >>> >>> at the very top of the file (It seems like it has to be pretty much the >>> first line). >>> >>> Are there any comments about automatically adding this (or utf_16?) to >>> the top of all of the notebook files? >> Please definitely add this. Make a trac ticket asap for it. Thanks!! > > Done! > > The patch is up at http://trac.sagemath.org/sage_trac/ticket/2399 > Does someone want to review the patch positively? Maybe someone can even convince mabshoff to apply it to 2.10.3 :) Now we can make a demo with a notebook that has some very weird utf8 characters in it to show how Sage reaches out to the world via the web interface (well, now=after patch is applied). Something with very different-looking characters would be a nice visual demonstration, like thai or cambodian or chinese or japanese characters. Jason --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
On Wed, Mar 5, 2008 at 5:37 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
>
>
> didier deshommes wrote:
> > On Wed, Mar 5, 2008 at 5:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
> >>
> >> dean moore wrote:
> >> > When I was writing some other code this came out; finally decided to
> >> > report it. Do the following
> >> > in an online SAGE notebook:
> >> >
> >> > /1+1/
> >> >
> >> > We get two. Now run the following:
> >> >
> >> > /# Limaçon
> >> > 1+1
> >> > /
> >> > Get:
> >> >
> >> > /Exception (click to the left for traceback):
> >> > ...
> >> > SyntaxError: Non-ASCII character '\xe7' in file
> >> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
> >> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
> >> > details
> >> >
> >> > Traceback (most recent call last):
> >> > File "", line 1, in
> >> > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line
> 4
> >> > SyntaxError: Non-ASCII character '\xe7' in file
> >> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
> >> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
> >> > details/
> >> >
> >> > ---
> >> >
> >> > /Sacre bleu!/ It's in a comment! Looking at the error & the web site
> >> > it may be a Python thing & untouchable.
> >> > But can we get around this? Shouldn't our French friends (and
> countless
> >> > others) be able to use SAGE?
> >>
> >>
> >> Apparently we can set the encoding of a python source file with a
> >> comment like:
> >>
> >> # -*- coding: utf_8 -*-
> >>
> >> at the very top of the file (It seems like it has to be pretty much the
> >> first line).
> >>
> >> Are there any comments about automatically adding this (or utf_16?) to
> >> the top of all of the notebook files?
> >
> > You can also use the codecs module to handle this:
> > codecs.open('stuff.txt','wb','utf-8')
> >
> > opens the file for writing with this encoding in mind.
>
>
> Is this better? The patch at #2399 does the magic comment trick. That
> way, the encoding is part of the file, so the file is valid python in
> and of itself.
Frankly I don't know (and didn't realize you had already posted the
patch). Unless python3.0's internals change for reading files, yours
should work.
didier
>
>
>
> Jason
>
>
> >
>
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
On Wed, Mar 5, 2008 at 2:37 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
>
>
> didier deshommes wrote:
> > On Wed, Mar 5, 2008 at 5:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
> >>
> >> dean moore wrote:
> >> > When I was writing some other code this came out; finally decided to
> >> > report it. Do the following
> >> > in an online SAGE notebook:
> >> >
> >> > /1+1/
> >> >
> >> > We get two. Now run the following:
> >> >
> >> > /# Limaçon
> >> > 1+1
> >> > /
> >> > Get:
> >> >
> >> > /Exception (click to the left for traceback):
> >> > ...
> >> > SyntaxError: Non-ASCII character '\xe7' in file
> >> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
> >> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
> >> > details
> >> >
> >> > Traceback (most recent call last):
> >> > File "", line 1, in
> >> > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line
> 4
> >> > SyntaxError: Non-ASCII character '\xe7' in file
> >> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
> >> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
> >> > details/
> >> >
> >> > ---
> >> >
> >> > /Sacre bleu!/ It's in a comment! Looking at the error & the web site
> >> > it may be a Python thing & untouchable.
> >> > But can we get around this? Shouldn't our French friends (and
> countless
> >> > others) be able to use SAGE?
> >>
> >>
> >> Apparently we can set the encoding of a python source file with a
> >> comment like:
> >>
> >> # -*- coding: utf_8 -*-
> >>
> >> at the very top of the file (It seems like it has to be pretty much the
> >> first line).
> >>
> >> Are there any comments about automatically adding this (or utf_16?) to
> >> the top of all of the notebook files?
> >
> > You can also use the codecs module to handle this:
> > codecs.open('stuff.txt','wb','utf-8')
> >
> > opens the file for writing with this encoding in mind.
>
>
> Is this better? The patch at #2399 does the magic comment trick. That
> way, the encoding is part of the file, so the file is valid python in
> and of itself.
>
I think your solution at #2399 is better.
William
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Mixed 32/64 bit .o files under Linux PowerPC
On Wed, Mar 5, 2008 at 1:45 PM, Sameer <[EMAIL PROTECTED]> wrote: > > Hi Michael, >The other problem I am facing on powerpc Linux is with compiling > with Fortran. Some parts of SAGE accept gfortran and others do not. It is definitely possible to build all of Sage only using gfortran, since many people do that (who want to avoid g95 binaries for example). Did you set SAGE_FORTRAN and SAGE_FORTAN_LIB? That said, of course we have _not_ ported Sage officially to ppc 64bit linux, so expect troubles. By the way, you can skip building any component of Sage by simplying touching a certain file (which tells Sage that the component built, even if it didn't). e.g., try this: cd SAGE_ROOT touch spkg/installed/r-2.6.1.p14 then type make to continue your Sage install. It will fail with rpy, but you can also skip that similiarly. R and rpy do not link with Sage in a binary way, so you should be able to build all the rest of Sage after skipping the build of R and rpy, and then you can get going with actually using Sage, then come back to R/Rpy if you're particularly interested in Statistics (that's what those packages are for). > Here is what I see: > checking for Fortran 77 libraries of sage_fortran... > checking how to get verbose linking output from gcc -std=gnu99... -v > checking for C libraries of gcc -std=gnu99... -L/usr/local/PET/src/ > build/sage-2.10.2/local/lib/ -L/usr/local/PET/src/build/sage-2.10.2/ > local/lib/../lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2 -L/usr/lib/ > gcc/powerpc64-suse-linux/4.1.2/../../../../powerpc64-suse-linux/lib/../ > lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib -L/ > lib/../lib -L/usr/lib/../lib -L/usr/local/PET/src/build/sage-2.10.2/ > local/lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../ > powerpc64-suse-linux/lib -L/usr/lib/gcc/powerpc64-suse-linux/ > 4.1.2/../../.. -lgcc_s > checking for dummy main to link with Fortran 77 libraries... none > checking for Fortran 77 name-mangling scheme... configure: error: > cannot compile a simple Fortran program > See `config.log' for more details. > Error configuring R. > > real0m57.989s > user0m23.697s > sys 0m23.042s > sage: An error occurred while installing r-2.6.1.p14 > > Please email sage-devel http://groups.google.com/group/sage-devel > explaining the problem and send the relevant part of > of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your > computer, operating system, etc. > If you want to try to fix the problem, yourself *don't* just cd to > /usr/local/PET/src/build/sage-2.10.2/spkg/build/r-2.6.1.p14 and type > > 'make'. > Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" > in order to set all environment variables correctly, then cd to > /usr/local/PET/src/build/sage-2.10.2/spkg/build/r-2.6.1.p14 > > (When you are done debugging, you can type "exit" to leave the > subshell.) > make[1]: *** [installed/r-2.6.1.p14] Error 1 > > make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' > > real44m44.649s > user41m19.765s > sys 2m49.245s > build/sage-2.10.2> which gfortran > /usr/bin/gfortran > build/sage-2.10.2> which g77 > g77: Command not found. > build/sage-2.10.2> which f77 > /opt/ibmcmp/xlf/10.1/bin/f77 > > build/sage-2.10.2> > > > > On Mar 4, 10:20 pm, "Michael.Abshoff" <[EMAIL PROTECTED]> > wrote: > > > > Sameer wrote: > > > Hi, > > > When I try to compile Sage 2.10.2 under ppc64 Linux using gcc, > > > I see that some files are > > > compiled in 32 bits and some others in 64 bits. Have you noticed this? > > > > Hi Sameer, > > > > there is several ways to solve the problem: > > > > a) Use a gcc that forces 64 bit output per default > > b) Wait until 2.10.4 and hope that I have time to merge all the 64 bit > > PPC fixes :) > > > > > > > > > When I type: > > > % make > > > I get the following error: > > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/PET/src/build/ > > > sage-2.10.2/local/include -I. -g -O2 -MT > > > libiml_la-nullspace.lo -MD -MP -MF .deps/libiml_la-nullspace.Tpo -c > > > nullspace.c -o > > > libiml_la-nullspace.o >/dev/null 2>&1 > > > /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/local/PET/src/build/ > > > sage-2.10.2/local/include -I. > > > -g -O2 -lm -o libiml.la -rpath /usr/local/PET/src/build/sage-2.10.2/ > > > local/lib libiml_la-basisop.lo > > > libiml_la-certsolve.lo libiml_la-error.lo libiml_la-latreduce.lo > > > libiml_la-memalloc.lo > > > libiml_la-mtrans.lo libiml_la-nonsysolve.lo libiml_la-padiclift.lo > > > libiml_la-reconsolu.lo > > > libiml_la-RNSop.lo libiml_la-nullspace.lo -L/usr/local/PET/src/build/ > > > sage-2.10.2/local/lib -lgmp > > > ../repl/librepl.la > > > gcc -shared .libs/libiml_la-basisop.o .libs/libiml_la- > > > certsolve.o .libs/libiml_la-error.o > > > .libs/libiml_la-latreduce.o .libs/libiml_la-memalloc.o .libs/libiml_la- > > > mtrans.o > > > .libs/libiml_
[sage-support] Re: SAGE chokes on French character
didier deshommes wrote:
> On Wed, Mar 5, 2008 at 5:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
>>
>> dean moore wrote:
>> > When I was writing some other code this came out; finally decided to
>> > report it. Do the following
>> > in an online SAGE notebook:
>> >
>> > /1+1/
>> >
>> > We get two. Now run the following:
>> >
>> > /# Limaçon
>> > 1+1
>> > /
>> > Get:
>> >
>> > /Exception (click to the left for traceback):
>> > ...
>> > SyntaxError: Non-ASCII character '\xe7' in file
>> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
>> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
>> > details
>> >
>> > Traceback (most recent call last):
>> > File "", line 1, in
>> > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4
>> > SyntaxError: Non-ASCII character '\xe7' in file
>> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
>> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
>> > details/
>> >
>> > ---
>> >
>> > /Sacre bleu!/ It's in a comment! Looking at the error & the web site
>> > it may be a Python thing & untouchable.
>> > But can we get around this? Shouldn't our French friends (and countless
>> > others) be able to use SAGE?
>>
>>
>> Apparently we can set the encoding of a python source file with a
>> comment like:
>>
>> # -*- coding: utf_8 -*-
>>
>> at the very top of the file (It seems like it has to be pretty much the
>> first line).
>>
>> Are there any comments about automatically adding this (or utf_16?) to
>> the top of all of the notebook files?
>
> You can also use the codecs module to handle this:
> codecs.open('stuff.txt','wb','utf-8')
>
> opens the file for writing with this encoding in mind.
Is this better? The patch at #2399 does the magic comment trick. That
way, the encoding is part of the file, so the file is valid python in
and of itself.
Jason
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: MAC PC configuration problem.
Hi Neal, When you start up the notebook on the Mac, pass the option server='192.168.1.103' and then you should able to access it on you Windows box by going to https://192.168.1.103:8000 . Let me know if that works. --Mike On Wed, Mar 5, 2008 at 8:06 AM, Neal <[EMAIL PROTECTED]> wrote: > > I have just installed SAGE on my MAC book, and it works fine there. > But I would like to use it from my desk PC (Windows XP). The PC has a > bigger display. I opened Firefox on the PC, entered the local IP > address of the MAC (192.168.1.103) and I get an acknowledgment from > the Apache Web server. Then I tried 192.168.1.103:8000, trying to > connect with the SAGE session running on my MAC. No luck. It times > out. > > I have tried variations like 192.168.1.103/localhost:8000 and several > other combinations, but no luck. The Apache response tells me > something is working; I just haven't managed to reach SAGE yet. > > > > --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
William Stein wrote: > On Wed, Mar 5, 2008 at 2:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote: >> >> dean moore wrote: >> > When I was writing some other code this came out; finally decided to >> > report it. Do the following >> > in an online SAGE notebook: >> > >> > /1+1/ >> > >> > We get two. Now run the following: >> > >> > /# Limaçon >> > 1+1 >> > / >> > Get: >> > >> > /Exception (click to the left for traceback): >> > ... >> > SyntaxError: Non-ASCII character '\xe7' in file >> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but >> > no encoding declared; see http://www.python.org/peps/pep-0263.html for >> > details >> > >> > Traceback (most recent call last): >> > File "", line 1, in >> > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4 >> > SyntaxError: Non-ASCII character '\xe7' in file >> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but >> > no encoding declared; see http://www.python.org/peps/pep-0263.html for >> > details/ >> > >> > --- >> > >> > /Sacre bleu!/ It's in a comment! Looking at the error & the web site >> > it may be a Python thing & untouchable. >> > But can we get around this? Shouldn't our French friends (and countless >> > others) be able to use SAGE? >> >> >> Apparently we can set the encoding of a python source file with a >> comment like: >> >> # -*- coding: utf_8 -*- >> >> at the very top of the file (It seems like it has to be pretty much the >> first line). >> >> Are there any comments about automatically adding this (or utf_16?) to >> the top of all of the notebook files? > > Please definitely add this. Make a trac ticket asap for it. Thanks!! Done! The patch is up at http://trac.sagemath.org/sage_trac/ticket/2399 Jason --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Minimum installation size
Hi, Martin, On Mar 5, 2008, at 8:58 AM, Martin Albrecht wrote: > On Wednesday 05 March 2008, Ryan Hinton wrote: >> What if I want to develop in certain sections (coding theory, maybe >> some graph theory)? > > I wouldn't recommend deleting static libraries because it is too > easy to shoot > yourself in the foot if you do. If you only strip your binaries/ > libraries > then you can still develop, you just won't get very nice backtraces > if Sage > crashes on you. A couple of questions: What's the problem with deleting static libraries after the build? They aren't used once the compilation is done. Also: I don't think you can strip dynamic libraries safely. Maybe the "non-external" symbols, if your linker/librarian supports it. Did I misunderstand your suggestion? 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
On Wed, Mar 5, 2008 at 5:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
>
>
> dean moore wrote:
> > When I was writing some other code this came out; finally decided to
> > report it. Do the following
> > in an online SAGE notebook:
> >
> > /1+1/
> >
> > We get two. Now run the following:
> >
> > /# Limaçon
> > 1+1
> > /
> > Get:
> >
> > /Exception (click to the left for traceback):
> > ...
> > SyntaxError: Non-ASCII character '\xe7' in file
> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
> > details
> >
> > Traceback (most recent call last):
> > File "", line 1, in
> > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4
> > SyntaxError: Non-ASCII character '\xe7' in file
> > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but
> > no encoding declared; see http://www.python.org/peps/pep-0263.html for
> > details/
> >
> > ---
> >
> > /Sacre bleu!/ It's in a comment! Looking at the error & the web site
> > it may be a Python thing & untouchable.
> > But can we get around this? Shouldn't our French friends (and countless
> > others) be able to use SAGE?
>
>
> Apparently we can set the encoding of a python source file with a
> comment like:
>
> # -*- coding: utf_8 -*-
>
> at the very top of the file (It seems like it has to be pretty much the
> first line).
>
> Are there any comments about automatically adding this (or utf_16?) to
> the top of all of the notebook files?
You can also use the codecs module to handle this:
codecs.open('stuff.txt','wb','utf-8')
opens the file for writing with this encoding in mind.
didier
>
> If there are no comments, I can post a patch for the notebook right away.
>
> Your example works with the above magic comment as the first line of a
> python file, but does not work if that comment is moved down one line.
>
> Jason
>
>
>
>
> >
>
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
On Wed, Mar 5, 2008 at 2:24 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > > > dean moore wrote: > > When I was writing some other code this came out; finally decided to > > report it. Do the following > > in an online SAGE notebook: > > > > /1+1/ > > > > We get two. Now run the following: > > > > /# Limaçon > > 1+1 > > / > > Get: > > > > /Exception (click to the left for traceback): > > ... > > SyntaxError: Non-ASCII character '\xe7' in file > > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but > > no encoding declared; see http://www.python.org/peps/pep-0263.html for > > details > > > > Traceback (most recent call last): > > File "", line 1, in > > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4 > > SyntaxError: Non-ASCII character '\xe7' in file > > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but > > no encoding declared; see http://www.python.org/peps/pep-0263.html for > > details/ > > > > --- > > > > /Sacre bleu!/ It's in a comment! Looking at the error & the web site > > it may be a Python thing & untouchable. > > But can we get around this? Shouldn't our French friends (and countless > > others) be able to use SAGE? > > > Apparently we can set the encoding of a python source file with a > comment like: > > # -*- coding: utf_8 -*- > > at the very top of the file (It seems like it has to be pretty much the > first line). > > Are there any comments about automatically adding this (or utf_16?) to > the top of all of the notebook files? Please definitely add this. Make a trac ticket asap for it. Thanks!! > > If there are no comments, I can post a patch for the notebook right away. > > Your example works with the above magic comment as the first line of a > python file, but does not work if that comment is moved down one line. --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: SAGE chokes on French character
dean moore wrote: > When I was writing some other code this came out; finally decided to > report it. Do the following > in an online SAGE notebook: > > /1+1/ > > We get two. Now run the following: > > /# Limaçon > 1+1 > / > Get: > > /Exception (click to the left for traceback): > ... > SyntaxError: Non-ASCII character '\xe7' in file > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but > no encoding declared; see http://www.python.org/peps/pep-0263.html for > details > > Traceback (most recent call last): > File "", line 1, in > File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4 > SyntaxError: Non-ASCII character '\xe7' in file > /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but > no encoding declared; see http://www.python.org/peps/pep-0263.html for > details/ > > --- > > /Sacre bleu!/ It's in a comment! Looking at the error & the web site > it may be a Python thing & untouchable. > But can we get around this? Shouldn't our French friends (and countless > others) be able to use SAGE? Apparently we can set the encoding of a python source file with a comment like: # -*- coding: utf_8 -*- at the very top of the file (It seems like it has to be pretty much the first line). Are there any comments about automatically adding this (or utf_16?) to the top of all of the notebook files? If there are no comments, I can post a patch for the notebook right away. Your example works with the above magic comment as the first line of a python file, but does not work if that comment is moved down one line. Jason --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] SAGE chokes on French character
When I was writing some other code this came out; finally decided to report it. Do the following in an online SAGE notebook: *1+1* We get two. Now run the following: *# Limaçon 1+1 * Get: *Exception (click to the left for traceback): ... SyntaxError: Non-ASCII character '\xe7' in file /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details Traceback (most recent call last): File "", line 1, in File "/home/server2/sage_notebook/worksheets/dino/9/code/3.py", line 4 SyntaxError: Non-ASCII character '\xe7' in file /home/server2/sage_notebook/worksheets/dino/9/code/3.py on line 4, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details* --- *Sacre bleu!* It's in a comment! Looking at the error & the web site it may be a Python thing & untouchable. But can we get around this? Shouldn't our French friends (and countless others) be able to use SAGE? Dean --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mixed 32/64 bit .o files under Linux PowerPC
Hi Michael, The other problem I am facing on powerpc Linux is with compiling with Fortran. Some parts of SAGE accept gfortran and others do not. Here is what I see: checking for Fortran 77 libraries of sage_fortran... checking how to get verbose linking output from gcc -std=gnu99... -v checking for C libraries of gcc -std=gnu99... -L/usr/local/PET/src/ build/sage-2.10.2/local/lib/ -L/usr/local/PET/src/build/sage-2.10.2/ local/lib/../lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2 -L/usr/lib/ gcc/powerpc64-suse-linux/4.1.2/../../../../powerpc64-suse-linux/lib/../ lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib -L/ lib/../lib -L/usr/lib/../lib -L/usr/local/PET/src/build/sage-2.10.2/ local/lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../ powerpc64-suse-linux/lib -L/usr/lib/gcc/powerpc64-suse-linux/ 4.1.2/../../.. -lgcc_s checking for dummy main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... configure: error: cannot compile a simple Fortran program See `config.log' for more details. Error configuring R. real0m57.989s user0m23.697s sys 0m23.042s sage: An error occurred while installing r-2.6.1.p14 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem, yourself *don't* just cd to /usr/local/PET/src/build/sage-2.10.2/spkg/build/r-2.6.1.p14 and type 'make'. Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" in order to set all environment variables correctly, then cd to /usr/local/PET/src/build/sage-2.10.2/spkg/build/r-2.6.1.p14 (When you are done debugging, you can type "exit" to leave the subshell.) make[1]: *** [installed/r-2.6.1.p14] Error 1 make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' real44m44.649s user41m19.765s sys 2m49.245s build/sage-2.10.2> which gfortran /usr/bin/gfortran build/sage-2.10.2> which g77 g77: Command not found. build/sage-2.10.2> which f77 /opt/ibmcmp/xlf/10.1/bin/f77 build/sage-2.10.2> On Mar 4, 10:20 pm, "Michael.Abshoff" <[EMAIL PROTECTED]> wrote: > Sameer wrote: > > Hi, > > When I try to compile Sage 2.10.2 under ppc64 Linux using gcc, > > I see that some files are > > compiled in 32 bits and some others in 64 bits. Have you noticed this? > > Hi Sameer, > > there is several ways to solve the problem: > > a) Use a gcc that forces 64 bit output per default > b) Wait until 2.10.4 and hope that I have time to merge all the 64 bit > PPC fixes :) > > > > > When I type: > > % make > > I get the following error: > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/PET/src/build/ > > sage-2.10.2/local/include -I. -g -O2 -MT > > libiml_la-nullspace.lo -MD -MP -MF .deps/libiml_la-nullspace.Tpo -c > > nullspace.c -o > > libiml_la-nullspace.o >/dev/null 2>&1 > > /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/local/PET/src/build/ > > sage-2.10.2/local/include -I. > > -g -O2 -lm -o libiml.la -rpath /usr/local/PET/src/build/sage-2.10.2/ > > local/lib libiml_la-basisop.lo > > libiml_la-certsolve.lo libiml_la-error.lo libiml_la-latreduce.lo > > libiml_la-memalloc.lo > > libiml_la-mtrans.lo libiml_la-nonsysolve.lo libiml_la-padiclift.lo > > libiml_la-reconsolu.lo > > libiml_la-RNSop.lo libiml_la-nullspace.lo -L/usr/local/PET/src/build/ > > sage-2.10.2/local/lib -lgmp > > ../repl/librepl.la > > gcc -shared .libs/libiml_la-basisop.o .libs/libiml_la- > > certsolve.o .libs/libiml_la-error.o > > .libs/libiml_la-latreduce.o .libs/libiml_la-memalloc.o .libs/libiml_la- > > mtrans.o > > .libs/libiml_la-nonsysolve.o .libs/libiml_la-padiclift.o .libs/ > > libiml_la-reconsolu.o > > .libs/libiml_la-RNSop.o .libs/libiml_la-nullspace.o -Wl,--whole- > > archive ../repl/.libs/librepl.a > > -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/local/PET/src/build/ > > sage-2.10.2/local/lib -Wl,--rpath > > -Wl,/usr/local/PET/src/build/sage-2.10.2/local/lib -L/usr/local/PET/ > > src/build/sage-2.10.2/local/lib > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so -lm -Wl,- > > soname -Wl,libiml.so.0 -o > > .libs/libiml.so.0.0.0 > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so: could not > > read symbols: File in wrong format > > collect2: ld returned 1 exit status > > make[4]: *** [libiml.la] Error 1 > > make[4]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src/src' > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src' > > Error building IML > > > real 0m41.850s > > user 0m26.428s > > sys 0m10.164s > > sage: An error occurred while installing iml-1.0.1.p9 > > Please email sage-develhttp://gro
[sage-support] Error related with singular, gap and resultant
Dear sage supporters,
a strange error occurs in sage 2.10.2 in the following way:
sage: R. = QQ[]
sage: f = x^3 + x + 1; g = x^3 - x - 1
sage: r = f.resultant(g)
sage: R.__dict__
{'_PolynomialRing_general__cyclopoly_cache': {},
'_PolynomialRing_general__generator': x,
'_PolynomialRing_general__is_sparse': False,
'_PolynomialRing_general__polynomial_class': ,
'_PolynomialRing_singular_repr__singular': // characteristic : 0
// number of vars : 1
//block 1 : ordering lp
// : namesx
//block 2 : ordering C,
'_has_singular': True}
Ok so far. Now we use the gap interface and experience a bad surprise:
sage: gap(R.base_ring())
Rationals
sage: R.__dict__
{'_PolynomialRing_general__cyclopoly_cache': {},
'_PolynomialRing_general__generator': x,
'_PolynomialRing_general__is_sparse': False,
'_PolynomialRing_general__polynomial_class': ,
'_PolynomialRing_singular_repr__singular': print(sage0);
// characteristic : 0
// number of vars : 1
//block 1 : ordering lp
// : namesx
//block 2 : ordering C,
'_has_singular': True}
See how R.__dict__['PolynomialRing_singular_repr__singular'] has
changed!
In the first part of the session, it contained a ring, but now it
contains print(sage0).
Even worse: Although sage0 used to be the identifier of the singular
ring associated with R, we now get
sage: singular('sage0')
print(sage8);
sage: sage: singular('sage0')
print(sage9);
sage: sage: singular('sage0')
print(sage10);
and so on!
So, the singular interface seems to be completely messed up. I have no
idea where this behaviour comes from.
Note that the line
sage: r = f.resultant(g)
is essential. When this line is replaced by, e.g.,
sage: singular(R)
the error does not occur. Also, when we first say gap(R.base_ring())
and then compute the resultant, everything is alright.
Perhaps this helps to detect the bug.
Any idea? Shall i open a ticket?
Yours
Simon
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Mixed 32/64 bit .o files under Linux PowerPC
Hi Michael, I untarred the gmp package and built it again changing makefiles to delete the -m64 option from CFLAGS and CXXFLAGS. It built properly and now the rest of SAGE is compiling properly. The problem was that by default the gmp package chose 64 bit compilation. We may need to disable this. Thanks for your help! - Sameer On Mar 4, 10:20 pm, "Michael.Abshoff" <[EMAIL PROTECTED]> wrote: > Sameer wrote: > > Hi, > > When I try to compile Sage 2.10.2 under ppc64 Linux using gcc, > > I see that some files are > > compiled in 32 bits and some others in 64 bits. Have you noticed this? > > Hi Sameer, > > there is several ways to solve the problem: > > a) Use a gcc that forces 64 bit output per default > b) Wait until 2.10.4 and hope that I have time to merge all the 64 bit > PPC fixes :) > > > > > When I type: > > % make > > I get the following error: > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/PET/src/build/ > > sage-2.10.2/local/include -I. -g -O2 -MT > > libiml_la-nullspace.lo -MD -MP -MF .deps/libiml_la-nullspace.Tpo -c > > nullspace.c -o > > libiml_la-nullspace.o >/dev/null 2>&1 > > /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/local/PET/src/build/ > > sage-2.10.2/local/include -I. > > -g -O2 -lm -o libiml.la -rpath /usr/local/PET/src/build/sage-2.10.2/ > > local/lib libiml_la-basisop.lo > > libiml_la-certsolve.lo libiml_la-error.lo libiml_la-latreduce.lo > > libiml_la-memalloc.lo > > libiml_la-mtrans.lo libiml_la-nonsysolve.lo libiml_la-padiclift.lo > > libiml_la-reconsolu.lo > > libiml_la-RNSop.lo libiml_la-nullspace.lo -L/usr/local/PET/src/build/ > > sage-2.10.2/local/lib -lgmp > > ../repl/librepl.la > > gcc -shared .libs/libiml_la-basisop.o .libs/libiml_la- > > certsolve.o .libs/libiml_la-error.o > > .libs/libiml_la-latreduce.o .libs/libiml_la-memalloc.o .libs/libiml_la- > > mtrans.o > > .libs/libiml_la-nonsysolve.o .libs/libiml_la-padiclift.o .libs/ > > libiml_la-reconsolu.o > > .libs/libiml_la-RNSop.o .libs/libiml_la-nullspace.o -Wl,--whole- > > archive ../repl/.libs/librepl.a > > -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/local/PET/src/build/ > > sage-2.10.2/local/lib -Wl,--rpath > > -Wl,/usr/local/PET/src/build/sage-2.10.2/local/lib -L/usr/local/PET/ > > src/build/sage-2.10.2/local/lib > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so -lm -Wl,- > > soname -Wl,libiml.so.0 -o > > .libs/libiml.so.0.0.0 > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so: could not > > read symbols: File in wrong format > > collect2: ld returned 1 exit status > > make[4]: *** [libiml.la] Error 1 > > make[4]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src/src' > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src' > > Error building IML > > > real 0m41.850s > > user 0m26.428s > > sys 0m10.164s > > sage: An error occurred while installing iml-1.0.1.p9 > > Please email sage-develhttp://groups.google.com/group/sage-devel > > explaining the problem and send the relevant part of > > of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your > > computer, operating system, etc. > > If you want to try to fix the problem, yourself *don't* just cd to > > /usr/local/PET/src/build/sage-2.10.2/spkg/build/iml-1.0.1.p9 and type > > 'make'. > > Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" > > in order to set all environment variables correctly, then cd to > > /usr/local/PET/src/build/sage-2.10.2/spkg/build/iml-1.0.1.p9 > > (When you are done debugging, you can type "exit" to leave the > > subshell.) > > make[1]: *** [installed/iml-1.0.1.p9] Error 1 > > make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' > > > real 45m41.259s > > user 38m16.037s > > sys 5m3.453s > > build/sage-2.10.2> file /usr/local/PET/src/build/sage-2.10.2/local/lib/ > > libgmp.so > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so: symbolic > > link to `libgmp.so.3.4.1' > > build/sage-2.10.2> file /usr/local/PET/src/build/sage-2.10.2/local/lib/ > > libgmp.so.3 > > libgmp.so.3@ libgmp.so.3.4.1* > > build/sage-2.10.2> file /usr/local/PET/src/build/sage-2.10.2/local/lib/ > > libgmp.so.3.4.1 > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so.3.4.1: ELF 64- > > bit MSB shared object, cisco > > 7500, version 1 (SYSV), not stripped > > build/sage-2.10.2> file .libs/libiml_la-basisop.o > > .libs/libiml_la-basisop.o: cannot open `.libs/libiml_la-basisop.o' (No > > such file or directory) > > build/sage-2.10.2> file `find . -name libiml_la-basisop.o -print` > > ./spkg/build/iml-1.0.1.p9/src/src/.libs/libiml_la-basisop.o: ELF 32- > > bit MSB relocatable, PowerPC or > > cisco 4500, version 1 (SYSV), not stripped > > ./spkg/build/iml-1.0.1.p9/src/src/libiml_la-b
[sage-support] Re: Spline question
On Wed, Mar 5, 2008 at 10:57 AM, dean moore <[EMAIL PROTECTED]> wrote: > Thanks! That worked nicely. > > But should this type of thing be documented, as others may face this? > > Dean > Sure! Could you just take the current docs for spline?, modifying them the way you wish they were regarding the above issues, and put the result as a response to this email? William --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Spline question
Thanks! That worked nicely. But should this type of thing be documented, as others may face this? Dean --- On Tue, Mar 4, 2008 at 10:18 PM, Mike Hansen <[EMAIL PROTECTED]> wrote: > On Tue, Mar 4, 2008 at 8:03 PM, dean moore <[EMAIL PROTECTED]> > wrote: > > I'm trying to spline the unit circle. The graph looks like a > polynomial, > > not a fit to > > the unit circle. > > > > Well, you're going to have some problems using spline since it does a > univariate polynomial spline interpolation. What you really want to > do is do a spline on each of the coordinates and then do a parametric > plot of those two splines: > > v = [] # Will hold points > step = 0.5 # "Fineness" of my approximation > for x in srange(0, 2*pi, step): # Fill parameter *v* with points > v.append((cos(x), sin(x))) # on the unit circle. > > x_spline = spline([(RDF(i)/len(v), v[i][0]) for i in > range(len(v))]+[(1,v[0][0])]) > y_spline = spline([(RDF(i)/len(v), v[i][1]) for i in > range(len(v))]+[(1,v[0][1])]) > parametric_plot((x_spline, y_spline),0,1) > > --Mike > > > > --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: MAC PC configuration problem.
On Wed, Mar 5, 2008 at 7:55 AM, Neal Laurance <[EMAIL PROTECTED]> wrote: > > I have just installed SAGE on my MAC book, and it works fine there. But > I would like to use it from my desk PC (Windows XP). The PC has a bigger > display. I opened Firefox on the PC, entered the local IP address of the > MAC (192.168.1.103) and I get an acknowledgment from the Apache Web > server. Then I tried 192.168.1.103:8000, trying to connect with the SAGE > session running on my MAC. No luck. It times out. You *must* explicitly start the notebook like this: sage: notebook(address="192.168.1.103") where 192.168.1.103 is the external address of your laptop. If you don't do this the notebook will _only_ listen to connection from localhost (i.e., your laptop), as a security precaution. After you type the above, from your PC navigate to https://192.168.1.103:8000 > > I have tried variations like 192.168.1.103/localhost:8000 and several > other combinations, but no luck. The Apache response tells me something > is working; I just haven't managed to reach SAGE yet. > > > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Minimum installation size
On Wednesday 05 March 2008, Ryan Hinton wrote: > What if I want to develop in certain sections (coding theory, maybe > some graph theory)? I wouldn't recommend deleting static libraries because it is too easy to shoot yourself in the foot if you do. If you only strip your binaries/libraries then you can still develop, you just won't get very nice backtraces if Sage crashes on you. Note, even if you removed all static libraries (again, I wouldn't recommend it!) you can still develop pure Python code which should constitute a fair amount of the coding theory / graph theory code (I don't know though). For your convenience lets reduce the size of 2.10.3.rc2: We start with: $ du -h --max-depth=1 3.3M./examples 64K ./ipython 222M./devel 27M ./doc 784M./local 17M ./data 700K./spkg 1.1G. This is due to the fact that all the source SPKGs have already been replaced by empty files. This is done automatically for binary releases. Now we strip the shared libraries $ cd $SAGE_ROOT $ cd local/; find . -name "*.so" | xargs strip $ cd .. $ du -h --max-depth=1 3.3M./examples 64K ./ipython 222M./devel 27M ./doc 684M./local 17M ./data 700K./spkg 952M. Now we strip executable (this is a bit messy): $cd local; find . -perm /u+x -type f | xargs strip $cd ..; du -h --max-depth=1 3.3M./examples 64K ./ipython 222M./devel 27M ./doc 648M./local 17M ./data 700K./spkg 915M. At this point we still got a fully functional developer-enabled copy of Sage. However, we are still at 915M. We should consider removing _some_ of the static libraries, i.e. those which are redundant. $ cd local; find -name "*.a" | xargs rm $ cd .. $ du -h --max-depth=1 3.3M./examples 64K ./ipython 220M./devel 27M ./doc 383M./local 17M ./data 700K./spkg 650M. However, now development might not be possible anymore. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _www: http://www.informatik.uni-bremen.de/~malb _jab: [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: submatrix notation and method
On Wed, Mar 5, 2008 at 10:21 AM, Dan Christensen <[EMAIL PROTECTED]> wrote:
>
> "didier deshommes" <[EMAIL PROTECTED]> writes:
>
> > SAGE now tries to support numpy (and matlab)-style indexing, by poking
> > at its underlying __getitem__ and __getslice__ (thanks to a suggestion
> > by William):
>
> Great!
>
> Another nice feature of numpy is *assigning* using numpy-style indexing.
> For example, to add a multiple of column j to column i, you can do
>
> A[:,i] += m*A[:,j]
>
> And you can zero out a region with
>
> A[2:4, 3:8] = 0(broadcasting used here)
This is currently not supported, I've opened a ticket:
http://trac.sagemath.org/sage_trac/ticket/2396
>
> About the efficiency concern raised by William, does it work to first
> assume the indices are not fancy, and if that fails, then catch an
> exception and try to interpret them as numpy-style indices?
We check first if both indices are Integers and return immediately. If
not, we check if each argument is either a list, a slice or an
integer and pass that result to matrix_from_rows_and_columns.
The new method turns out to be faster in most cases for
element-by-element retrieval on large matrices (all timings done on
sage.math):
{{
#old
sage: M = random_matrix(ZZ,1500,600)
sage: %timeit M[29,300]
1 loops, best of 3: 70.7 µs per loop
#new
sage: M = random_matrix(ZZ,1500,600)
sage: %timeit M[29,300]
1 loops, best of 3: 68.3 µs per loop
#
#old
sage: M = random_matrix(ZZ,1500,1500)
sage: %timeit M[1000,1000]
1 loops, best of 3: 70.3 µs per loop
#new
sage: M = random_matrix(ZZ,1500,1500)
sage: %timeit M[1000,1000]
1 loops, best of 3: 68 µs per loop
}}}
In this case, I think it's cython being smarter about optimizing stuff.
For whole row retrieval, it is still slower:
{{{
#old
sage: M = random_matrix(ZZ,4000)
sage: %timeit M[3000]
1000 loops, best of 3: 1.05 ms per loop
#new
sage: M = random_matrix(ZZ,4000)
sage: %timeit M[3000]
1000 loops, best of 3: 1.12 ms per loop
}}}
This depends on matrix_from_rows, so optimizing that will yield results faster.
didier
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] MAC PC configuration problem.
I have just installed SAGE on my MAC book, and it works fine there. But I would like to use it from my desk PC (Windows XP). The PC has a bigger display. I opened Firefox on the PC, entered the local IP address of the MAC (192.168.1.103) and I get an acknowledgment from the Apache Web server. Then I tried 192.168.1.103:8000, trying to connect with the SAGE session running on my MAC. No luck. It times out. I have tried variations like 192.168.1.103/localhost:8000 and several other combinations, but no luck. The Apache response tells me something is working; I just haven't managed to reach SAGE yet. --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Minimum installation size
What if I want to develop in certain sections (coding theory, maybe some graph theory)? On Mar 5, 3:38 pm, "Michael.Abshoff" <[EMAIL PROTECTED]> wrote: > Ryan Hinton wrote: > > I would like to use and contribute to Sage on my university's Linux > > cluster, but I only have about 2.0 GB disk space total for programs > > and data. An Ubuntu installation (sage-2.10.2, I believe) weighed in > > at about 1.3 GB. I don't think this leaves me enough room for data. > > Is there a convenient way to reduce this size? > > > Thanks! > > Hi Ryan, > > you can remove certain static libraries and strip everything to go > down in size. You lose the ability to develop on that copy, but it > seems to be a trade off you are willing to make for the "compute only > version" of your Sage install. > > I am traveling now, but since this has been a much requested feature I > will write a script that does the job - unless somebody beats me to it. > > Cheers, > > Michael > > > --- > > Ryan Hinton > > rwh4s, domain virginia.edu --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] MAC PC configuration problem.
I have just installed SAGE on my MAC book, and it works fine there. But I would like to use it from my desk PC (Windows XP). The PC has a bigger display. I opened Firefox on the PC, entered the local IP address of the MAC (192.168.1.103) and I get an acknowledgment from the Apache Web server. Then I tried 192.168.1.103:8000, trying to connect with the SAGE session running on my MAC. No luck. It times out. I have tried variations like 192.168.1.103/localhost:8000 and several other combinations, but no luck. The Apache response tells me something is working; I just haven't managed to reach SAGE yet. --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Minimum installation size
On Wednesday 05 March 2008, Ryan Hinton wrote: > I would like to use and contribute to Sage on my university's Linux > cluster, but I only have about 2.0 GB disk space total for programs > and data. An Ubuntu installation (sage-2.10.2, I believe) weighed in > at about 1.3 GB. I don't think this leaves me enough room for data. > Is there a convenient way to reduce this size? I don't know if you built from source or if you got the binary release, if you built from source: cd $SAGE_ROOT/spkg/standard for i in *.spkg; do rm $i; touch $i; done will replace all the source SPKGs with empty files. Note the "rm" in the above line so be careful about it. If you don't want nice gdb backtraces (as a normal end user you probably don't want to debug Sage's C code) you can also strip all libraries and binaries in $SAGE_LOCAL/local/bin and $SAGE_LOCAL/lib cd $SAGE_ROOT/local find -name "*.so" | xargs strip will do it for the shared libs. I once got it down to 655M using these two tricks, see: http://trac.sagemath.org/sage_trac/ticket/1293#comment:2 Hope that helps, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _www: http://www.informatik.uni-bremen.de/~malb _jab: [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Minimum installation size
Ryan Hinton wrote: > I would like to use and contribute to Sage on my university's Linux > cluster, but I only have about 2.0 GB disk space total for programs > and data. An Ubuntu installation (sage-2.10.2, I believe) weighed in > at about 1.3 GB. I don't think this leaves me enough room for data. > Is there a convenient way to reduce this size? > > Thanks! Hi Ryan, you can remove certain static libraries and strip everything to go down in size. You lose the ability to develop on that copy, but it seems to be a trade off you are willing to make for the "compute only version" of your Sage install. I am traveling now, but since this has been a much requested feature I will write a script that does the job - unless somebody beats me to it. Cheers, Michael > --- > Ryan Hinton > rwh4s, domain virginia.edu > > > > --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: submatrix notation and method
Will you allow single-argument indexing as well? The Matlab convention is that indexing using a single argument indexes vec(A) instead of A. That's often useful, e.g., to update the diagonal of an nxn matrix, you could write A[::n+1] = 1.0. More generally, it allows you to easily update a subset of the elements in A by writing A[I] = b where I is an index-set. Without single-argument indexing, you would need to write a loop for doing that. I think I raised the same question on the Scipy list long ago, and as I remember it the developers didn't like the idea. Personally, I like the convention, and it makes matrix computions more flexible than having to use a helper routine for things like that. Joachim On Mar 5, 4:21 pm, Dan Christensen <[EMAIL PROTECTED]> wrote: > "didier deshommes" <[EMAIL PROTECTED]> writes: > > SAGE now tries to support numpy (and matlab)-style indexing, by poking > > at its underlying __getitem__ and __getslice__ (thanks to a suggestion > > by William): > > Great! > > Another nice feature of numpy is *assigning* using numpy-style indexing. > For example, to add a multiple of column j to column i, you can do > > A[:,i] += m*A[:,j] > > And you can zero out a region with > > A[2:4, 3:8] = 0 (broadcasting used here) > > About the efficiency concern raised by William, does it work to first > assume the indices are not fancy, and if that fails, then catch an > exception and try to interpret them as numpy-style indices? > > Dan --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] mympi in addition to mpi4py as optional package in sage?
Do you see the mympi python/mpi module showing up as an optional package in sage? http://peloton.sdsc.edu/~tkaiser/mympi/ I see openmpi and mpi4py there (which is great). Albert --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Minimum installation size
I would like to use and contribute to Sage on my university's Linux cluster, but I only have about 2.0 GB disk space total for programs and data. An Ubuntu installation (sage-2.10.2, I believe) weighed in at about 1.3 GB. I don't think this leaves me enough room for data. Is there a convenient way to reduce this size? Thanks! --- Ryan Hinton rwh4s, domain virginia.edu --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: submatrix notation and method
"didier deshommes" <[EMAIL PROTECTED]> writes: > SAGE now tries to support numpy (and matlab)-style indexing, by poking > at its underlying __getitem__ and __getslice__ (thanks to a suggestion > by William): Great! Another nice feature of numpy is *assigning* using numpy-style indexing. For example, to add a multiple of column j to column i, you can do A[:,i] += m*A[:,j] And you can zero out a region with A[2:4, 3:8] = 0(broadcasting used here) About the efficiency concern raised by William, does it work to first assume the indices are not fancy, and if that fails, then catch an exception and try to interpret them as numpy-style indices? Dan --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Vector fields and Quivers
On Tue, Mar 4, 2008 at 12:38 AM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Hector Villafuerte wrote: ... > > So my question: is there a SAGEly way to plot this type of vector fields? > > Thanks in advance! > > There is now! It turned out to be a pretty simple fix to > plot_vector_field; see http://trac.sagemath.org/sage_trac/ticket/2381 ... Thanks Jason! I like it when there are SAGEly ways to proceed :) Best, -- Hector --~--~-~--~~~---~--~~ 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://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Vector fields and Quivers
Eric Drechsel wrote:
> Jason: wow, that was quick. I'll try out the plot_vector_field patch
> as soon as I figure out how to test patches etc
No problem. The patch is included in 2.10.3, so the functionality
should be available in just a day or two at the most (2.10.3 is almost
released).
>
> I ended up using Hector's example and some things from the matplotlib
> documentation for my assignment. A notable improvement is using
> axis('tight'), which solves the window mis-alignment problem.
> Uploaded to https://www.sagenb.org/home/pub/1721
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---
