kcrisman wrote:
> That's unfortunate. Indeed, I do not have libntl.0.dylib, just
> libntl.3.dylib and libntl.dylib. And yes, this was from a
working 6.1.1
> :-) All on OS X 10.7.5 with usual tools. Is this another
> SAGE_UPGRADING=yes (I don't - yet - have it set) thing?
Yes and no (since it's the same since NTL has been upgraded). ;-)
And that wouldn't have happened with 'sage --upgrade', since that uses
SAGE_UPGRADING=yes (hence the name of the latter). Just saying...
I.e. https://groups.google.com/forum/#!topic/sage-release/I1bYOE5W0Ww ?
Of course, I really don't want to do make distclean && make. Doing sage
-f ntl probably isn't right either, but it's what I'm trying.
Unfortunately plain 'make' (with SAGE_UPGRADING!=yes) also touches the
files in ... .../installed/, so rerunning 'make' with SAGE_UPGRADING=yes
afterwards has no effect.
But in your case, it should be sufficent to simply touch
.../installed/ntl-... (the *new* version) [i.e., no need to reinstall
it], and /then/ (re)run 'env SAGE_UPGRADING=yes make'. At least the
errors above, caused by modules still referencing the shared library of
the old NTL version will vanish.
(You may run into similar problems with other updated spkgs, in which
case the same procedure -- just touching those packages to pretend they
had been installed recently, /after/ any package that depends on them,
and running 'make' with SAGE_UPGRADING set to 'yes' -- should work.)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
