On Sep 10, 8:36 pm, Hamptonio <[EMAIL PROTECTED]> wrote:
> cat /etc/issue gives:

Hello Marshall,

>
> Welcome to SUSE LINUX Enterprise Server 9 (x86_64) - Kernel \r (\l).
>
> The tail end of the polymake build, when it crashes, has the
> following:
>
> make[2]: Leaving directory `/home/bc1/hamptonm/sage-2.8.3.6/spkg/build/
> polymake-2.2.p2/build/modules/graph'
> g++   -I/home/bc1/hamptonm/sage-2.8.3.6/local/lib  -I/home/bc1/
> hamptonm/sage-2.8.3.6/local/lib  -o cayley_embedding
> cayley_embedding.o libpolytope.a ../../lib/libpoly.a  -lgmp
> collect2: ld terminated with signal 11 [Segmentation fault]

Okay, this is not a gcc issue (at least the output makes it very
unlikely), but that the linker shoots itself. Check with the sysadmin
if there is a more current ld somewhere in the systems, otherwise
compile your own binutils locally and make sure that they are in $PATH
before the systems ld. Try again with that ld and let us know if the
problem goes away. You should also make sure the polymake doesn't hard
code the path to ld somewhere in the makefile in case the error
doesn't go away with the new binutils.

> make[2]: *** [cayley_embedding] Error 1
> make[1]: *** [do_all] Error 2
> make[1]: Leaving directory `/home/bc1/hamptonm/sage-2.8.3.6/spkg/build/
> polymake-2.2.p2/build/apps/polytope'
> make: *** [all] Error 2
> cp: cannot create regular file `/home/bc1/hamptonm/sage-2.8.3.6/local/
> polymake/bin/polymake': No such file or directory
> Do not worry if there is an error message above, as long as the build
> says it worked below.
> Error building and installing polymake
>
> real    6m1.033s
> user    5m19.608s
> sys     0m31.232s
>

Cheers,

Michael


--~--~---------~--~----~------------~-------~--~----~
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to