#6456: Upgrade cvxopt in sage from 0.9 to 1.1.2
------------------------+---------------------------------------------------
Reporter: was | Owner: mabshoff
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.3.3
Component: packages | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by drkirkby):
Replying to [comment:15 dimpase]:
> Replying to [comment:14 drkirkby]:
> > However, I do not know how the compilers and paths are configured on
that machine. You need to have GNU make & GNU tar in your path before the
Sun ones, and you need to have the Sun linker (/usr/ccs/bin/ld) in your
path before any GNU ones. There are some general instructions on building
Sage on Solaris at http://wiki.sagemath.org/solaris which you would need
to follow.
>
> well, on Skynet there is /usr/local/skynet_bash_profile
> that you can source upon login (from .bashrc, or just manually),
> and this gives you the ready setup to build Sage.
I'm not however aware of anyone building Sage on there recently, so I
don't know if the environment is set up suitably. Quite a few Solaris-
specific changes have been made in the last year, and some of them might
not be compatible with the build system on there. I don't know.
Specifically, if
{{{
gcc -v
}}}
shows gcc was configured with the GNU linker, then the GNU linker must be
in your path before the Sun linker. (Basically, whatever linker gcc uses,
must be in your path first, as some code makes the assumption the first
linker in your path is the one gcc uses, which might not be true.) I'm not
aware of a foolproof test of this.
There should be something like
{{{
--with-ld=/usr/ccs/bin/ld
}}}
if the Sun linker was used, or
{{{
--with-ld=/path/to/gnu/ld
}}}
if the GNU linker was used.
Certainly, I've never had a problem with gnutls failing on 't2'.
> I don't have an account on t2, it seems to me.
I've emailed William to ask if you can have an account on t2, as that
might be the simplest solution, though that Blade 2500 would be
significantly faster than 't2'.
> By the way, absent-mindedly I started building 4.3.3.alpha on there,
> and it went till gnutls, where it stopped... I noticed that gnutls is
over 2 years old, version 2.2.2, whereas the current one is 2.8.5.
Shouldn't one upgrade to this one, before even trying to fix this?
>
> Dima
I can see your point about upgrading, though I'm not aware of any
particular issues with the version in Sage. That version will build on
Solaris. You could try appending /usr/sfw/lib to your LD_LIBRARY_PATH. I
have known of issues with gnutls on OpenSolaris, but not on Solaris 10.
I see your post about the GPL 3. That bit is sorted out then.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6456#comment:17>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
