Hi there,
We've been asked the following question in #10519:
I thought this might be because amgf.sage is a Sage file and not a Python
file. So i renamed it amgf.py instead and got syntax errors. What's up
with that? Do i have to rewrite all my code in Python instead of Sage?
I
Hi,
Sorry that I realized this is the devel group instead of support group
only after I had applied and was approved membership. If this is the
wrong group, please let me know.
I was (am) building Sage 4.7 from source on a freshly installed
OpenSUSE 11.4 (the binary for Ubuntu didn't work). Afte
Hi!,
At http://www.sagenb.org/home/pub/2813, I have published a worksheet
that aims at explaining how one can implement a new parent and take
advantage of both the category framework and the coercion model
(including construction functors).
My approach was to implement fraction fields step by ste
On 11 Jun., 21:19, Simon King wrote:
> In another thread, I suggested to proceed with documentation similar
> than with spkgs: I believe that it is better to make preliminary
> versions of tutorials available to the public (explicitly marking them
> as preliminary or draft) ...
... similar to an
> Hi,
>
> Sorry that I realized this is the devel group instead of support group
> only after I had applied and was approved membership. If this is the
> wrong group, please let me know.
>
> I was (am) building Sage 4.7 from source on a freshly installed
> OpenSUSE 11.4 (the binary for Ubuntu di
Hi everyone,
I got this problem building both alpha2 and alpha4. I'm running OS X
(10.6.7) on a 64-bit Macbook Pro.
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../src
-I/Users/roed/sage/sage-4.7.1.alpha4/local/include -g -O2 -frounding-math
-I/Users/roed/sage/sage-4.7.1.alpha4/local/in
Thanks, Francois,
The following is the config.log:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by R configure 2.10.1, which was
generated by GNU Autoconf 2.61. Invocation command line was
$ ./
> configure:5008: checking for C compiler default output file name
> configure:5035: gcc -I/home/andrew/Download/software/sage-4.7/local/
> include -L/home/andrew/Download/software/sage-4.7/local/lib/ -I/home/
> andrew/Download/software/sage-4.7/local/include -L/home/andrew/
> Download/software/s
Ahh, thanks a lot Francois.
This gives me the following thought: When I met the problem of libppl
before, I used the solution posted here: link the local/lib/libppl.so.
9.0.0 to /usr/lib/libppl.so.9.0.0 to replace old one. I just found
that libppl.so.9 symbolically linked to the old libppl.so.9.0.
Do you use some non-standard compiler? Or did you run out of memory/disk
space? Something killed g++ and I'm pretty sure it wasn't us.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
10 matches
Mail list logo
