#9896: Upgrading from 4.5.3 to 4.6.alpha* can fail (not limited to MacOS X)
------------------------------+---------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.6
Component: build | Keywords: upgrade update dependencies PARI
NewPARI
Author: Leif Leonhardy | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:111 jhpalmieri]:
> I'm confused again. On my mac, it seems like
{{{
#!sh
$ export LDSHARED="gcc -bundle -undefined dynamic_lookup"
}}}
> solves the problem: I did this and then upgraded from 4.5.3 to
4.6.alpha'''3''', and did not have the reported problem and all tests pass
in sage/libs/pari.
{{{ptestlong}}}? Some extension modules should still refer to the ''old''
PARI shared library, which can cause trouble. Did you do anything else
except {{{export LDSHARED=...}}} and {{{./sage -upgrade
/path/to/alpha3}}}?
> So do we need the various patches?
Currently just four IIRC... ;-)
> They may be good ideas, but are they necessary for this ticket? (I have
only seen a problem on OS X, so I can't easily test what works and what
doesn't on other systems.)
While setting {{{LDSHARED}}} is not necessary on systems other than MacOS
X (at least as far as I know / on the supported platforms), the patches
make upgrading more "reliable". (I personally had to play a little to make
upgrading fail on my Linux boxes I must admit, but without the patches it
definitely ''can'' fail. Also, we'd run into similar problems when it
comes to upgrading e.g. MPIR; to make ''that'' work, we'll in addition
have to add some more dependencies to {{{module_list.py}}}.)
> Also, do we need to advertise the need to set LDSHARED like this? Or
can we set it automatically during the upgrade process?
I intended to do so, there are just (too) many ways how one could do this.
;-) (Basically e.g. adding a few Darwin-specific lines to
{{{devel/sage/setup.py}}}, which is part of the {{{sage-x.y.z.spkg}}},
which "of course" gets updated upon ''every'' upgrade, regardless if there
are any changes to the Sage library at all - besides {{{version.py}}}
which is or will become redundant anyway.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9896#comment:114>
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.
