I tried building sage 4.3.0.1 (and 4.3.0.2.alpha5-6583 snapshot created by Minh to demonstrate that unpleasant trac# 6583 bug) on skynet's mark, (SunOS mark 5.10 Generic_127111-01 sun4u sparc SUNW,Sun-Blade-2500)
and it fails at gnutls spkg (this is not happening on t2), with messages indicating that it does not find things in libgcrypt. I even tried modifying spkg-install to insist that configure looks for libgcrypt in $SAGE_LOCAL, but to no avail. Morever, if I just run ./configure with the options as in spkg- install, as well as --with-libgcrypt-prefix=$SAGE_LOCAL, in src/ directory of the spkg, and then make, it builds OK. The difference in the gcc call that fails is that it has -R $SAGE_LOCAL/lib option, while during the successful build the same call has instead options -Wl,--rpath -Wl,$SAGE_LOCAL/lib My guess is that -R (a linker option) is not working properly here (as it's a mixed gcc/sun linker environment, things are a bit weird...)?! I do not understand how this can happen (different configure behavour when invoked with sage building?!), and what's going on. This anyhow needs to be fixed if we want to move on with the Solaris port. Dima -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
