Sage 4.1.2.alpha2 fails to build on Solaris due to Singular

2 views
Skip to first unread message

Minh Nguyen

unread,
Sep 22, 2009, 1:14:42 PM9/22/09
to sage-...@googlegroups.com
Hi folks,

Sage 4.1.2.alpha2 fails to compile on t2.math, SPARC Solaris with GCC
4.4.1 and the Sun linker. This time the cause of the failure is due to
ticket #6596 [1] which upgrades Singular to version 3-1-0-4-20090723.
This failure has also been reported for Sage 4.1.2.alpha1. The
relevant ticket is #6951 [2]. Here's a snippet of the relevant error
message:

{{{
/bin/sh: ../.././install-sh: not found
make[3]: [install-libsingular] Error 1 (ignored)
../.././install-sh -c kInline.cc
/scratch/mvngu/sage-4.1.2.alpha2/local/include/singular
make[3]: ../.././install-sh: Command not found
make[3]: *** [install-libsingular] Error 127
make[3]: Leaving directory
`/scratch/mvngu/sage-4.1.2.alpha2/spkg/build/singular-3-1-0-4-20090818/src/kernel'
make[2]: *** [install-libsingular] Error 2
make[2]: Leaving directory
`/scratch/mvngu/sage-4.1.2.alpha2/spkg/build/singular-3-1-0-4-20090818/src'
Unable to install libsingular.

real 51m44.032s
user 45m26.845s
sys 2m40.908s
sage: An error occurred while installing singular-3-1-0-4-20090818
}}}

[1] http://trac.sagemath.org/sage_trac/ticket/6596

[2] http://trac.sagemath.org/sage_trac/ticket/6951

--
Regards
Minh Van Nguyen

gsw

unread,
Sep 22, 2009, 4:46:33 PM9/22/09
to sage-devel
Hi Minh,

obviously (look at your own trace output), you are talking about
"singular-3-1-0-4-20090818.spkg", not
"singular-3-1-0-4-20090723.spkg".

Just looking at the top entries of the "SPKG.txt" file of the old
(Sage-4.1.1) "singular-3-1-0-2-20090620.p0.spkg", and of the current
Sage-4.1.2-alpha "singular-3-1-0-4-20090818.spkg", shows what the
problem is, that the latter spkg might be broken also on Itanium
(ia64, see trac #6360 and #6240) i.e. not only on Sun, and what to do
about it.
I can look into building a new spkg with the necessary fixes tomorrow,
or the day after, if nobody beats me to it.

Cheers,
Georg
Reply all
Reply to author
Forward
0 new messages