On Nov 24, 10:43 am, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On Nov 24, 6:27 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
>
Hello Justin,
>
>
> > On Nov 23, 2007, at 21:11 , William Stein wrote:
>
> > > On Nov 23, 2007 8:18 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote:
> > >>> This is all really weird since I fully tested building
> > >>> Sage-2.8.13 on
> > >>> OSX 10.4 intel and OSX 10.5 intel (both core duo and Xeon),
> > >>> and didn't have any problems at all. So the problem could
> > >>> be with...
> > > ...
> > >> I reported this during one of the "alpha/rc" cycles (2.8.10.alpha?, I
> > >> think), and tried the "move /usr/local out of the way" trick. That
>
> > > I see! The problem was definitely in 2.8.13.rc0 I think, because
> > > I found
> > > it then, and then somebody subsequently fixed it as a result, i.e.,
> > > the
> > > problem is fixed in 2.8.13 (but not before).
>
> Hello Justin,
>
> I remember that you reported the problem on 10.4 with your gmp in /usr/
> local, but we never opened a ticket for it. The cddlib.spkg I posted
> above fixes the issues (at least it ought to), so please try that one
> out and report back.
>
> In that contect:
> * Axiom 1: Untested code is broken.
> * Axiom 2: Reported bugs not entered into trac will get lost.
>
The problems you have with 10.4.11 and 10.5.1 are unrelated.
#1252 is the gmp in /usr/local issue which should be fixed.
#1253 is the 10.5.1 build failure. The problem is that gmp contains a
workaround for 10.5 that didn't get applied on 10.5.1 because the
check is for Darwin-9.0.0 while OSX 10.5.1 is Darwin-9.1.0. The same
happens with python and maybe more spkgs. My build on 10.5.1 hasn't
finished yet. The issue is trivial to fix and 2.8.14.rc1 should have
all the fixes. By the time you people on the west coast wake up rc1
should be ready for download - and it is Thanksgiving weekend, so so
far it felt like the states have dropped off the face of the earth for
the last couple days ;)
I made #1253 a blocker for 2.8.14.
Cheers,
Michael
>
>
>
>
> > Do you mean 2.18.14? This showed up for me in the released 2.8.13.
>
> > >>> Something I've wondered about for a while -- is there a bulletproof
> > >>> way to ignore /usr/local/ during build of Sage?
>
> > >> I think 'gcc' has flags that let you force the lookup paths for
> > >> "system-supplied" includes and libs. I'll see if I can track that
> > >> down.
>
> > > That would be very very interesting indeed.
>
> > This will take a bit of time to run to ground...there are a handful
> > of flags, and they have overlapping functionality. I'll send a
> > synopsis when I've digested what Xcode has to say.
>
> That might be an interesting approach, but I consider issues like the
> one you see on 10.4 build system bugs. If we could change the search
> path default for the linker on the fly we should do it, but changing
> it globally would probably break loads of other software.
>
> > Justin
>
> Cheers,
>
> Michael
>
>
>
> > --
> > Justin C. Walker, Curmudgeon-At-Large
> > Institute for the Absorption of Federal Funds
> > --------
> > If you're not confused,
> > You're not paying attention
> > --------
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
