Bill Hart wrote:
Actually, I might be thinking of a similar issue which occurs for OSX
64 bit. So perhaps this just hasn't been fixed for solaris yet.
Micheal made endless fixes like
if [ $SAGE64 = yes -a `uname` = Darwin ] then ;
some OS X fix.
fi
Since 99% of those fixes, such as adding -m64 to CFLAGS, would have been
appropriate on any 64-bit build, I think that was quite unfortunate. So it would
not surprise me if something was done on OS X, which would have been useful on
any 64-bit build.
I've tried to implement changes in a way that the operating-specific or
compiler-specific code is limited to a very small number of files.
Dave
On Jan 15, 12:46 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
This is a very old issue. It was fixed by Michael Abshoff years ago.
Who knows why it is broken again.
But I agree, the LD_LIBRARY_PATH_64 should be set correctly.
Bill.
On Jan 14, 9:47 pm, "Dr. David Kirkby" <david.kir...@onetel.net>
wrote:
Jaap Spies wrote:
Building of linbox on Open Solaris 06/2009 in VirtualBox ends with:
----------------------------------------------------------------------
Libraries have been installed in:
/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/lib
[...]
linbox-sage.C: At global scope:
linbox-sage.C:72: warning: void linbox_set_modn_matrix(mod_int**,
LinBox::DenseMatrix<LinBox::Modular<double> >&, size_t, size_t)
declared static but never defined
make[4]: *** [linbox-sage.lo] Error 1
make[4]: Leaving directory
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/s
rc/interfaces/sage'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/s
rc/interfaces'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/s rc'
Error installing linbox
real 0m52.563s
user 0m33.152s
sys 0m17.425s
sage: An error occurred while installing linbox-1.1.6.p2
Please email sage-develhttp://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /export/home/jaap/Downloads/sage-4.3.1.alpha2/install.log. Describe
your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2
and type 'make check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd
'/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2'
&& '/export/home/jaap/Downloads/sage-4.3.1.alpha2/sage' -sh)
When you are done debugging, you can type "exit" to leave the
subshell.
make[1]: *** [installed/linbox-1.1.6.p2] Error 1
make[1]: Leaving directory
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg'
real 0m53.402s
user 0m33.611s
sys 0m17.806s
Error building Sage.
j...@opensolaris:~/Downloads/sage-4.3.1.alpha2$
With:
echo $LD_LIBRARY_64
/export/home/jaap/Downloads//sage-4.3.1.alpha2/local/lib:/usr/local/gcc-4.3
.4-GNU-assembler-Sun-linker/lib/amd64/:/usr/lib/amd64/
Jaap
There appear to be a number of issues with linbox on Solaris. I'm just a bit
concerned this might be a more fundamental one, having wider impact that simply
linbox.
I'm not sure how best to resolve this GMP related issue. There are two obvious
options
1) Install 64-bit libraries in $SAGE_LOCAL/lib/ and hope for the best. Hope that
LD_LIBRARY_PATH_64 gets us out of trouble. That could conceivably break if a
package installs headers into $SAGE_LOCAL/include and libraries into
$SAGE_LOCAL/lib/sparcv9.
Clearly this is the easiest option.
2) Define a directory SAGE_LOCAL_LIB
SAGE_LOCAL_LIB=$SAGE_LOCAL/lib/
if [ "x`uname`" = xSunOS ] ;
if [ "x$SAGE64" = xyes" ; then
SAGE_LOCAL_LIB=$SAGE_LOCAL/lib/`isainfo -k`
fi
fi
then install 64-bit libraries to $SAGE_LOCAL_LIB
I just checked my HP-UX machine, and find it too has a separate directory
/usr/lib/pa20_64/ for 64-bit libraries.
http://docs.sun.com/app/docs/doc/816-5138/dev-env?a=view
has some information about the Solaris conventions.
Part of me thinks we should do the job properly, and install the libraries in
the correct place. Another part of me thinks lets try and hope
LD_LIBRARY_PATH_64 gets us out of trouble.
--
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
