Build report on the second 3.1.2.rc1:
On 64-bit Suse, all ok and all tests pass.
On 32-bit ubuntu (): build ok, some test failures:
sage -t devel/sage/sage/stats/hmm/chmm.pyx
sage -t devel/sage/sage/stats/hmm/hmm.pyx
sage -t devel/sage/sage/schemes/elliptic_curves/period_lattice.py
sage -t devel/sage/sage/matrix/matrix_real_double_dense.pyx
The first two are thw known oldies. The third, which is in a doctest
I wrote for a recent patch, is just numerical fuzz. It's not that
surprising, since the patch had a lot of precision tests and I can
patch it by the usual trick of replacing the last 3 decimal digits
with "..." (unless anyonle knows a better way).
The last one is this:
******************************************
File "/home/john/sage-3.1.2.rc1/tmp/matrix_real_double_dense.py", line 493:
sage: b = e * v
Exception raised:
Traceback (most recent call last):
File "/home/john/sage-3.1.2.rc1/local/lib/python2.5/doctest.py",
line 1228, in __run
compileflags, 1) in test.globs
File "<doctest __main__.example_8[8]>", line 1, in <module>
b = e * v###line 493:
sage: b = e * v
File "element.pyx", line 1384, in
sage.structure.element.RingElement.__mul__
(sage/structure/element.c:9357)
File "coerce.pyx", line 662, in
sage.structure.coerce.CoercionModel_cache_maps.bin_op
(sage/structure/coerce.c:6364)
TypeError: unsupported operand parent(s) for '*': 'Complex Double
Field' and 'Vector space of degree 3 and dimension 1 over Real Double
Field
User basis matrix:
[0.440242867236 0.567868371314 0.695493875393]'
**********************************************************************
File "/home/john/sage-3.1.2.rc1/tmp/matrix_real_double_dense.py", line 494:
sage: diff = a.change_ring(CDF) - b
Exception raised:
Traceback (most recent call last):
File "/home/john/sage-3.1.2.rc1/local/lib/python2.5/doctest.py",
line 1228, in __run
compileflags, 1) in test.globs
File "<doctest __main__.example_8[9]>", line 1, in <module>
diff = a.change_ring(CDF) - b###line 494:
sage: diff = a.change_ring(CDF) - b
NameError: name 'b' is not defined
**********************************************************************
File "/home/john/sage-3.1.2.rc1/tmp/matrix_real_double_dense.py", line 495:
sage: abs(abs(diff)) < 1e-10
Exception raised:
Traceback (most recent call last):
File "/home/john/sage-3.1.2.rc1/local/lib/python2.5/doctest.py",
line 1228, in __run
compileflags, 1) in test.globs
File "<doctest __main__.example_8[10]>", line 1, in <module>
abs(abs(diff)) < RealNumber('1e-10')###line 495:
sage: abs(abs(diff)) < 1e-10
TypeError: bad operand type for abs(): 'function'
**********************************************************************
John
2008/9/9 Georg S. Weber <[EMAIL PROTECTED]>:
>
> Sigh, it seems that we have (had) two different build errors here.
> One directly after "Done installing PolyBoRi.", which was healed by
> updating to the .p4 polybori 0.5 spkg.
> The other error seems to be OS X specific and occurs even before
> PolyBoRi can be fully installed.
> I'll try now a run with the old 3.1.1. PolyBoRi v0.3 spkg, to see
> whether there are still other issues
>
> Cheers,
> gsw
>
>
> P.S.:
> Thanks for the info w.r.t. GMP and its different versions ... that was
> interesting.
> For the record, GMP v4.2.3 still seemingly does not want to recognize
> my Core2 Duo properly:
> ...
> checking build system type... core2-apple-darwin8.11.1
> checking host system type... core2-apple-darwin8.11.1
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of
> Makefiles... no
> checking ABI=32
> checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer has
> sizeof(long)==4... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2...
> no
> checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=k8... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=k8 -
> march=core2... no
> checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=k8 -
> march=core2 -mno-sse2... no
> checking whether gcc is good for sse2... yes
> checking whether the operating system supports XMM registers... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=k8 -
> march=k8... yes
> checking for gcc... gcc
> ...
>
> I would have expexted that "... mtune=core2" works.
> (Sorry if this is too "off topic")
>
> On 9 Sep., 13:11, Alex Ghitza <[EMAIL PROTECTED]> wrote:
>> For the record, replacing polybori-05rc.p3.spkg with the new p4 version and
>> continuing the build process worked for me (dell laptop running ubuntu).
>>
>> Alex
>>
>>
>>
>> Georg S. Weber wrote:
>> > sorry,
>> > but the "polybori-05rc.p4.spkg" you pointed to (http://
>> > sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/rc... )
>> > throws exactly the same build error as before:
>>
>> > ...
>> > /usr/bin/libtool: unknown option character `d' in: -dylib_install_name
>> > Usage: /usr/bin/libtool -static [-] file [...] [-filelist
>> > listfile[,dirname]] [-arch_only arch] [-sacLT]
>> > Usage: /usr/bin/libtool -dynamic [-] file [...] [-filelist
>> > listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name]
>> > [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-
>> > segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table
>> > <filename>] [-seg_addr_table_filename <file_system_path>] [-all_load]
>> > [-noall_load]
>> > scons: *** [polybori/libpolybori-0.5.0.dylib.0.0.0] Error 1
>> > scons: building terminated because of errors.
>> > Error building PolyBoRi.
>>
>> > real 4m20.282s
>> > user 3m33.739s
>> > sys 0m28.699s
>> > sage: An error occurred while installing polybori-0.5rc.p4
>> > ...
>>
>> > See my message above from 11:18h for more info on that build problem.
>> > Is it the time worth to give the corrected tarball from 11:50h a try?
>> > (No, if just the spkg polybori...p3 was repalced by the ...p4 above,
>> > what is exactly what I did manually on my Macs.)
>>
>> > Cheers,
>> > gsw
>>
>> > On 9 Sep., 11:22, mabshoff <[EMAIL PROTECTED]> wrote:
>> >> Arg, I know what is wrong and it was a dumb mistake of mine. The spkg
>> >> at
>>
>> >>http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/rc...
>>
>> >> fixes the issue. My apologies, it seems that everything that can go
>> >> wrong will go wrong in the 3.1.2 release cycle :(
>>
>> >> Cheers,
>>
>> >> Michael
>>
>> --
>> Alexandru Ghitza
>> Lecturer, Pure Mathematics
>> Department of Mathematics and Statistics
>> The University of Melbourne
>> Parkville, VIC, 3010
>> Australia
> >
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
