On Feb 19, 5:29 am, Simon King <k...@mathematik.uni-jena.de> wrote:
> On Feb 19, 1:35 pm, mabshoff <mabsh...@googlemail.com> wrote:

<SNIP>

> I copied the info that ./sage -b gave me into some file
> installSAGE_B.log.
> You can find the two install.log 
> athttp://sage.math.washington.edu/home/SimonKing/SPKG/

Ok, you build three of the four extensions successfully, so NTL is not
at fault here any more, but then things blow up with

cc1plus: warning: command line option "-Wstrict-prototypes" is valid
for Ada/C/ObjC but not for C++
sage/rings/polynomial/multi_polynomial_libsingular.cpp: In function
âObject* __pyx_pf_4sage_5rings_10polynomial_28multi_polynom
ial_libsingular_23MPolynomial_libsingular_gcd(PyObject*, PyObject*,
PyObject*)âsage/rings/polynomial/multi_polynomial_libsingul
ar.cpp:21731: error: â_USE_CHINREM_GCDâas not declared in this scope
sage/rings/polynomial/multi_polynomial_libsingular.cpp:21763: error:
â_USE_CHINREM_GCDâas not declared in this scope
error: command 'gcc' failed with exit status 1
sage: There was an error installing modified sage library code.

This seems to be Sage 3.1.2, so is it 3.1.2 or is it upgraded? It
might very well be that this singular.spkg you have been building
needs a recent Sage, but Martin knows more about that glue code than I
do.

Also: What g++ are you using on that machine? Is the 3.1.2 build from
sources?

We seem to wipe out the old installed headers, but maybe for whatever
reason this is a problem with factory? The best lead you might get is
if you figure out if there are any renames of libraries or headers.
And likely asking Hans this question about the symbol
"_USE_CHINREM_GCD" might also lead to a quick solution.

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to