William,
If it helps, I put some debugging statements in the code:
def next_prime(n, proof=None):
print "inside next_prime(): Before integer_ring.ZZ n =", n, "
proof = ", proof
n = integer_ring.ZZ(n)
print "inside next_prime(): n =", n, " proof = ", proof
return n.next_prime(pro
William,
Yes, isprime(2) works properly. I get:
64/sage-2.10.2> ./sage -gp -q
? isprime(2)
1
?
?
Thanks,
- Sameer
On Mar 9, 4:35 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 9, 2008 at 2:40 PM, Sameer <[EMAIL PROTECTED]> wrote:
>
> > Michael,
> > I am getting closer.
On Sun, Mar 9, 2008 at 2:40 PM, Sameer <[EMAIL PROTECTED]> wrote:
>
> Michael,
>I am getting closer. I rebuilt the iml and linboxwrap packages and
> got rid of the undefined errors. Now, I get:
> 64/sage-2.10.2> ./sage -br
>
> --
> s
Michael,
I am getting closer. I rebuilt the iml and linboxwrap packages and
got rid of the undefined errors. Now, I get:
64/sage-2.10.2> ./sage -br
--
sage: Building and installing modified SAGE library files.
Installing c_lib
scons: `i
On Mar 9, 2:43 am, Sameer <[EMAIL PROTECTED]> wrote:
> William, Michael,
> I re-installed gap by compiling it in 32 bit mode and that got rid
> of the error.
Good, that is a workaround - at least until someone wants to run GAP
in 64 bit mode :)
> gap, it seems doesn't support 64 bit mode. No
William, Michael,
I re-installed gap by compiling it in 32 bit mode and that got rid
of the error. gap, it seems doesn't support 64 bit mode. Now, I am
dealing with some startup errors such as:
/usr/local/PET/src/build/64/sage-2.10.2/local/lib/liblinboxwrap.so.0:
undefined symbol: _gfortran_st_
On Mar 9, 1:48 am, Sameer <[EMAIL PROTECTED]> wrote:
> William,
>Thanks a lot for the
> sage -br
> command. I found that I needed to re-install singular, fplll and then
> it needed qd so I got qd 2.1 initially but it didn't work, so I got qd
> 2.3.5 from LBL and it compiled everything. At th
William,
Thanks a lot for the
sage -br
command. I found that I needed to re-install singular, fplll and then
it needed qd so I got qd 2.1 initially but it didn't work, so I got qd
2.3.5 from LBL and it compiled everything. At the end, sage gave an
error:
copying sage/dsage/web/index.html -> /u
On Sat, Mar 8, 2008 at 12:23 PM, Sameer <[EMAIL PROTECTED]> wrote:
>
> Hi,
>I made scripts for gcc/g++/gfortran and put them in my ~/bin
> directory. These scripts add -m64 argument to the compilers and so I
> was able to generate 64 bit binaries. After several errors and
> manually interv
On Mar 8, 9:23 pm, Sameer <[EMAIL PROTECTED]> wrote:
> Hi,
>I made scripts for gcc/g++/gfortran and put them in my ~/bin
> directory. These scripts add -m64 argument to the compilers and so I
> was able to generate 64 bit binaries. After several errors and
> manually intervening (building sh
Hi,
I made scripts for gcc/g++/gfortran and put them in my ~/bin
directory. These scripts add -m64 argument to the compilers and so I
was able to generate 64 bit binaries. After several errors and
manually intervening (building shared objects etc.) I think it has
compiled SAGE completely on ppc
Hi,
So, I rebuilt clisp and then maxima built properly. Regarding the
sage error, I tried to build gmp-4.2.1 using a gcc wrapper where I eat
up the -m64 argument. This wrapper internally calls /usr/bin/gcc. This
way, when I invoke:
% gcc -m64 -c foo.c
it builds a 32 bit object. When I installed
On Mar 6, 1:47 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> 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
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 1
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
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
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
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
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 def
19 matches
Mail list logo
