On Thursday, December 13, 2012 4:34:03 PM UTC-5, Emmanuel Charpentier wrote:
>
> I can't reproduce your problem (using the server at www.sagenb.org). I
> ask :
>
Undy, is it possible that you have an older version of Sage? We do update
Maxima (and hence our integration routines) periodically;
Jeroen Demeyer writes:
> Could you list your environment variables within Sage?
Script started on Fri Dec 14 09:12:28 2012
bash greg-minshalls-mbp: {500} ./sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with
C_INCLUDE_PATH / CPLUS_INCLUDE_PATH are overriding the default gcc header
search path. This is why compilation is failing. Did fink put in these
system-wide environment variables? Thats seriously effed up.
--
You received this message because you are subscribed to the Google Groups
"sage-su
Volker,
> C_INCLUDE_PATH / CPLUS_INCLUDE_PATH are overriding the default gcc header
> search path. This is why compilation is failing. Did fink put in these
> system-wide environment variables? Thats seriously effed up.
no, they come from my .bashrc. they've been "there" since 2008. sadly,
i
No its first -I, then *_INCLUDE_PATH, then the path thats hard-wired
into the compiler. But since Sage builds its own compiler you are
effectively overriding the search path.
On Friday, December 14, 2012 3:13:06 PM UTC, Greg Minshall wrote:
> > C_INCLUDE_PATH / CPLUS_INCLUDE_PATH are overriding
Is there any function in Sage by which this kind of symbolic calculation
is possible?
s=0
for i=1 to m
if(i>a+t)
s=s+2i
else
s=s+t
m,a,t are non negative integers.
--
You received this message because you are subscribed to the Google Groups
"sage-support"
On Fri, Dec 14, 2012 at 12:31 PM, Santanu Sarkar <
sarkar.santanu@gmail.com> wrote:
> Is there any function in Sage by which this kind of symbolic
calculation
> is possible?
>
> s=0
> for i=1 to m
> if(i>a+t)
> s=s+2i
> else
> s=s+t
>
> m,a,t are non nega
On Fri, Dec 14, 2012 at 2:44 PM, Santanu Sarkar <
sarkar.santanu@gmail.com> wrote:
> No, as s will be a function of a,m,t,
> I need that function. For my toy example it will be easy.
>
You wrote "> s=0" right in your question, so I don't think I'll be able
to help you further. I hope som
Volker,
No its first -I, then *_INCLUDE_PATH, then the path thats hard-wired
> into the compiler. But since Sage builds its own compiler you are
> effectively overriding the search path.
however, this doesn't explain the failure i was having, where
gcc -c -I. -I../src/headers -I../src/la
Hi,
I was actually using a very old version of Sage (4.8). I have just tried
with version 5.4.1 and... yes, it works perfectly now!
I should have thought of upgrading Sage earlier I am sorry about that.
Thank you,
Undy
Il giorno venerdì 14 dicembre 2012 15:01:10 UTC+1, kcrisman ha scritto:
>
Santanu Sarkar writes:
> No, as s will be a function of a,m,t,
You can't have imperative code in a symbolic function, if that's what
you're asking. You can of course use an imperative (Python) function to
do what you want::
def s(m, a, t):
result = 0
for i in srange(1,m+1):
If the directory is already in the built-in search path (like
/Users/minshall/src/import/sage/sage-5.4.1/local/include if you use the gcc
that Sage compiled) then the -I option is ignored.
-Idir
Add the directory dir to the head of the list of directories to be searched
for header files. This
Volker,
> If the directory is already in the built-in search path (like
> /Users/minshall/src/import/sage/sage-5.4.1/local/include if you use
> the gcc that Sage compiled) then the -I option is ignored.
ah! got it. so, the Sage-compiled gcc includes .../local/include as
"a standard system direc
On Friday, December 14, 2012 12:41:57 PM UTC-8, Keshav Kini wrote:
>
> Santanu Sarkar > writes:
>
> > No, as s will be a function of a,m,t,
>
> You can't have imperative code in a symbolic function, if that's what
> you're asking. You can of course use an imperative (Python) function to
> do w
I ran "make check" and this is what I got. This is on Ubuntu 12.04
HACK zompu:~/playground/sage/sage-5.4.1$ ./sage -t -force_lib
"devel/sage/sage/structure/dynamic_class.py"
sage -t -force_lib "dev
Aha, it probably has to do with this environment variable that I have set:
PYTHONDONTWRITEBYTECODE=1
I set this years ago in my bash init files in order to work-around some
other bug in some other software package, the details of which I've now
forgotten...
--
You received this message becau
On Friday, December 14, 2012 9:16:26 PM UTC-7, zooko wrote:
>
> Aha, it probably has to do with this environment variable that I have set:
>
> PYTHONDONTWRITEBYTECODE=1
>
Confirmed that unsetting PYTHONDONTWRITEBYTECODE, rerunning "make", and
then rerunning this test caused the test to pass.
S
17 matches
Mail list logo
